-
Notifications
You must be signed in to change notification settings - Fork 25
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
Auth token refresh misses when macOS is sleeping #984
Comments
Hello @SpencerCDixon - I appreciate the report and thank you for your time in investigating from your end. I'm asking our Cocoa developers, including @ricardopereira who worked on #881, to take a look in case there's something obvious to ask or point out. |
Great, thanks! I chatted with Tom in Intercom and we went through a number of settings and flows that didn't work out. He may have some useful context to the situation. Happy to recreate and capture verbose or debug logs if yall think that would be helpful as well! |
Hi @SpencerCDixon . The changes at branch 984-fix-token-error-connect fixed the issue in my repro. May I ask you to test it? Your Podfile should look like this:
Thanks! |
Looks good to me on that branch! Thanks @tcard! Will that be able to make it into next release? |
That's great news. Nice work, @tcard. Toni's created a PR (#986) so as soon as we've merged that then either I or one of my colleagues will get a release out. Probably tomorrow at some point. |
Which version of the Ably SDK are you using?
1.1.18
On which platform does the issue happen?
macOS 10.14.6
Are you using Carthage?
0.34.0
Which version of Xcode are you using?
What did you do?
authCallback
is not properly re-fetching TokenRequests when the computer is sleeping during the TTL expiration. Reproduction steps:Note: if you don't sleep the computer it refetches the tokens fine!
What did you expect to happen?
Client to properly reconnect once computer wakes from sleep.
What happened instead?
It never fetches the new token and enters this infinite loop of being unable to reconnect.
Edit: My guess is this issue is very related to this one
The text was updated successfully, but these errors were encountered: