GameMaker-Bugs
GameMaker-Bugs copied to clipboard
YoYoGames
Licensing: Greatly increased rate of randomly getting logged-out in 2024.14.0
Description
Since the 2024.14 update, there's been a much higher rate of people opening GM to find themselves logged out. It just happened to me as well. It doesn't happen while GM is open, but any time GM is restarted there's a chance of login status being lost. It's happening for both legacy and Opera accounts. Earlier today in particular we had a lot of people coming to the help channels confused because their settings were gone (as a result of being logged out)
Steps To Reproduce
Restart GM. Unfortunately it's not 100% repro, and I don't know what specific factor determines if you get logged out or not.
Which version of GameMaker are you reporting this issue for?
IDE v2024.14.0.207 Runtime v2024.14.0.251
Which operating system(s) are you seeing the problem on?
Windows 10.0.26100.0
1000effd-c663-44a7-b050-2afc3ff5796b
There have been a number of recent licensing changes on the web side as well, including this week. Some of these could well have invalidated old login sessions.
This should mean it's a temporary issue and there is nothing further to do here; however, interesting if the feedback you're getting is that it's only affecting those on 2024.14. (Do wonder if that's just because people in that group are more likely to be early-adopters, etc., and so there are only small numbers of people not on 2024.14 ;) )
We will monitor if any change seems required.
The constant logouts are still happening, I'm getting logged out every single day, but only in monthly. Not getting logged out of beta. I've also talked to others who have gotten logged out multiple times today.
I have been experiencing this issue also. Full log: https://api.gamemaker.io/api/github/downloads/3fbfe52d-edf4-4686-9762-99532dc4f5b0 (Note I had to login again to update the sample)
I've been experiencing this when updating my monthly builds - though not when closing and reopening it. Full log: https://api.gamemaker.io/api/github/downloads/ece49e3c-5e3d-4d59-a232-51692b239063 (Note that similar to Esther, I had to login again to upload sample)
Ok so a few things form the logs.
It going through the auth provider path and getting a platform licence. This may be the ide not respecting the expired at.
Next up I am seeing called to yoyogames.com for a token refresh, this is not the correct refresh for auto provider tokens.
So it looks like an issue with the IDE when using the auth provider path. It'll need a coretech debug on startup. And likely they just need to remove those requests.
Uploading this on behalf of someone else. The ui.log files that should be checked are in the AttachedFiles folder - https://api.gamemaker.io/api/github/downloads/8662da1d-2039-48be-8d76-e78394cf1acf
It's consistent for me. A rebooted PC will have logged me out of Game Maker's latest update. I have a Legacy account.
It also doesn't load my Layouts settings until I close and restart the IDE, after being logged back in.
I just updated to 2024.14.1 and got logged out. I was logged in before updating. No computer restart or anything, just updated with the auto-updater.
@konjerk I assume when you are logging in it is taking you via the auth.gamemaker.io path aye?
@code-bunny I wouldn't know its path to verification, seeing as Legacy log-in doesn't ever have me leave the IDE.
@konjerk thanks for that, so that suggests something different is going on for you. There is a way to do legacy login outside the IDE, but if everything is in the normal IDE it's a different issue to the others reported here.
Updating to .14.1 will log you you out that first time, as there is a change in licensing system, but you should be able to log-in that one time and remain logged-in just fine thereafter.
Not loading your custom project layouts properly after logging-in is a separate bug and should be fixed already for the .2 release/.200 Betas starting soon.
I've experienced logging out in pre-14.0 releases (1400 betas and 2024.13 stable).
Haven't gotten logged out since 2024.14.1 released, so seems it may have been a 2024.14.0 specific issue