-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Token issue #33
Comments
Looks like you're running an older version of the code, the auth stuff has been refactored quite a bit lately. Though I suspect that won't help with this... Are you using a Skype-only (username to login) or Microsoft (email, If you put |
Has this happened again since reporting? I suppose if not easily reproducible, it may have just been a temporary hiccup on the server... |
It has happened a few times over the days, I didn't get to implement proper logging including the raw http response logging yet though. Regarding the skype-only question - it's a skype-only account, no live: prefix. It seems after roughly two days the connection is being lost (script restarts itself after exiting): After the update the most recent error I had was this:
|
The PPFT token comes before the username/password are entered, so I'm not sure how that's glitching out. That said, it appears the flow has changed again since I wrote this code -- there now appears to be an annoying two-step flow where username decides the type of login on the next page. Maybe I need to update SkPy to match. |
So as far as I can tell, the user-then-password flow is purely client-side -- the PPFT retrieval and credential submission is all still the same... 🤔 |
@Nothing4You Any luck reproducing with HTTP debug on? |
Sorry it took this long, I just added logging SKPY_DEBUG_HTTP=1, so I should have results in 2 days. |
So, finally.
The problem seems to be the following extracted from SKPY_DEBUG_HTTP:
|
As in... exactly a day? Sessions usually only last 24 hours (check I've set an event loop of my own running on a test account, so will see what happens to it tomorrow... |
Yes, initially it was every 48 hours, now it's down to every 24 hours:
|
Okay, mine expired, but the auth handler kicked in as the token was past expiry (except that failed due to a missing PPFT token instead). No 500 here. 😞 Can you check the expiry you get is indeed 24 hours? I'm curious how you had it working for 48 hours before, I've never had a token last longer than a day... |
As far as I can tell, there is no way to refresh registration tokens, so I think you will have to reconnect and resubscribe to events when your token expires. |
I'll close this ticket now, given that there doesn't appear to be a way to refresh registration tokens. You'll have to reconnect every 24 hours using |
Hey there,
I just noticed this exception in my log, I don't know how to reproduce this though, hopefully it's enough info for you to see the issue already:
The text was updated successfully, but these errors were encountered: