Closed calendulish closed 2 months ago
The UpdateAuthSessionWithSteamGuardCode accepts the code on relogin process, with SteamGameServer reusing the same code later (wrong already). Apparently the wrong code expires at 1s or less before the call. Is it caused by the server time cache mechanism?
Describe the bug There's a minor desync in steamguard module when generating codes after a "full relogin". Codes are automatically fixed on the second try.
To Reproduce Steps to reproduce the behavior:
Desktop (please complete the following information):
Additional context Further investigation is needed to determine if the cause is the server time desync (we still need to check the server time?!) or the delay between api execution and the generation of the codes (aren't we already adding the function time on stlib?!).