Revadike

The method is now called `createAuthSessionTicket`, for anyone wondering

What is your usage application?

Created PR: https://github.com/DoctorMcKay/node-steamcommunity/pull/276

There is no way to abort the login process once called.

Nevermind, seems it just took a bit longer than usual. V3 is all good.

This issue isn't specific to v4. I can't get it to work on the latest version of v3 either. Debugging this currently...

@ThePlata, did u try? For me, it seems callback isn't called at all.

I did this for the callback to support the old structure: (result, detail, packages) => { // conversation new to old structure if (result) { detail = result.purchaseResultDetails; packages = result.packageList; result = result.eresult; } else { result = 1; }

Another issue getProductInfo callback doesn't get fired.

I've made it log all debug events and this is the log: https://pastebin.com/EZRG8xm3 It repeats every 2 minutes, until it finally works. Sometimes it works at first try, but often it takes several tries. loggedOnSteam only gets logged on loggedOn event. And signedIntoBarter only gets logged ONCE websession. This is my login config (un and pass omitted) { accountName: 'xxx', password: 'xxx', twoFactorCode: 'XXX', logonID: 1551653434369, rememberPassword: true, dontRememberMachine: false, autoRelogin: true, machineName: 'BOT@CLIENT' }: WebSocket disconnected with error: Ping timeout This seems to cause it, or at least be related with it.

Something weird is happening. I updated my bot to work with your latest steam packages. However, sometimes it seems like something inside steam-user gets stuck. Sometimes it works just fine, but other time it will only emit loggedOn and websession events. All other events are not emitted. And that's not all. I expect loggedOn to be only emitted once, since in my code I only login once, however when these other events are not emitted, loggedOn gets emitted every 2 minutes. Any idea what's going on?

You could of course always do it yourself, by checking the web request from steam and use https://github.com/DoctorMcKay/node-steamcommunity/wiki/HTTP-Hooks to incorporate that in your script.

I'm also wondering this actually!

Can't you just turn the callback of the friendMessage ID event into a promise and await that in an async function?

I wouldn't know without checking your bot's logic. It also begs the question: Why don't you just try?