Bug #14712
MB - FCM iOS&Android payload structure
Status: | Closed | Start date: | 09 November 2022 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | chok yee fan | % Done: | 0% | |
Category: | - | Spent time: | - | |
Target version: | - | |||
Phase: | R1 | Branch Code: | showroom-proj-base-i5 |
Description
Record down the FCM data structure for BE integrate.
History
#1 Updated by Wong Mun Fung about 2 years ago
- title and body is the one that will be display to user in notification.
- "click_action": "com.adobe.phonegap.push.background.MESSAGING_EVENT" is include here so that Android app can capture the data in "data" when user click the notification
- "data" content is additional data that we want app to capture and handle when user click the notification. eg: deeplink, navigate path
Heres the sample FCM notification payload without the token.
"notification": {
"title": "Test Notification",
"body": "This offer expires at 11:30 or whatever",
"click_action": "com.adobe.phonegap.push.background.MESSAGING_EVENT"
},
"data": {
"surveyID": "ewtawgreg-gragrag-rgarhthgbad"
}
#2 Updated by Wong Mun Fung about 2 years ago
- Assignee changed from Wong Mun Fung to chok yee fan
#3 Updated by chok yee fan about 2 years ago
- Assignee changed from chok yee fan to Chew Kim Hian
#4 Updated by Chew Kim Hian about 2 years ago
- Status changed from New to Feedback
- Assignee changed from Chew Kim Hian to chok yee fan
what issue you facing now?
what is the data you getting now?
#5 Updated by chok yee fan about 2 years ago
- Assignee changed from chok yee fan to Chew Kim Hian
try on showroom app push notification from BE.
Android and iOS using the FCM
#6 Updated by Chew Kim Hian about 2 years ago
- Assignee changed from Chew Kim Hian to chok yee fan
nothing to do as of now
#7 Updated by chok yee fan about 2 years ago
- Status changed from Feedback to Closed
Mun Fung use showroom app pointing to UG, work as normal. So nothing to do as of now.