-
Notifications
You must be signed in to change notification settings - Fork 237
Fix coroutine scope #4820
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
Fix coroutine scope #4820
Conversation
…se the appropriate CoroutineScope when injecting one.
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #4820 +/- ##
========================================
Coverage 80.45% 80.46%
========================================
Files 2141 2141
Lines 56736 56737 +1
Branches 7110 7110
========================================
+ Hits 45649 45652 +3
Misses 8637 8637
+ Partials 2450 2448 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Thanks, this should also solve some issues where the coroutine scope outlived the component 🤞 .
|
Content
Use the CoroutineScope tight to the session when appropriate.
Introduce a
AppCoroutineScope
annotation so that we do not inject the app coroutine scope by mistake.Motivation and context
Use the correct coroutine scope in all the classes.
Screenshots / GIFs
No change
Tests
There should have no effect, but signing out should cancel any pending operation in the session coroutine scope.
Tested devices
Checklist