New LeetCode UI

[FNSYacoub]

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]

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]

@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]

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]

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

[QasimWani]

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]

I think the bug is still there for the new UI

[dashingquark]

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

[QasimWani]

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]

now using older version 👍

[thegreekgoat98]

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]

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]

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]

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]

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]

@aguynamedloren

[varun-s22]

I have submitted a PR regarding this issue, Will get to it, when someone reviews it

[SUSHANT12PRABHU]

Yes same issue, lets wait!

[Asharalikhan4]

Yes same issue, lets wait!

You can change leetcode UI till the issue get fixed.

[jpsxlr8]

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

[mrFahrenhiet]

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]

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

[Ahmed-Shukri02]

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:

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

[plgrazon]

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:

1. Fork this repo and clone to your local machine
2. Change to the patch_1 branch by typing git checkout patch_1 in your command line
3. Go to chrome://extensions
4. Enable Developer mode by toggling the switch on top right corner
5. Click 'Load unpacked'
6. Select the entire LeetHub folder
7. 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]

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:

1. Fork this repo and clone to your local machine
2. Change to the patch_1 branch by typing git checkout patch_1 in your command line
3. Go to chrome://extensions
4. Enable Developer mode by toggling the switch on top right corner
5. Click 'Load unpacked'
6. Select the entire LeetHub folder
7. 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]

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:

1. Fork this repo and clone to your local machine
2. Change to the patch_1 branch by typing git checkout patch_1 in your command line
3. Go to chrome://extensions
4. Enable Developer mode by toggling the switch on top right corner
5. Click 'Load unpacked'
6. Select the entire LeetHub folder
7. 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]

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:

1. Fork this repo and clone to your local machine
2. Change to the patch_1 branch by typing git checkout patch_1 in your command line
3. Go to chrome://extensions
4. Enable Developer mode by toggling the switch on top right corner
5. Click 'Load unpacked'
6. Select the entire LeetHub folder
7. 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]

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:

1. Fork this repo and clone to your local machine
2. Change to the patch_1 branch by typing git checkout patch_1 in your command line
3. Go to chrome://extensions
4. Enable Developer mode by toggling the switch on top right corner
5. Click 'Load unpacked'
6. Select the entire LeetHub folder
7. 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:

1. Had an old repo that was linked to the original LeetHub extension.
2. I installed this new LeetHub-Test extension built by @Ahmed-Shukri02
3. I linked my previously exisiting repo to this extension
4. Tried submitting a code, but it was not pushed to GitHub (with the new LeetCode UI)
5. Created and linked a new repo with this extension
6. Tried submitting again, code still did not get pushed to the new repo
7. 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]

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]

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

[nabilnaja]

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]

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]

its not pushing the code to github please fix the issue

[Sami-AlEsh]

waiting for any update ...

[varun-s22]

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]

yes its not pushing the code from leetcode to github .

[RafaelJohn9]

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]

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]

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]

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

[plgrazon]

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]

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

[plgrazon]

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]

@plgrazon follow for follow 🤝🤝