Open ivan-shih opened 3 months ago
Are you on the latest commit on your mac?
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.
Can you use a new cookie and confirm that this cookie contains cf_clearance
, LEETCODE_SESSION
and csrftoken
tokens?
csrftoken
I have just confirmed that all three tokens - cf_clearance, LEETCODE_SESSION, and csrftoken are present in the session.
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.
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
Can you try changing
leetcode.nvim
branch tomacos
and check if it changes anything?With
lazy.nvim
just addbranch = "macos"
to your leetcode.nvim config
The problem persists even after switching to the macOS branch (commit 9a639).
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.
You can pass debug = true
in leetcode.nvim opts to see http responses, but im guessing it won't be any different then this https://github.com/kawre/leetcode.nvim/issues/69.
can you check if latest commit changed anything?
can you check if latest commit changed anything?
I just pulled the latest commit and got this error:
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.