ThatOneLukas
Comments
@Donuts1000 Thank you! Got it working by installing `pass` and `pass-secret` (AUR) as I think `gnome-keyring` is bloat in my opinion
Issue still persists on launcher version 2.2.3963.
@Inky19 If I rename the key to `clientToken` it changes back to `mojangClientToken`. Interesting thing is that the client token is required for authentication/getting access token (I can still join servers). I have a newly bought (Microsoft) account in the launcher but I have to log in to that too. (Edit: Ugh backticks don't work for inline code)
Could this be related to the client token being at the key mojangClientToken instead of clientToken in launcher_accounts.json?
When the launcher is opened and I log in the accessToken key+value pair in launcher_accounts.json is added for my account but it is empty.
I have the same issue, launcher installed from the AUR and same failure to get clientToken in the log. Account type is Mojang and Java is openjdk 16.0.1 2021-04-20. How do I close MCL-18997?
@nothing99 Similarily to MCL-18924 the launcher is installed from the AUR, same failure to get token in launcher_log.txt and when moving/renaming the .minecraft directory and then reinstalling the launcher the issue still persists.
@nothing999 I do not think that this is a duplicate since it happens every time I restart the launcher, not when the computer is restarted.
Could an option be added to store the token in a separate way?