relog wierd behaviour

[JVz]

My bot checks every 10 minutes for client.steamID property and if its null I'm trying to relog with 

client.logOn

 

but loggin on produces this errors:

client error Error: LogonSessionReplaced

steam user error: {"eresult":34}

 

I'm also checking for client.publicIP and it is undefined when steamID is null

I was thinking it can be issues with connection, so I've tried to check 5 times with 5 sec intervals before relogging and every time client.publicIP is undefined and client.steamID is null but after that bot relogs just fine with LogonSessionReplaced error, so I assume connection is okay

 

[JVz]

looks like sometimes client.steamID is null even when steam-user is logged in

[Dr. McKay]

Do you have some way to reproduce this?

Checking whether steamID is set on a timer is not the proper way to reconnect. This would run you into problems if SteamUser is currently attempting to connect but isn't yet logged on. You only need to call logOn() when your bot starts up, and if the error event is emitted.

[JVz]

Can't find consistent way to reproduce but got same behaviour again. I disabled my relog to let bot reconnect using autorelog

Received disconnected event  from steam user

eresult=3

msg=NoConnection

but didn't get error from steam user. 2 hours later still steamID is null. After restarting bot connected just fine