Author Topic: Steam protocol  (Read 396797 times)

0 Members and 3 Guests are viewing this topic.

Offline dartraiden

Re: Steam protocol
« Reply #570 on: 17 12 2024, 13:40:42 »
Try the last build.
 

Offline KentKareless

Re: Steam protocol
« Reply #571 on: 18 12 2024, 10:18:16 »
I am using Commit https://github.com/miranda-ng/miranda-ng/commit/4c3d77032316bc8814cddc00d020ba00d4533999 (see attached version info) and it still does not work for me.
I also tried deleting the existing AccessToken, RefreshToken and SessionId keys in the DB but still no dice.

If i remember correctly the commit that broke it for me was: https://github.com/miranda-ng/miranda-ng/commit/4d6ff1f6d3a818998364004e032d640675918ce7
But i am not 100% sure about that.

Does it still work fine for you?
« Last Edit: 18 12 2024, 10:20:08 by KentKareless »
 

Offline ghazan

Re: Steam protocol
« Reply #572 on: 18 12 2024, 15:50:01 »
KentKareless,
well, in that log there was a problem with relogin, and it is definitely fixed.
you cannot send messages, that's true, bug Miranda is already able to receive them
 

Offline KentKareless

Re: Steam protocol
« Reply #573 on: 18 12 2024, 16:59:18 »
well, in that log there was a problem with relogin, and it is definitely fixed.
Yes, that's correct!
I now get a completely different netlog (see attachment).
Login still does not work though.

It might be related to the fact that i am have an authenticator connected to my steam account.

P.S.: Thank you very much for working on Steam chat integration!
 

Offline ghazan

Re: Steam protocol
« Reply #574 on: 18 12 2024, 17:10:24 »
It might be related to the fact that i am have an authenticator connected to my steam account.
Obviously, Steam required Miranda to validate your login attempt using TOTP code, but the code being sent doesn't make Steam happy.
BTW, are you sure that this code is only 5 chars long? I have read somewhere, that only email notification code has 5 letters, while TOTP code is longer
 

Offline ghazan

Re: Steam protocol
« Reply #575 on: 18 12 2024, 17:45:34 »
KentKareless,
I've uploaded a build with more error info, please make this log again
 

Offline KentKareless

Re: Steam protocol
« Reply #576 on: 18 12 2024, 17:55:31 »
I just did!
Here it is (see attachment).

The TOTP code is definitely only 5 characters long!
 

Offline ghazan

Re: Steam protocol
« Reply #577 on: 18 12 2024, 17:59:00 »
Okay, now it's possible to see the error code
DuplicateRequest = 29 - wtf does it mean?... very interesting

// Observed results can be InvalidLoginAuthCode, TwoFactorCodeMismatch, Expired, DuplicateRequest.
// DuplicateRequest happens when accepting the prompt in the mobile app, and then trying to send guard code here,
// we do not throw on it here because authentication will succeed on the next poll.

@KentKareless
Okay, let's ignore this trash, next build will be available in 30 minutes
« Last Edit: 18 12 2024, 18:19:59 by ghazan »
 
The following users thanked this post: KentKareless

Offline KentKareless

Re: Steam protocol
« Reply #578 on: 18 12 2024, 19:27:58 »
Logging in works fine now!
Thanks for the quick fix!  :)
 

Offline KentKareless

Re: Steam protocol
« Reply #579 on: 20 12 2024, 16:34:22 »
I have an idea of why the "Duplicate request" error happens:

It might be related to the fact, that i am running the builtin Steam chat and then connecting with Miranda NG.
Even right now with the fix that just ignores the error, the builtin Steam chat is disconnected when Miranda NG connects.

It would be really nice if it would be possible to be connected with Miranda NG and the builtin chat client, but i am not sure if that is technically possible.