Skip to content

SDK doesn't reconnect after host device long sleep #700

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
electrozen opened this issue Oct 28, 2020 · 4 comments
Closed

SDK doesn't reconnect after host device long sleep #700

electrozen opened this issue Oct 28, 2020 · 4 comments
Assignees

Comments

@electrozen
Copy link

electrozen commented Oct 28, 2020

As discussed in #548 , when the host device awake from a long sleep, reconnection doesn't occur due to expired SAS token ("Connection Refused: not authorised"). SAS token renewal occur later but fail to restart the connection.

What would be the best workaround ? Any way to check on the state of the SDK and restart it ? So far I'm attempting to detect sleeps outside of the process and restart the process instantiating the SDK. Thanks for your help.

Log in debug mode showing the issue below.
perfdaemon-issue.log

AB#8680651

@cartertinney
Copy link
Member

This is a known issue - we're working on implementing a solution

@cartertinney
Copy link
Member

Issue is being tracked in #706

@cartertinney
Copy link
Member

This issue has been resolved and included in the latest release, 2.5.0

@az-iot-builder-01
Copy link
Collaborator

@electrozen, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants