-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get_my_inventory not working "Success value should be 1" #345
Comments
Steam was updated today, this is probably why your error occurs |
I created a simple example and tested it. |
Perhaps the error occurs due to the fact that you specify the path to mafile and not to steam_guard.json Do not send the code as a screenshot, it is better to send it in text so that it can be easily copied |
@Dandelion101
maFile : I use Files created using Steam Desktop Auth(SDA), I repeat, everything worked until last night) Error 1:
|
I am using python version 3.8.10 and 3.10.11. It doesn 't work on both of them . I tried to delete and recreate the api_key. It didn't help. |
I'm using the buy item method from the steampy library. And for the last two days I’ve been receiving this answer: {'message': 'There was a problem purchasing your item. The listing may have been removed. Refresh the page and try again.'} 2024-01-19 18:26:33,196 - my_logger - WARNING - There was a problem buying this item. Message: There was a problem buying this item. Message: There was a problem purchasing your item. The listing may have been removed. Refresh the page and try again. I just can’t cope with this problem, can someone tell me something? |
Steam update came out last night |
The same problem. Have you found any solutions? |
For some reason, get_my_inventory works every other time. Also, I noticed that .is_session_alive() does not work in 90% of cases. |
I've got same error today on prod server, but in development server with the same account and library version it works fine. |
This problem appeared last night.
Steampy v1.1.1
How fix?
The text was updated successfully, but these errors were encountered: