Dr. McKay

Update to 4.19.7 please.

Correct, when a new client session is established, a web session is automatically negotiated.

Go ahead and try v4.19.6 please.

Okay, this is interesting. Are you running your app on slow hardware, maybe a Raspberry Pi? It looks like Steam is sending back gzipped responses, and for some reason some of these responses are taking multiple seconds to ungzip. This is resulting in the timer for ClientLogOnResponse elapsing while ungzipping, resulting in a relog. But once the account gets relogged, the old ClientLogOnResponse comes in and it thinks it's logged on when it isn't. log.txt

That means that Steam didn't respond to the add-friend request within 10 seconds. I don't know why this would happen other than Steam just being unreliable.

You would want to use a loop to request inventories until Steam no longer reports that more items are available, and use array_merge to combine the result pages.

Searching the market is the only way to get a list of available assets for an app, without using inventories or third-party sites.

Before you call webLogOn, check to see if the client.steamID property is null. If it is, then you're not connected to Steam, and that's likely the reason why your web session expired.

You'd need to use the WebAPI for that.

The way the CS:GO item system works is pretty insane and it's a fool's errand to try to decode item names out of the data sent back from the GC. Your best bet is to keep track of what item IDs correspond to which items before you put them in the casket, then refer back to that mapping when you want to retrieve stuff. The CS:GO game client only removes one item from the casket at a time, and waits until it's removed before removing another one. You probably shouldn't try to remove items much faster than that, or else you might get on Valve's bad side.

Thanks, that's a little helpful but I'm still having trouble tracking down exactly what's happening. Please update to steam-user v4.19.5 and also log the debug-verbose event in the same manner as the debug event.

AMGetClanMembers might not be a protobuf message. In any case, it might not work at all, and even if it does it's most likely only going to give you either a list or a count of members in a Steam group, not followers of an app. It may not be possible to get the number of followers of an app.

If you aren't using the cancelTime option, there shouldn't be any reason why the module would cancel trades on its own. The trades are going into the Canceled state and not Declined, right? Maybe whatever you're using to confirm the trades is wigging out and canceling them from there...

How frequently does this happen? If it happens fairly frequently, can you add this so I can see the debug output? client.on('debug', (msg) => console.log(msg)); It sounds plausible to me that something is preventing the API request from going through, but having the debug output would confirm this.

It seems to me that CMsgFSGetFollowerCount is for getting the follower count of a user, not of an app.

I'd recommend changing your Steam account password and API key. It sounds like it's possible that somebody else has access to your account.

You're using the automatic confirmation checker, which has had this notice on its documentation page for 3.5 years:

Swap the order of err and personas.

No, that's a very bad idea.

Correct. If other sites are showing players' stats, they're getting them some other way.

No, that's not possible. Otherwise every third-party site you sign into using Steam would be able to log into your account and do nasty things to you. All you get from Steam's OpenID login is the user's SteamID, nothing more.

You're missing the first err argument to the getPersonas callback.

Let me see the code in question, please.

The documentation is on GitHub. I would need to see the entire error output to help you with that at all.

What do you mean by getPersonas sends you mistakes?