mojira.dev
MCL-12347

Minecraft Launcher sometimes forgets account information on load

sporadically, the launcher ‘forgets’ all account details (of the logged in account) and you have to reenter login information. This seems to only happen with the last logged in profile, and seemingly at random. It might be duplicatable easily on computer restart?

Linked issues

MC-164134 "Keep me logged in" not working Resolved MC-164286 Launcher logs me out every now and then Resolved MC-164373 Why do I need to log in everytime I try to play minecraft Resolved MC-164388 log in Resolved MC-218544 Logging Out after quit Resolved

Attachments

Comments 28

This happened to me several times as well in the past few days. But I didn't think of looking at the launcher log file in time.

Next time this happens, I’ll check the log files before logging in

can confirm this has happend to me multiple times now - always the last logged in account, doesnt seem to be a pc restart that does it as restarting the luncher triggered it, i find it intreasing that the luncher is kinda aware its forget the account as i opens the enter details screen and not just switch to  different account thats still logged in

forgot to check log files tho sorry

Experiencing the same problem

Everything is normal in the log file beside this:

[Error: 2019-10-20 17:40:25.2943514: LauncherController.cpp(388)] NO_USER_SELECTED

Maybe the access token expires? - because it doesn't happen if you stop and start the launcher immediately...

Edit:
I also noticed that the launcher_profiles.json doesn't contain a profileId and a userId under authenticationDatabase/<SomeHash>/properties:

{
  "analyticsFailCount" : 0,
  "analyticsToken" : "<analyticsToken>",
  "authenticationDatabase" : {
    "bd49bb76f93cbd155eee1e85724ad227" : {
      "accessToken" : "<accessToken>",
      "profiles" : {
        "2770e2ff3f19438682ea1fcc370ffc94" : {
          "displayName" : "<displayName>"
        }
      },
      "properties" : 
      [
        {
          "name" : "registrationCountry",
          "profileId" : "", //←!!!
          "userId" : "", //←!!!
          "value" : "DE"
        }
      ],
      "username" : "<email>"
    }
  },
  "clientToken" : "<clientToken>",
  "launcherVersion" : {
    "format" : 21,
    "name" : "2.1.3674",
    "profilesFormat" : 2
  },
  "profiles" : {
    //...
  },
  "selectedUser" : {
    "account" : "bd49bb76f93cbd155eee1e85724ad227",
    "profile" : "2770e2ff3f19438682ea1fcc370ffc94"
  },
  "settings" : {
    "channel" : "release",
    "crashAssistance" : false,
    "enableAdvanced" : true,
    "enableAnalytics" : false,
    "enableHistorical" : true,
    "enableReleases" : true,
    "enableSnapshots" : true,
    "keepLauncherOpen" : true,
    "locale" : "de-DE",
    "profileSorting" : "ByLastPlayed",
    "showGameLog" : true,
    "showMenu" : true,
    "soundOn" : false
  }
}

Which leads me to the assumption that the clientToken stays active for a amount of time (maybe one day?), but when it expires the launcher is unable to get a new one from the servers with the accessToken.

EDIT2:
Just found this out:
If you delete clientToken (replace "<Token>" with ""), the launcher doesn't generate a new one, beside having a accessToken and "remeberMe" enabled, you have to reenter your credentials.

18 more comments

This was a legit issue, albeit not launcher specific. It has since been fixed.

I just had this happen on

[media]

Edit:

For clarification, it seemed to lose any record of the latest account logged in and the user didn't show up in the accounts list. On the previous time this happened it completely lost both accounts and their credentials had to completely be reentered.

I would like to reopen this issue. I am experiencing it with

Launcher 2.1.15168
Bootstrap 777
UI 5555

I just had this happen again today. Could this please be reopened and looked into.

So, just had this happen again, I think it's related to when the launcher updates itself.

vashts240

(Unassigned)

Confirmed

Retrieved