-
Notifications
You must be signed in to change notification settings - Fork 6
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
GDLauncher sign in loop, cannot log in to Microsoft account #342
Comments
Just installed 2.0.9 on my Manjaro GNOME installation and encountering the same exact issue. Newbie question: Where do I find the logs for the AppImage version? |
Same issues here, on Arch. |
I have the same issue. Just downloaded from official site using appimage on ubuntu 22.04. |
Ok, just re-installed using Manjaro '"Add/Remove Software". It was not a new version, but I was able to sign in with Microsoft today. Give it another try my good people. |
I am having this same issue on Windows 11. Interestingly, I get the same issue when I install version 2.0.6 from an exe that was sitting in my downloads from April. |
Version v2.0.20 from the Discord server fixes this issue. For those not in the server it seems it will be released on auto update soon. |
do you know when it will be released ? |
I am not sure. It was not stated in the announcement. |
It's currently rolled out to 30% of our users, will increase it to 100% later today |
Since last Thursday, I cannot log in to my Microsoft account using GDLauncher. I'm getting asked to approve login request with Microsoft Authenticator, I approve the request, then GDLauncher just asks me to sign in again. I cannot find any error message in any log. I tried with both version 1 and version 2 and getting same issue. From searches on Google, I found several posts about login issues with Microsoft account, but they date back to 2021, so that seems a new issue. I cannot keep actively using Linux if I have to switch back to CurseForge, the only launcher that works reliably without having me move my saves from one launcher to another periodically.
The text was updated successfully, but these errors were encountered: