If you are not receiving mobile app messages, ensure that the certificates are appropriately configured.
When mobile app messages are not delivered on iOS, you may see errors, such as BadDeviceToken, DeviceTokenNotForTopic, or BadCertificate.
- The iOS certificate has expired, is invalid, or has been revoked. (403 errors)
- The p12 or p8 has expired, is invalid, or has been revoked. It needs to be regenerated.
- The p12 or p8 is generated using a third-party tool instead of the Apple site.
- The p12 or p8 does not contain a Production-friendly name.
- The appKey is incorrectly associated to Development or Production environment.
Note: The Development certificate should be specified for Development Apps and the Production certificate for Production Apps only. If you are using an Enterprise certificate, you will need to choose Production.
- Development appKeys are not associated with Development.
- Enterprise appKeys are not associated with Production.
- The iOS token is invalid, or is mismatched. (400 or 410 errors)
.pemcertificate may be wrong.
BundleIdmay be wrong.
DeviceIDmay be wrong.
If you experience an issue in iOS certificates, you can regenerate the certificate after you follow the instructions in the Set up your iOS in Apple article.
Once corrected, re-upload your corrected certificate into Acoustic Campaign. For more details, see How do I add an app?
When a mobile app user force quits the iOS app on iOS 10 or 11, subsequent mobile app messages may not be delivered. As a result of this, mobile app users on iOS 10 receive mobile app messages only on reopening the app. On iOS versions from 11.0 through 11.2, users do not receive the mobile app messages. However, iOS 9 and versions 11.3 and later, work fine.