Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot update problem list #74

Open
ivan-shih opened this issue Mar 11, 2024 · 15 comments
Open

cannot update problem list #74

ivan-shih opened this issue Mar 11, 2024 · 15 comments

Comments

@ivan-shih
Copy link

After inputting the cookie, LeetCode.nvim always displays "session expired" and prompts me to input a new cookie to continue using it.

Strangely, I can see LeetCode.nvim displaying my LeetCode login username, indicating that I have successfully logged in, but it still keeps prompting me to update the cookie.

However, this issue occurs only on my MacPro. When I use Ubuntu, everything works fine.

@kawre
Copy link
Owner

kawre commented Mar 11, 2024

Are you on the latest commit on your mac?

@ivan-shih
Copy link
Author

Are you on the latest commit on your mac?

Yes, I just checked and confirmed that I'm on the latest commit 05d415.
I can provide more information to assist you in debugging. Please let me know what additional information would be helpful.

@kawre
Copy link
Owner

kawre commented Mar 12, 2024

Can you use a new cookie and confirm that this cookie contains cf_clearance, LEETCODE_SESSION and csrftoken tokens?

@ivan-shih
Copy link
Author

csrftoken

I have just confirmed that all three tokens - cf_clearance, LEETCODE_SESSION, and csrftoken are present in the session.

@ivan-shih
Copy link
Author

That's right, I had previously tried copying the Chrome session from Linux to MacOS, but it still didn't work properly. However, I'm confident that the session worked fine with LeetCode.nvim on Linux.

kawre added a commit that referenced this issue Mar 12, 2024
@kawre
Copy link
Owner

kawre commented Mar 12, 2024

Can you try changing leetcode.nvim branch to macos and check if it changes anything?

With lazy.nvim just add branch = "macos" to your leetcode.nvim config

@ivan-shih
Copy link
Author

Can you try changing leetcode.nvim branch to macos and check if it changes anything?

With lazy.nvim just add branch = "macos" to your leetcode.nvim config

The problem persists even after switching to the macOS branch (commit 9a639).

@ivan-shih
Copy link
Author

When copying the LeetCode session from Chrome to LeetCode.nvim, I can momentarily see "Login successful" but it then prompts that the session has expired, even though it displays my LeetCode username in the background. Do you need me to provide any logs? I can assist in obtaining them.

@kawre
Copy link
Owner

kawre commented Mar 13, 2024

You can pass debug = true in leetcode.nvim opts to see http responses, but im guessing it won't be any different then this #69.

@kawre
Copy link
Owner

kawre commented Mar 14, 2024

can you check if latest commit changed anything?

@ivan-shih
Copy link
Author

can you check if latest commit changed anything?

I just pulled the latest commit and got this error:

Enable JavaScript and cookies to continue
<script>

@kawre
Copy link
Owner

kawre commented Mar 18, 2024

Does this issue still persists? Supposedly leetcode has fixed this

@ivan-shih
Copy link
Author

Does this issue still persists? Supposedly leetcode has fixed this

Unfortunately, that doesn't seem to be the case. The problem persists from what I can tell.

@smomara
Copy link

smomara commented Aug 19, 2024

I'm having the same issue. Tried macos branch as well. @ivan-shih have you found a fix?

image

@ivan-shih
Copy link
Author

I'm having the same issue. Tried macos branch as well. @ivan-shih have you found a fix?

image

I haven't found a direct fix for the issue yet. Instead, I'm currently running leetcode.nvim using Docker in a Linux environment, which has been working for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants