Missing Fields in Notification #284
Open
Conversation
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
Added missing fields for title and body. fechanique#160
Adding body and title.
No notification object here. Will have to send contents in data array.
arindamnayak
suggested changes
Apr 17, 2017
|
|
||
| Map<String, Object> data = new HashMap<String, Object>(); | ||
| data.put("wasTapped", false); | ||
| data.put("title", remoteMessage.getNotification().getTitle()); |
There was a problem hiding this comment.
You should add a null check for " remoteMessage.getNotification()", because you send only data in FCM API , then background notification works - explained here. So in that case, 'remoteMessage.getNotification()' will be null and it will break.
|
Why hasn't this been merged? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Added missing fields for title and body.
#160