Push notification -> From staging to production

[fern1]

Hi, we have been testing push notifications for a while now in staging and we finally made it work for Android and iOS. Now we want to put it into production. We already created a prod instance, but we are not sure the "move" was done correctly.
We updated the prod pkey in the data collection Campaign extension already and published it, and managed to add the android keys and ios certificates without an issue.
But are not sure if there is something missing on the Campaign side. We ran a "test" using the prod campaign instance, with an app that was generated in prod (the devs did something to make sure it is not going to our users).. However, it only detected 8 targets (even as a test we have more than that), and nobody got the push.
this is the log:
42Push Failure (400) : DeviceTokenNotForTopic jobId=xxxxxxxxxx pushId=* platform=APNS

How can we check if everything is correct in the prod instance? any idea of what can be wrong?

[Craig_Thonis]

Hi Fern,

Doing a bit of digging, this error typically occurs when the certificate has expired or contains multiple keys or passwords. Take a look at the documentation below and if the issue persists, please reach out to Campaign Support.

KB Article:

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-14775.html?lang=en

[fern1]

Thank you, Craig!
The dev team gave us a new certificate. This time we did not get any errors, however, it showed that 70% of the pushes were sent but nobody got any push notification.

Is there any special change that we should do when moving from stating to prod? We want to be sure the error is not on the adobe side.

[Sukrity_Wadhwa]

Hi @Craig_Thonis, 

Could you please help @fern1 further with their query?

Thanks!