You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed it by replacing WebAuth with login as Steam Client, but it's cookies expires fast, like 3-4 mins for me, so added relogin() func every time it did
UPD: noticed that relogin isn't refresh cookies, so it needs full relog using login() or cli_login(), that causes some bad feeling because of 2FA codes. Waiting for fix or another suggestions what to do
Mabye somebody knows how to login using shared_secred code or steamguard file?
Same issue with me, I think Steam is trying to reduce bot recently.
I check reciving message from WebAuth post to "https://steamcommunity.com/login/dologin/", and got "429 Too Many Requests". So json parser can't work properly.
Can't replicate the OPs error, I get the correct data from the RSA, but login responds with 429. My guess is that they've decomissioned the old login flow. This mean I have to investigate the new one, and see how that works.
Fixed it by replacing WebAuth with login as Steam Client, but it's cookies expires fast, like 3-4 mins for me, so added relogin() func every time it did
That web sessions is bound the the steam client session, which I'm guessing you didn't keep alive, thus it timed out and both were expired. Calling client.idle() every minute or so, should be sufficient to keep it alive.
Can't replicate the OPs error, I get the correct data from the RSA, but login responds with 429. My guess is that they've decomissioned the old login flow. This mean I have to investigate the new one, and see how that works.
Fixed it by replacing WebAuth with login as Steam Client, but it's cookies expires fast, like 3-4 mins for me, so added relogin() func every time it did
That web sessions is bound the the steam client session, which I'm guessing you didn't keep alive, thus it timed out and both were expired. Calling client.idle() every minute or so, should be sufficient to keep it alive.
Seems like client.idle() worked for me, but anyway i'll wait for new webauth, because it is more suitable for my project. Btw, can you explain what does actually idle() does?
Btw, can you explain what does actually idle() does?
SteamClient uses gevent for cooperative multasking, you need to yield to the event loop so other tasks can be processed, such as sending/receiving messages, client heartbeat, etc.
Activity
jethro1412 commentedon Dec 23, 2022
Version 1.4.3 also affected
Marcelzocker999 commentedon Dec 23, 2022
Same for me using WebAuth
/usr/lib/python3.8/json/decoder.py in raw_decode(self, s, idx)
353 obj, end = self.scan_once(s, idx)
354 except StopIteration as err:
--> 355 raise JSONDecodeError("Expecting value", s, err.value) from None
356 return obj, end
JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Gobot1234 commentedon Dec 23, 2022
I think the easiest fix for this ATM is to change the post to a get request and switch to using params instead of data, that seems to work for me
Marcelzocker999 commentedon Dec 23, 2022
Fixed it by replacing WebAuth with login as Steam Client, but it's cookies expires fast, like 3-4 mins for me, so added relogin() func every time it did
UPD: noticed that relogin isn't refresh cookies, so it needs full relog using login() or cli_login(), that causes some bad feeling because of 2FA codes. Waiting for fix or another suggestions what to do
Mabye somebody knows how to login using shared_secred code or steamguard file?
Mije36 commentedon Dec 24, 2022
Same issue with me, I think Steam is trying to reduce bot recently.
I check reciving message from WebAuth post to "https://steamcommunity.com/login/dologin/", and got "429 Too Many Requests". So json parser can't work properly.
Gobot1234 commentedon Dec 24, 2022
It is entirely possible that Steam are just phasing out this endpoint considering AFAIK it's not used by official code anymore
rossengeorgiev commentedon Dec 24, 2022
Can't replicate the OPs error, I get the correct data from the RSA, but login responds with 429. My guess is that they've decomissioned the old login flow. This mean I have to investigate the new one, and see how that works.
That web sessions is bound the the steam client session, which I'm guessing you didn't keep alive, thus it timed out and both were expired. Calling
client.idle()every minute or so, should be sufficient to keep it alive.Marcelzocker999 commentedon Dec 25, 2022
Seems like
client.idle()worked for me, but anyway i'll wait for new webauth, because it is more suitable for my project. Btw, can you explain what does actuallyidle()does?rossengeorgiev commentedon Dec 25, 2022
SteamClientuses gevent for cooperative multasking, you need to yield to the event loop so other tasks can be processed, such as sending/receiving messages, client heartbeat, etc.Kein commentedon Jan 10, 2023
So is it like
RunCallbacksin the original SDK/API?