• Type: Provider error
• Description: Android error provided by FCM (Firebase cloud messaging). An existing registration token may cease to be valid in a number of scenarios, including:
  • If the client app unregisters with FCM.
  • If the client app is automatically unregistered, which can happen if the user uninstalls the application. For example, on iOS, if the APNS Feedback Service reported the APNS token as invalid.
  • If the registration token expires (for example, Google might decide to refresh registration tokens, or the APNS token has expired for iOS devices).
  • If the client app is updated but the new version is not configured to receive messages.
• Troubleshooting:

1. Check your app implementation for setting the push tokens.

2. Check your segmentation criteria and only include Push Enabled users.

• Whom to contact: Your app developer (Make sure to pass them the name of this error.)

• Type: Segmentation error
• Description: At the time of sending we were not able to find any devices linked to the contact selected by the segmentation criteria.
• Troubleshooting: Check your segmentation criteria. It might contain a condition that is contradictory to what you want to achieve, for example, it doesn't contain any reference to any mobile behavior of your users, or potentially, it could also select inactive, old users.
• Whom to contact: N/A

• Type: Provider error
• Description: Implementation problem on Android. A registration token is tied to a certain group of senders. When a client app registers with FCM, it must specify which senders are allowed to send messages. You should use one of those sender IDs when sending messages to the client app. If you switch to a different sender, the existing registration tokens won't work.
• Troubleshooting:

1. Check that the Google Project Number in your app matches the one in your Google Developers Console. Firebase is deprecating Server Keys and replacing them with Firebase Cloud Messaging Tokens, and occasionally Server Keys may just stop working. If you still use the Server Key as the API key when configuring your Android app and you get the MismatchSenderId error, please make sure to use the Firebase Cloud Messaging Token instead of the Server Key.

2. Log into the Firebase console, open your project. Under the General tab, scroll down to Download the latest config file and click the button to downloadgoogle-services.json (which should include the correct project and sender IDs).

• Whom to contact: Your app developer (Make sure to pass them the name of this error.)

• Type: Provider error
• Description: iOS error provided by APNs (Apple Push Notification service). The device token is inactive for the specified topic. An existing registration token may cease to be valid in a number of scenarios, including:
  • If the client app unregisters with APNs.
  • If the client app is automatically unregistered, which can happen if the user uninstalls the application.
  • If the registration token expires.
  • If the client app is updated but the new version is not configured to receive messages.
• Troubleshooting:

1. Check your app implementation for setting the push tokens.

2. Check your segmentation criteria and only include Push Enabled users.

• Whom to contact: Your app developer (Make sure to pass them the name of this error.)

• Type: Provider error
• Description: An existing registration token may cease to be valid in a number of scenarios, including:
  • If the client app unregisters.
  • If the client app is automatically unregistered, which can happen if the user uninstalls the application.
  • If the registration token expires.
  • If the client app is updated but the new version is not configured to receive messages.
• Troubleshooting:

1. Check your app implementation for setting the push tokens.

2. Check your segmentation criteria and only include Push Enabled users.

• Whom to contact: Your app developer

• Type: Certificate error
• Description: We were not able to obtain a valid certificate for your iOS app.
• Troubleshooting: Check your app settings and add either a valid p12 certificate file or authorization token.
• Whom to contact: Your app developer

• Type: Provider error
• Description: iOS error provided by APNs (Apple Push Notification service). The specified device token is invalid. Verify that the request contains a valid token and that the token matches the environment.
• Troubleshooting: Check your app implementation. Has your app certificate been changed recently?
• Whom to contact: Your app developer

• Type: Personalization error
• Description: We were not able to resolve personalization details for the contact. This might be due to missing data on the contact level that are required for sending the message out.
• Troubleshooting:

1. Check your campaign and personalization attributes that you are using.

2. Check if the personalization is required for the message.

• Whom to contact: N/A

• Type: Certificate error
• Description: Certificate for your app has expired.
• Troubleshooting: Check your app settings and add a valid certificate for your app.
• Whom to contact: Your app developer

• Type: Provider error
• Description: Devices were excluded from the push campaign delivery based on their invalid push token status from a previous send. The status will be updated if/when the app is used again by the user.
• Troubleshooting: Check your segmentation criteria and only include Push Enabled users.
• Whom to contact: Your marketer

• Type: Provider error
• Description: The contact has revoked the push notification permission on the device.
• Troubleshooting: Consider to use another channel (e.g. In-app, email, SMS etc.) to win back the contact to accept push messages.
• Whom to contact: Your marketer

• Type: Segmentation error
• Description: At the time of sending the contact’s device doesn’t match the device-level criteria in the segment under the Apply segment criteria for devices option.
• Troubleshooting: Check your segmentation criteria under the Apply segment criteria for devices option.
• Whom to contact: N/A

• Type: Certificate error
• Description: The iOS certificate/token topic does not match with the app's bundle identifier.
• Troubleshooting: Check the Xcode project bundle identifier. It should be the same as Emarsys platform app settings.
• Whom to contact: Your app developer

• Type: Certificate error
• Description: The status of your certificate has been revoked. When this happens, you receive an alert on the Channels > Mobile Engage > Apps tab.
• Troubleshooting: You need to renew your app certificate.
• Whom to contact: Your app developer

• Type: Provider error
• Description: The Internal ID exceeds the maximum size allowed for APNS.
• Troubleshooting: Check the value and length of the Internal ID. The value must not exceed 64 bytes.
• Whom to contact: Your marketer