Rodrigo

Sometimes my application throws the "Already logged on elsewhere" error randomly. I think it is during some re-login implementation of the lib + my setup.

What has been happening is that this error is being thrown out of nowhere and I don't exactly know how to stop it from shutting down my application. I have catches everywhere and its not being catch by anything.

If I put a event handler on the client.on("error") event should it stop throwing into some outer scope?

I have been receiving this error (Error: Could not act on confirmation) when finishing a trade.

Could it be because I am using an older version of node-community? Or is there something happening with steam

I have been receiving an error: "callback is not a function". I believe it has something to do with this implementation: 
 

watchSteamGuard(profileId) {
  const client = this.client(profileId) // SteamUser Client
  const sharedCode = this.sharedCode(profileId)
  client.on(‘steamGuard’, function (_, callback, lastCodeWrong) {
    if (lastCodeWrong) {
      setTimeout(function () {
        callback(SteamTotp.getAuthCode(sharedCode))
      }, 30000)
    }
  })
}

I am on version 4.18. Have no idea what might be causing the problem. Any insight would be greatly appreciated.

To verify if a user’s tradelink is valid I usually would create an offer using the tradeLink and calling getUserDetails on that offer. But if the user renew his tradelink, only the token value is being changed and I feel like my method isn’t the most realiable since is not throwing me errors when I try to get userDetails. 
 

Is there any other realiable way to verify for a valid tradeLink?

I need help understanding what is happening here.

I try to logOn on top of a session that's already logged on, and I recieve the error AlredyLoggedInElsewhere.

I don't understand what happens with my client sessions, it seems that I have a T1 session, a T2 session, but T4 dropped off and T5 received the error. Is T5 online after this?

Are T1 and T2 online? They are still handling messages. How do I know if am currently logged in or off?

 

 

\

Sometimes when I try to login on a process that has already logged, it prompts asking for the steam guard code. Is there a way to disable this?

Currently, for reasons I do not know, my bots take about a minute to logIn. Sometimes, due to the nature of the business, I receive a call to log in again, but sometimes it tries to login on top of a client instance that is currently trying. I tried to solve this by implementing a timeout, calling logOff when it fires off.

I wanted to know if there is a way to check if the client instance is currently trying to login. Or I have to implement a variable on my end to check it.

Also, is there a reason why my bots are taking this long? I am using the TCP protocol, but I read some topics here forcing WebSockets. I run these bots on containers inside a cloud environment.

I was wondering, wouldn't the logOff() method remove the event listeners? @Dr. McKay

Just so I understand the behavior, because I face this error sometimes. The first session would be kicked out with this error, but the session that logged in would be logged in correctly? @Dr. McKay

I was wondering if it's possible to handle operations with Steam-offer-manager along with multiple applications logging the same user. Let's say I have an application running steam-offer-manager polling for events. But I want to run a task in a Cloud Function where I need to log in to one of the profiles polling in the other application. I don't want to log off the listener....

Is this possible?

If it's not, where can I find information on Steam's API on how it handles sessions/logins? Any suggestions on doing something like this?