Expected behavior

When logging in with Microsoft, I expected to log in with the account I originally logged in to with the minecraft session.

Observed/actual behavior

I get logged in with a different account, usually the one of the session I launched latest

Steps/models to reproduce

I haven't fully managed to reproduce the issue purposefully yet, but here's what I've done when it has happened

• Use a launcher that allows launching multiple instances of Minecraft (e.g. Modrinth, what I used)
• Launch 2 separate instances on 2 different accounts, both of them including the AuthMe mod, with some interval of time between them
• Let the first session expire, then refresh the session with AuthMe
• First session now uses second session's account

Version

AuthMe: 8.0.0
Fabric Loader: 0.15.3
Game Version: 1.20.4

Agreements

• I am running the latest version of the mod.
• My version of Minecraft is supported.
• I have searched for and ensured there isn't already an open issue regarding this.

Other

No response

Hi,

Have you tried holding Ctrl (in Minecraft) when you click to login with Microsoft? That should force the single sign-on to pause on Microsoft's end and ask to choose an account.

Alright, I tried it and it worked, thanks for the help!
I wonder if there's perhaps a way to cache or save the account that the client originally logged in with? That way it'll automatically use that instead of having to pick an account every time people use 2+ accounts.

I attempted to create a fix for the issue in pull request #123. After the first session refresh using AuthMe, it should store the refresh token for the session for the next authorization. (This might not fix it on first login, but should fix on second login onwards)