-
Notifications
You must be signed in to change notification settings - Fork 111
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
Make stopSync more aware of background usage. #3501
Conversation
@@ -930,7 +934,7 @@ class AppCoordinator: AppCoordinatorProtocol, AuthenticationFlowCoordinatorDeleg | |||
backgroundTask = appMediator.beginBackgroundTask { [weak self] in | |||
guard let self else { return } | |||
|
|||
stopSync() | |||
stopSync(isBackgroundTask: true) |
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.
I don't think this one is strictly needed, but doesn't hurt.
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.
Makes sense to me 👍
Generated by 🚫 Danger Swift against 42da81c |
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3501 +/- ##
===========================================
- Coverage 78.71% 78.71% -0.01%
===========================================
Files 743 743
Lines 61906 61907 +1
===========================================
Hits 48729 48729
- Misses 13177 13178 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
We still had a bug where a successful background task was being run in the foreground. So this PR makes
stopSync
a bit more aware about whether it's being called from a backround task or not.(#3478)