@Ankita.Ghosh make sure you do not use one generated for Demo purpose, from a Dynamic System Settings 'DemoPushToken'.
The app developer should be able to provide the push token associated with the test device.
Check you are not testing the use case by setting proper PushToken through the DSS 'DemoPushToken'.
check the entry into 'PR_DATA_PUSH_REGISTRATION', - is there an entry in the table ? The device has to be registered properly so that an entry would be added to the table.
The user guide has entire registration/unregistration process of a Device.
Thank you for your reply, I will take a step back and describe what we have done so far, We are trying to use Push Notification as a communication channel for CDH.
"make sure you do not use one generated for Demo purpose "-- need more clarity on this. As we are into pre-sales and want to showcase push notification feature for our clients.
we have built an android app from Pega channels and interfaces, Installed it into an android device. The APP is Push enabled and we are testing the push notification from Manage Tab>Push notification, I am able to receive push notifications. But when we are trying to test it from App studio > settings > channels >Push notification > Added application > Added Variant > added FCM server key> While testing > Getting sender ID Mismatch.
How do I get Test Push Token? As the app is built within Pega Interface.
PR_DATA_PUSH_REGISTRATION this table does not have any data, It will be very nice if you can share with us the process to register a device.
Posted: 1 year ago
Posted: 9 May 2022 8:39 EDT
Marije Schillern (MarijeSchillern)
Senior Knowledge Management Specialist
This sounds like the app variant ID may not be configured correctly. In the Firebase Console for the associated project in the Project settings > Cloud Messaging tab (same place you grabbed the FCM server key from) there is a "Sender ID" field. This is basically the "username" to go with the FCM Server Key and should be used as the App Variant ID for that android application. This collectively gives the server code the username and password it needs to send, and should eliminate the Sender ID Mismatch errors at send time.