New LeetCode UI #366

FNSYacoub · 2022-10-04T16:12:19Z

Since the 1st of October 2022, LeetCode has a new UI and submission process which is not compatible with how the plugin works, thus it stopped working.
I think the plugin needs an urgent update to work with the new UI.

QasimWani · 2022-10-04T22:02:34Z

it seems to work fine now? Can someone else confirm this? I tested it with a new problem and an older problem I had already solved before.

B-soto · 2022-10-05T00:23:40Z

@QasimWani Looks like the bug is still present. Latest leethub code over the last 6 days is not being added to my git repo

QasimWani · 2022-10-05T00:59:58Z

hmm so leetcode update only seems to reflect on my new leetcode account. Talked to few folks and it seems like the UI update hasn't reflected across al leetcode users. Let's discuss this further in our discord (see #general channel)

arm210402 · 2022-10-05T05:00:36Z

Is the code updated or not for the new UI ??
@B-soto

QasimWani · 2022-10-05T05:11:06Z

no code has been pushed to LeetHub. leetcode UI hasn't been changed on my account for some reason. I don't think leetcode UI is universally applied?

kshitij-srivastav · 2022-10-05T06:24:30Z

I think the bug is still there for the new UI

dashingquark · 2022-10-05T21:46:28Z

I still have no code updating. old account(pre Oct 1st) , deleted and reinstalled repo

QasimWani · 2022-10-09T09:53:18Z

use the older leetcode UI. Click on your profile and click "revert to old version"

I won't have time maintaining the repo on a daily basis. But happy to look into PR's for this issue.

arm210402 · 2022-10-09T12:55:37Z

now using older version 👍

thegreekgoat98 · 2022-10-11T18:02:22Z

use the older leetcode UI. Click on your profile and click "revert to old version"

I won't have time maintaining the repo on a daily basis. But happy to look into PR's for this issue.

Thanks this worked.

dragneel786 · 2022-10-12T17:46:24Z

Don't wanna sound pushy, but can you please figure out how to solve this issue, as a temporary fix reverting to older version is fine, but I really love the leetcode new UI and I really really love this extension. So please help here!!

andreidimaano · 2022-10-14T00:40:25Z

Hey Everyone, I inspected the LeetCode success page on the new UI. In the source code for this repo we have this:

const successTag = document.getElementsByClassName('success__3Ai7');

The new UI doesn't have this success class name but I found that the tag leading-6 seems to be unique and associated with Acceptance. i don't have time to code it but maybe someone can use this and test it out with the new UI? @QasimWani

heykush · 2022-10-26T19:33:40Z

Hi @QasimWani @andreidimaano, I have tried a possible solution of yours to change the tag, but it didn't work out because leetcode has updated my tag in New UI. This need to review the whole file of the leetcode.js. Let me know if anyone will do it; I love to help with that.

ps: working fine with Old UI

aguynamedloren · 2022-10-27T04:47:20Z

Happy to help debug and investigate a fix here if I get the new UI, but for now, it looks like I'm still on the old UI.

For context, can someone with the new UI post a screenshot?

IshaanAnsari · 2022-11-05T16:37:08Z

@aguynamedloren

jpsxlr8 · 2023-01-16T12:21:58Z

I think still the problem persists!
Anyone got any updates regarding new UI ??

mrFahrenhiet · 2023-01-16T18:37:42Z

I think still the problem persists! Anyone got any updates regarding new UI ??

Yes I am facing this problem as well. There only seems to be one solution, i.e., to revert back to old version

codentacos · 2023-01-18T16:59:26Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

Ahmed-Shukri02 · 2023-01-18T19:24:29Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

I've made a pull request that should fix the issue. It should be in prod soon.
Whilst you are waiting for the update, you can fork my repo and use it locally on your machine:

Fork this repo and clone to your local machine
Change to the patch_1 branch by typing git checkout patch_1 in your command line
Go to chrome://extensions
Enable Developer mode by toggling the switch on top right corner
Click 'Load unpacked'
Select the entire LeetHub folder
Run "npm run setup" to install the developer dependencies

plgrazon · 2023-01-31T13:59:11Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

I've made a pull request that should fix the issue. It should be in prod soon. Whilst you are waiting for the update, you can fork my repo and use it locally on your machine:

Fork this repo and clone to your local machine

Change to the patch_1 branch by typing git checkout patch_1 in your command line

Go to chrome://extensions

Enable Developer mode by toggling the switch on top right corner

Click 'Load unpacked'

Select the entire LeetHub folder

Run "npm run setup" to install the developer dependencies

Hi Ahmed,

Great work! I forked your repo but I'm getting the 422 issue when submitting. Is this a known bug?

mayankjain25 · 2023-02-01T19:43:26Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

I've made a pull request that should fix the issue. It should be in prod soon. Whilst you are waiting for the update, you can fork my repo and use it locally on your machine:

Fork this repo and clone to your local machine

Change to the patch_1 branch by typing git checkout patch_1 in your command line

Go to chrome://extensions

Enable Developer mode by toggling the switch on top right corner

Click 'Load unpacked'

Select the entire LeetHub folder

Run "npm run setup" to install the developer dependencies

This still does not work. Have tried it in the new UI but the codes aren't getting pushed

nabilnaja · 2023-02-01T20:30:57Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

I've made a pull request that should fix the issue. It should be in prod soon. Whilst you are waiting for the update, you can fork my repo and use it locally on your machine:

Fork this repo and clone to your local machine

Change to the patch_1 branch by typing git checkout patch_1 in your command line

Go to chrome://extensions

Enable Developer mode by toggling the switch on top right corner

Click 'Load unpacked'

Select the entire LeetHub folder

Run "npm run setup" to install the developer dependencies

Hi Ahmed,

Great work! I forked your repo but I'm getting the 422 issue when submitting. Is this a known bug?

I had the same problem when I was using an existing repo. It worked when I created a new one from leethub screen. Hope this helps you.

plgrazon · 2023-02-01T22:22:49Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

I've made a pull request that should fix the issue. It should be in prod soon. Whilst you are waiting for the update, you can fork my repo and use it locally on your machine:

Fork this repo and clone to your local machine

Change to the patch_1 branch by typing git checkout patch_1 in your command line

Go to chrome://extensions

Enable Developer mode by toggling the switch on top right corner

Click 'Load unpacked'

Select the entire LeetHub folder

Run "npm run setup" to install the developer dependencies

Hi Ahmed,

Great work! I forked your repo but I'm getting the 422 issue when submitting. Is this a known bug?

I had the same problem when I was using an existing repo. It worked when I created a new one from leethub screen. Hope this helps you.

Yea. That's what I did as well, made a new repo then switched to the old one.

mayankjain25 · 2023-02-03T05:26:00Z

Also experiencing this issue. Any updates on a fix coming for this?(Besides reverting to old UI)

I've made a pull request that should fix the issue. It should be in prod soon. Whilst you are waiting for the update, you can fork my repo and use it locally on your machine:

Fork this repo and clone to your local machine

Change to the patch_1 branch by typing git checkout patch_1 in your command line

Go to chrome://extensions

Enable Developer mode by toggling the switch on top right corner

Click 'Load unpacked'

Select the entire LeetHub folder

Run "npm run setup" to install the developer dependencies

Hi Ahmed,
Great work! I forked your repo but I'm getting the 422 issue when submitting. Is this a known bug?

I had the same problem when I was using an existing repo. It worked when I created a new one from LeetHub screen. Hope this helps you.

Yea. That's what I did as well, made a new repo then switched to the old one.

Here's what I did:

Had an old repo that was linked to the original LeetHub extension.
I installed this new LeetHub-Test extension built by @Ahmed-Shukri02
I linked my previously exisiting repo to this extension
Tried submitting a code, but it was not pushed to GitHub (with the new LeetCode UI)
Created and linked a new repo with this extension
Tried submitting again, code still did not get pushed to the new repo
Linked my older repo again, but the code still was not pushed

I don't understand what is wrong here. Please check this out.
(btw kudos to @Ahmed-Shukri02 for coming up with the fix)

Ahmed-Shukri02 · 2023-02-10T17:21:30Z

Hi Ahmed,

Great work! I forked your repo but I'm getting the 422 issue when submitting. Is this a known bug?

Hi @plgrazon, sorry for the late reply but yes this is a known issue that is found even on the old version of leethub for old leetcode UI #486. I don't really understand it and I might be wrong but I think it has something to do with trying to update a solution already in your repository from a device that isn't storing the commit's SHA in your chrome storage (for example if you completed Two Sum on one device and tried to commit it again to the same repo on another device or re-initializing leethub on the same device). It's quite annoying but a good quick fix suggested by @nabilnaja is to just make a new repo

This still does not work. Have tried it in the new UI but the codes aren't getting pushed

@mayankjain25 Right now you may be on the main branch which is quite outdated. Sorry for the confusion, I haven't made that super clear and I might merge the working version onto main to make it less confusing.

My current working version is on the patch_1 branch. For now you can access it by running git checkout patch_1 on the bash terminal you cloned the repo on.

jals413 · 2023-05-13T12:52:00Z

Can we get an update regarding the fix of this issue ?

nabilnaja · 2023-05-20T22:57:09Z

It doesn't push the solution anymore. it's since May 17.

@Ahmed-Shukri02 Do you have any idea why please?

Thank you.

varun-s22 · 2023-07-22T21:18:38Z

Turns out Leetcode got updated once again, and this time it resembles the previous original result page.
I think now this can be integrated with the new UI :)
Will work soon, if @Ahmed-Shukri02 or someone reviews on it

lokeshs333 · 2023-08-28T11:58:57Z

its not pushing the code to github please fix the issue

Sami-AlEsh · 2023-08-29T06:23:59Z

waiting for any update ...

varun-s22 · 2023-08-29T06:40:31Z

uhmm ok i'll have a look at this once again.. and if @QasimWani or someone could review it, then that would be nice
else you can use my public fork for the same
I'll take a look in a week or so ;)

ADITISHARMA-22 · 2023-09-19T08:59:47Z

yes its not pushing the code from leetcode to github .

RafaelJohn9 · 2024-01-10T18:27:03Z

I'll be willing to work on the extension to accept the new UI if the owner is willing to accept me working on it

arm210402 · 2024-01-10T18:28:51Z

I'll be willing to work on the extension to accept the new UI if the owner is willing to accept me working on it

Just fort it

Imtiaz-Rafi · 2024-02-06T18:53:22Z

Its been more than 1 year, but why its not still resolved? I can see some open pull request also, which can solve the issue.

likeyellow · 2024-02-22T07:46:13Z

Thanks for your shared.
Now It is very well work.

plgrazon · 2024-03-14T19:00:12Z

I'll be willing to work on the extension to accept the new UI if the owner is willing to accept me working on it

Hi @RafaelJohn9 were you able to resolve the issue?

RafaelJohn9 · 2024-03-14T19:15:54Z

No, I found that another developer had already resolved it. Check the leethub extension. Supports multiple browsers

plgrazon · 2024-03-14T19:52:49Z

No, I found that another developer had already resolved it. Check the leethub extension. Supports multiple browsers

got it, I just found one as well. Thanks

RafaelJohn9 · 2024-03-15T04:22:39Z

@plgrazon follow for follow 🤝🤝

shafaque · 2024-07-18T16:58:24Z

I think the problem still persists :(

Al-toid · 2024-09-19T17:18:11Z

No, I found that another developer had already resolved it. Check the leethub extension. Supports multiple browsers

can you link?

RafaelJohn9 · 2024-10-01T04:38:32Z

No, I found that another developer had already resolved it. Check the leethub extension. Supports multiple browsers

can you link?
https://chromewebstore.google.com/detail/leethub-v2/mhanfgfagplhgemhjfeolkkdidbakocm?hl=en&pli=1

FNSYacoub added the bug Something isn't working label Oct 4, 2022

FNSYacoub assigned QasimWani Oct 4, 2022

This was referenced Oct 4, 2022

No more commits after the leetcode update. #357

Open

LeetHub is not working #365

Closed

QasimWani pinned this issue Oct 11, 2022

QasimWani mentioned this issue Oct 13, 2022

Questions are not being updated to repository after new UI in leetcode coding interface. #380

Open

andreidimaano mentioned this issue Oct 14, 2022

Possible Solution to #366 - New LeetCode UI #383

Open

saipavanbhanu mentioned this issue Nov 4, 2022

LeetHub no longer pushing submissions with new Leetcode update #399

Open

Ahmed-Shukri02 mentioned this issue Jan 9, 2023

My leet code solutions dont update / dont go to my github repo. Can anyone help? #476

Open

Therason mentioned this issue Feb 13, 2023

The Extension Isn't supporting New LeetCode UI. Please Fix This Issue #496

Open

New LeetCode UI #366

New LeetCode UI #366

Comments

FNSYacoub commented Oct 4, 2022

QasimWani commented Oct 4, 2022

B-soto commented Oct 5, 2022

QasimWani commented Oct 5, 2022 • edited Loading

arm210402 commented Oct 5, 2022 • edited Loading

QasimWani commented Oct 5, 2022

kshitij-srivastav commented Oct 5, 2022

dashingquark commented Oct 5, 2022

QasimWani commented Oct 9, 2022

arm210402 commented Oct 9, 2022

thegreekgoat98 commented Oct 11, 2022

dragneel786 commented Oct 12, 2022

andreidimaano commented Oct 14, 2022 • edited Loading

heykush commented Oct 26, 2022

aguynamedloren commented Oct 27, 2022

IshaanAnsari commented Nov 5, 2022

jpsxlr8 commented Jan 16, 2023

mrFahrenhiet commented Jan 16, 2023 • edited Loading

codentacos commented Jan 18, 2023

Ahmed-Shukri02 commented Jan 18, 2023 • edited Loading

plgrazon commented Jan 31, 2023

mayankjain25 commented Feb 1, 2023

nabilnaja commented Feb 1, 2023

plgrazon commented Feb 1, 2023

mayankjain25 commented Feb 3, 2023

Ahmed-Shukri02 commented Feb 10, 2023

jals413 commented May 13, 2023

nabilnaja commented May 20, 2023 • edited Loading

varun-s22 commented Jul 22, 2023

lokeshs333 commented Aug 28, 2023

Sami-AlEsh commented Aug 29, 2023

varun-s22 commented Aug 29, 2023

ADITISHARMA-22 commented Sep 19, 2023

RafaelJohn9 commented Jan 10, 2024

arm210402 commented Jan 10, 2024

Imtiaz-Rafi commented Feb 6, 2024

likeyellow commented Feb 22, 2024

plgrazon commented Mar 14, 2024

RafaelJohn9 commented Mar 14, 2024

plgrazon commented Mar 14, 2024

RafaelJohn9 commented Mar 15, 2024

shafaque commented Jul 18, 2024

Al-toid commented Sep 19, 2024

RafaelJohn9 commented Oct 1, 2024

QasimWani commented Oct 5, 2022 •

edited

Loading

arm210402 commented Oct 5, 2022 •

edited

Loading

andreidimaano commented Oct 14, 2022 •

edited

Loading

mrFahrenhiet commented Jan 16, 2023 •

edited

Loading

Ahmed-Shukri02 commented Jan 18, 2023 •

edited

Loading

nabilnaja commented May 20, 2023 •

edited

Loading