Fixed issues with reporting sync state events from different threads #6341
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Content
Replaced
LiveData
withFlow
for sync state reporting.Motivation and context
SyncRequestStateTracker
instance is reused in different threads, because of theScope
annotation. IfLiveData::postValue
is called fast enough, some events can get lost, because only the last one is dispatched.So in my case I could reproduce loosing of
InitialSyncRequestState.Idle
due to sendingIncrementalSyncIdle
from another thread.Signed-off-by: Artjom König [email protected]