This repository was archived by the owner on Sep 4, 2020. It is now read-only.
Move to Looper/Handler for Synchronous execution#18
Merged
iambmelt merged 1 commit intomicrosoftgraph:masterfrom Jun 24, 2016
peternied:looper
Merged
Move to Looper/Handler for Synchronous execution#18iambmelt merged 1 commit intomicrosoftgraph:masterfrom peternied:looper
iambmelt merged 1 commit intomicrosoftgraph:masterfrom
peternied:looper
Conversation
When using the synchronous executor from a background thread, on certain API devices, the foreground action would never be called back on. Switching to Looper.getMainLooper() to provide access to the foreground execution environment.
Contributor
|
Looks great, @peternied! Thanks for submitting a fix 👍
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
When using the synchronous executor from a background thread, on certain
API devices, the foreground action would never be called back on.
Switching to Looper.getMainLooper() to provide access to the foreground
execution environment.