Dr. McKay

As per the documentation: If it's the first emit, accountInfo won't be defined yet. The data is available as an event argument.

You aren't logged into the website in the loggedOn event. Wait for webSession, call community.setCookies, then start the confirmation checker (although I advise against using it, it's better to just confirm as needed).

This issue arising after updating is merely a coincidence. It appears that in today's Steam maintenance, Valve added a new binary KV node type. Please run npm update and let me know if that doesn't fix it.

Yes, it appears that Steam no longer sends back the SteamID when an account is created successfully. I'll update the readme accordingly.

Then why are you trying to check confirmations as part of the login process? Show your code.

You're not really doing it right. steam-user includes everything from steam (and SteamFriends). You don't need to create SteamClient or SteamFriends objects yourself. Additionally, steam-user automatically prompts for Steam Guard codes so you don't need to handle that case yourself (although things are going to get messy if you're starting up multiple bots at the same time that need codes).

Are you logged in?

Please show your code.

Yeah. Unfortunately, that just happens sometimes because Valve sucks. You'll just have to figure out ways to deal with it.

Wait, I might be slightly confused. Does an item with the ID in the receipt exist, or is there just no such item in the inventory with the ID given by the receipt when the issue happens?

Is it online on Steam?

How do you know that specific items map to a different asset ID, if the asset ID reported by the receipt exists?

Show your code. I suspect you aren't passing a function as the first argument to offer.send().

There is no need to call community.setCookies since you're using manager.setCookies and you passed the SteamCommunity instance to the TradeOfferManager constructor. Can you add some output to the webSession event to make sure that's getting emitted properly?

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/blob/master/examples/storehouse-steam.js You should be able to relatively easily modify this example to only accept offers where you don't give any items (e.g. offer.itemsToGive == 0)

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#getofferscontainingitemsitems-includeinactive-callback Please read the documentation.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#getoffersfilterhistoricalcutoff-callback Please read the documentation.

steam-tradeoffer-manager never had anything to do with this, so there isn't anything to update.

See cancelTime here: https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#constructoroptions

I suggest you check again.

All the information I have is that it doesn't work. http://apistatus.steam.pm

A pretty easy way to invalidate your session: community.setCookies(["steamLogin=invalid", "steamLoginSecure=invalid"]);

You seem to be under the mistaken impression that any of us work for Valve.

42 = NoMatch Did you perhaps set the apiKey property manually?

https://support.steampowered.com/kb_article.php?ref=3330-IAGK-7663