Closed henrydatei closed 1 year ago
The error arose when attempting to create booster packs, because the sessionid
cookie could not be found.
To fix this issue, you need to fill in your cookies in personal_info.json
, especially sessionid
.
Once this is done, you could run the script again after toggling these boolean values to False
to save time:
https://github.com/woctezuma/steam-market/blob/57c717118fed8c660bd830f51f0ccfaf45fd5e40/market_arbitrage.py#L498-L499
That being said, I am surprised that the script could run this far without the cookies.
Did you fill in some of the info, but not all of the info, e.g. steamLoginSecure
but not sessionid
? 🤔 Indeed, if the sessionid
cookie had been available but obsolete, then the error would have been different. Here, it seems that the value of the sessionid
cookie was not filled in at all, but some of the rest of the cookies must have been correctly filled in, for the script to run this far.
I have done this. Literally 5 minutes before I ran the scriptVon meinem iPhone gesendetAm 19.01.2023 um 16:15 schrieb Wok @.***>: You need to fill in your cookies in personal_info.json.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Interesting.
Then maybe the script updated the cookie values in the JSON file and erased the value of
Edit: After looking at the code again, I don't think the dictionary entry for sessionid
which you had previously filled in. Not sure how this would be possible.sessionid
could be deleted when updating cookies.
Could you check which fields currently exist in the JSON file personal_info.json
?
{
"steamLoginSecure": "76561***"
}
Did you fill in some of the info, but not all of the info, e.g.
steamLoginSecure
but notsessionid
? 🤔 Indeed, if thesessionid
cookie had been available but obsolete, then the error would have been different. Here, it seems that the value of thesessionid
cookie was not filled in at all, but some of the rest of the cookies must have been correctly filled in, for the script to run this far.
As you see above I didn't fill in the sessionid
value because the README file just said I need the value for steamLoginSecure
(or maybe I was just blind and didn't see it 😄 )
Did you fill in some of the info, but not all of the info, e.g.
steamLoginSecure
but notsessionid
? 🤔 Indeed, if thesessionid
cookie had been available but obsolete, then the error would have been different. Here, it seems that the value of thesessionid
cookie was not filled in at all, but some of the rest of the cookies must have been correctly filled in, for the script to run this far.As you see above I didn't fill in the
sessionid
value because the README file just said I need the value forsteamLoginSecure
(or maybe I was just blind and didn't see it 😄 )
Ah, I see where the confusion could come from.
Indeed, the README only mentions steamLoginSecure
in the section called How to fill-in your cookie information
. Based on the run of the script, this seems right: the script worked fine with relaxed rate-limits by solely using the steamLoginSecure
cookie, and the script only failed at the very end when it was time to create booster packs.
The sessionid
is mentioned a bit below in the README in an annotation (NB²
) "to automate the creation and sale of booster packs". So I understand how it could be overlooked.
On a side-note, it is always possible to perform this last step (creation and sale of booster packs) manually by going to this page to create packs, and then manually listing packs on the Steam Market. This is especially relevant if there are only a few packs.
I ran
python3 market_arbitrage.py
and I got the following errorShortened console output: