-
Notifications
You must be signed in to change notification settings - Fork 95
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
Stop the sync service constantly attempting to restart on auth error. #1654
Conversation
Additionally removes a retain cycle that was preventing the client from being released.
Generated by 🚫 Danger Swift against c667017 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #1654 +/- ##
===========================================
- Coverage 58.73% 58.52% -0.21%
===========================================
Files 412 413 +1
Lines 28223 28256 +33
Branches 14061 14078 +17
===========================================
- Hits 16577 16538 -39
- Misses 11187 11263 +76
+ Partials 459 455 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here. |
The SDK has changed a lot, we no longer need to stop and start the sync loop.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Additionally removes a retain cycle that was preventing the client from being released.
This really isn't the ultimate solution. The sync service should provide us with more context as to what error occurred, and more specifically, what conditions need to change before a restart is triggered (e.g. network conditions/some user input/none, its fatal)