Clarify which thread service runs on#26
Open
jasonobrien wants to merge 1 commit intoudacity:TFCM.04-Solution-AddFirebaseMessagingServicefrom
jasonobrien:TFCM.04-Solution-AddFirebaseMessagingService
Open
Clarify which thread service runs on#26jasonobrien wants to merge 1 commit intoudacity:TFCM.04-Solution-AddFirebaseMessagingServicefrom jasonobrien:TFCM.04-Solution-AddFirebaseMessagingService
jasonobrien wants to merge 1 commit intoudacity:TFCM.04-Solution-AddFirebaseMessagingServicefrom
jasonobrien:TFCM.04-Solution-AddFirebaseMessagingService
Conversation
FirebaseMessagingService's onMessageReceived method isn't called on the main thread, but on a background service thread. This does imply some timing constraints, but not on the same order. See docs at: https://firebase.google.com/docs/cloud-messaging/android/receive
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow up to #25.
FirebaseMessagingService's onMessageReceived method isn't called on the
main thread, but on a background service thread. This does imply some
timing constraints, but not on the same order.
See docs at:
https://firebase.google.com/docs/cloud-messaging/android/receive