Dr. McKay

You can never accept an offer you create. Accepting is an action that can only be done by the trade recipient. If this happens when accepting incoming trades, that means they aren't active. They've already been accepted or declined or canceled.

I'd avoid outright saying it. Just say that you have a lot of confirmations on your device for trades that no longer exist, and give that error message that you see in the title.

Please dump your licenses property to JSON and either post it here or PM it to me.

Wrong module. This isn't node-steam-tradeoffers.

You probably need to contact Steam Support.

I honestly have no idea what you're asking. The statistics in Steam groups aren't always up-to-date or correct.

I don't think family sharing applies since it's per-machine. Are you sure that they aren't just free apps?

I'm not available for work.

If Steam is down, you can't log in. I don't understand where the confusion is. Wait for Steam to come back online, and the client will reconnect on its own and emit webSession.

If you're using node-steam-user, it will automatically reconnect when it gets disconnected. You can handle the event where you need a Steam Guard code by setting the promptSteamGuardCode option to false and handling the steamGuard event.

You need to call webLogOn with no arguments, and call it on the same Steam client as the one that's already connected to Steam.

This is what the amount property is for.

Read the second half of this.

That's the correct method to use, but you can't use it if you aren't currently connected to Steam (e.g. because Steam is down). That's what's throwing that error.

The code in your first post will absolutely work. Regarding your second post, are you passing the 64-bit SteamID as a string instead of a number? JavaScript can't handle integers that are that big.

You're trying to relog the web session while Steam is down. Don't do that, and just wait for Steam to come back. It will emit webSession automatically once it reconnects successfully.

Has your web session expired?

relog will only work if you're currently logged on (steamID is not null). If you're not logged on (steamID is null), logOn.

There's no reason why that shouldn't work, besides the sentry not being valid for your account.

It won't automatically relogin if you explicitly log off.

None of the code you posted would result in that error. That said, you want to use webLogOn instead of logOn, assuming client is a node-steam-user instance. The web session is distinct from the client session. It connects as a client, then uses that client session to obtain cookies for a web session. The web session expires but the client session doesn't, so webLogOn just gets new cookies using that same client session.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#acceptskipstateupdate-callback Async events would be pretty difficult, seeing as EventEmitter is synchronous.

Yes, it's caused by different device IDs.

You're most likely trying to reuse a code. You can't do that.

You can't use confirmations on two devices at once. I suspect that you're using a physical mobile phone to confirm some trades. This will cause problems like the one you describe (confirmations don't always show up).