Dr. McKay

I'm not sure what circumstances automatically enable email Steam Guard. If you already have a valid refresh token, then yeah, you can use steam-session to get new cookies.

There's no reason not to.

I very much wouldn't be surprised if Valve removed the ability to use sentry files with the auth server last week. They're seemingly cleaning up deprecated transitional code. Why can't you just get a machine auth token going forward?

Versions?

npm update should take care of this for you.

Decode the JWT and check the exp parameter, but be aware that tokens can be invalidated server-side at Valve's discretion, and nobody's sure exactly what makes that happen besides IP changes.

This is a known incompatibility in Electron that the Electron team has acknowledged and refused to fix. Package maintainers cannot consider all possible incompatibilities in all possible runtime environments; you'd do well to only use third-party modules in your main process rather than in a Node-enabled renderer process. You're ultimately trying to run code written for Node.js in an environment that's only mostly API-compatible with Node.js. I'll try to add a workaround when I get to it.

Don't care.

Works fine for me. I'm not going to provide support for automated abuse reporting.

npm update

You can't.

What do you mean by "use it with steam-user"?

npm update

Works fine for me. Why are you doing all that and not just calling community.setCookies()?

This is expected behavior. You can only use a token generated with EAuthTokenPlatformType.SteamClient with steam-user. This is expected behavior. renewRefreshToken() does not work for EAuthTokenPlatformType.WebBrowser.

This is a known issue, see: https://github.com/DoctorMcKay/node-steamcommunity/issues/321 community.login isn't going to work until I can finish the v4 rewrite. Until then, you can either use steam-session or steam-user to get login cookies for use with steamcommunity.

The solution is to stop using unsupported, deprecated libraries and migrate to things that are supported. For logging into web, steam-session is what you're looking for.

Update steam-user to v4.29.0 or later using npm.

Update to v4.29.0 or later.

client.setPersona(SteamUser.Steam.EPersonaState.Online, Config.access.setNickname) This line tells me that you're using steam-user v3.x.x or earlier, as SteamUser.Steam was removed in v4.0.0.

Version?

You can't log on with SteamUser using cookies; they're only for web sessions, which SteamUser isn't using. SteamUser will automatically save your machine authorization as long as local storage is available (which it should be in most cases), but if you need to manually handle machine auths, check out this section in the docs. You can also use a refresh token to log on, which is sort of like SteamUser's version of a cookie. That's documented here.

Technically only the owner of the asset is supposed to see the tradable after time, but you can use the ISteamEconomy/GetAssetClassInfo WebAPI method to retrieve those owner descriptions.

No, this isn't possible at the moment, but it could be possible to add support for doing that.