Dr. McKay

Have you noticed whether anything else (for example, name and/or market_name) was missing when you experienced app_data being gone?

I think that for v2 I'm going to make successful API calls always return data instead of "Data temporarily unavailable" (e.g. when the offer appears to be empty), but hold off on emitting events if that's the current state of the data.

Try using getTimeOffset to see if your clock isn't close enough to Steam's. If that doesn't work, make certain you're using the correct secret (shared_secret, it should be base64).

Is your clock right?

Add this to your code and see what it prints out: steam.on('debug', console.log);

No, the event won't fire if there isn't any HTTP traffic going on. But if you pass the SteamCommunity instance to the constructor of TradeOfferManager, then the manager will use that community for its HTTP requests and so no-session requests triggered by the manager will fire the event.

That warning is normal. It installed successfully.

https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#sessionexpired And yes, refreshing cookies every hour or so isn't a bad idea.

Thanks!

Yeah, that should work.

It'll be an empty array if you received nothing. You need to use the trade ID, not the trade offer ID.

I beg your pardon?

What did you use to start confirmation checking?

Some items can be missing a market_hash_name under normal circumstances (e.g. some H1Z1 items). If name is empty that's a pretty dead giveaway.

If you'd read that page that was linked, you'd know that that's exactly what confirmation polling does.

You should try again later.

You need to re-logon every so often to refresh your session. Using steam-user all you need to do is call webLogOn() periodically (or when stuff starts to break).

All you can do is go online using chatLogon. You can't go "in-game".

Get a bunch of IPs.

Yes, steamcommunity.com has a global rate limit, which applies to the inventory endpoint. I don't know what the limit is exactly, but there is one and you'll start getting 429 if you hit it.

The documentation suggests that you don't go lower than 10 seconds.

Timeouts are just timeouts. There isn't anything that can be done about them, unfortunately. I'm considering removing the "Data temporarily unavailable" error. That error is returned when the API call succeeds, but the returned offer has no items on either side. I think there's probably a better way to handle that.

Which polling error is more frequent?

Please tell me what the actual errors are.

Yes.