All Activity

Recently I started getting the error below when trying to confirm trades. Error: Could not act on confirmation Is it perhaps related to this issue? If so, can it only be fixed manually by logging into each steam account or is there a way to fix it via the module?

Moved to correct forum - this was in an update to node-steam-session, not node-steam-user. As far as I've seen, this parameter is present for any GET request issued by the mobile app to the WebAPI. Confirmations don't go through the API so it's not present for those requests. In practice, the only request that origin=SteamMobile is added to in steam-session is the initial GetPasswordRSAPublicKey request as that's the only GET request issued when using EAuthTokenPlatformType.MobileApp.

The latest update (1.9.4) adds a new "origin=SteamMobile" parameter to mobile GET requests. Is this parameter only used for requests that are part of the node-steam-user library / login process or is this new parameter used for other mobile GET requests, such as retrieving pending confirmations, as well?

really? that simple??

Works for me.

Also, I’m a bit confused about how this class was instantiated before. I can see how `EconItem` is created, but I’m not sure where `CEconItem` comes from or how it was initialized previously. Could you clarify how this used to work?

Hi guys! What is the best way for me to check if a user (i have their steamid64) has activated their mobile steam guard authenticator and no longer have a 15 days trade probation? for now, im using this method: Bot.tradeOfferManager.createOffer(tradeURL).getUserDetails((err, me, them) => { const error = err?.message?.toLocaleLowerCase(); if (error) console.log(`ERROR in checkForErrors for user: ${userID}: ${error}`); if (error?.includes('inventory privacy')) return resolve('private_inventory'); if (error?.includes('is no longer valid')) return resolve('invalid_trade_url'); if (!options.checkTradeBan) return resolve(''); if (them?.escrowDays > 0) return resolve('steam_guard_not_activated'); if (them?.probation) return resolve('trade_ban'); return resolve(''); }); by the way, I 100% know this is a bad code. but i don't know how else should i do this. (and also, it breaks from time to time and i have to hotfix it. it's broken now and I just want to do it properly, once and for all)

my bad, I've changed log level of newOffer to debug, and didn't check debug logs

Hi! Right now, the contextid is coming as `16` instead of `2`, as it used to be before. Because of this, the `cache_expiration` field is not being set. Looking at the code here, can we just add a similar check for `contextid == 16` to set the cache_expiration as well? Or is there a better way to handle this with the new contextid? Thanks!

There's no reason it wouldn't, a counter-offer is a new trade offer like any other.

Yes, that's what I said.

After cs2 trade hold update my bot stopped receiving "newOffer" event for counteroffers

the trade offer is not updated during the rollback, only trade. Thus, GetTradeStatus with tradeid from GetTradeOffer returns the correct status 12

Am I trippin or steam added new fields to GetTradeOffer API? eresult: 1 delay_settlement: true

Internal behavior changes when logging on with EAuthTokenPlatFormType.MobileApp Updated reported app version from 3.0.0 to 3.10.3 Updated reported device name from Galaxy S22 to Galaxy S25 Added origin=SteamMobile query string parameter to match official app behavior Full Changelog: v1.9.3...v1.9.4 View on GitHub

Already known, see this thread:

As you've figured out, the actual trade offer stays in the Accepted state, but the underlying trade gets rolled back. steam-tradeoffer-manager doesn't poll GetTradeHistory at all right now, so adding support for detecting these rolled back trades would incur additional requests. I'm still working on thinking of the best way to go about this, but for now I suggest you do your own GetTradeHistory polling.

https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.49.0 As far as I can tell, clicking that button in the popup (which is what acknowledgeTradeProtection() does) is all that's needed, and it only needs to be done once per account. If you've already clicked the button on the account(s) you use to trade, you shouldn't need to do anything more.

Added acknowledgeTradeProtection() method Full Changelog: v3.48.8...v3.49.0 View on GitHub

Thanks, I wasnt aware there was a different contextid for trade protected items.

The sentOfferChanged event does not emit when an offer is rolled back. Please confirm if this is already known, or if this can be addressed in an update. Thanks.

Yes is a bit difficult to use GetTradeHistory, but for the moment this is the only solution, until steam will solve the endpoint. I just implemented GetTradeHistory to track also the rolled back trades (state == 12) and is working. You just have to get the trade history and find that one with your trade id, and you will get the state and the items also.

yep, if you will find other endpoint that will give info about trades on hold let us all know. GetTradeHistory isn't convenient for our use case

I checked also that API endpoint you mention and still same state id, 3 (Completed). Now I thing that is something from steam, they didnt update properly the system, or they didnt update this endpoint. I think that node-steam-tradeoffer-manager module is also using this endpoint, so may not be a problem from module, but from steam. As a conclusion, the trade state is updated only on trade history API: https://api.steampowered.com/IEconService/GetTradeHistory/v1

Thanks doc. Your'e a life saver as always. For now, as a temporary fix, I just logged into the bot using the steam client (or a web browser) and accepted the pop up manually in trade history page. It's working fine for now. currently waiting for the new update. ❤️