-
Notifications
You must be signed in to change notification settings - Fork 667
連cookie都無法登入了? #908
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
Comments
Same issue |
same. |
same too,bro . I try all night . |
cannot login with GitHub, able to submit within past 24 hours but not now. |
same issue, not able to log in both with cookie, linkedin, as well as github |
thought it was just me, was even working in the morning, stopped working in the afternoon |
yeah same logging in with github and cookie is no longer working as of a few hours ago |
same issue! |
this is a very helpful extension, hope it can be fixed soon |
guys I can log in now |
Value: |
This bug comes up again.... |
I'm experiencing the same issue; it used to work well before, but now I can't log in with a cookie anymore. I will try the method suggested by @g-akshay.If it's successful, I will provide an update. |
any luck? |
Update:
It seems the issue might not be with the extension, but rather how the LeetCode website handles authentication. |
I also had this issue come up when @HOZH and @billpku experienced it. I did some debugging, and it looks like when leetcode tries to submit the solution, an HTML page was sent as a response, saying something like "hang on a second" in the title. I just console log'ed the response html and wasn't able to open it in a browser because the linked javascript couldnt' be found. I tried linkedin, github, and cookie logins while this issue was occurring and nothing worked. Only thing that worked was waiting two days, just like @billpku experienced. And now that the issue is gone, signing in with any method is successful |
以往用cookie都能順利登入,但今天卻不行了,有人遇到一樣的問題嗎?
錯誤訊息顯示如下
let s = args.map(x => x.toString()).join(' ');
^
The text was updated successfully, but these errors were encountered: