Troubleshooting External Push Notification Service (PNS) Configuration for MobilePush Implementation

If there is a discrepancy in the provisioning settings between your application and the notification service, you may encounter the following symptoms:

• Send Failure: The push notification result is Fail, accompanied by errors indicating token issues (e.g., Requested entity was not found, NotRegistered, mismatch).

• Opt-In Failure (iOS): The contact status in Marketing Cloud remains Not Opted In, even though notifications are enabled on the device.

• Missing Token: The System Token (Device Token) remains null or empty.

Configuration Checkpoints

These symptoms typically indicate an authentication mismatch between the app and the PNS. Please verify your configuration against the following checklists.

1. iOS (APNs) Checkpoints

• Xcode Configuration:

  • Ensure the Push Notifications capability is enabled in your Xcode project.

• Apple Developer Portal:

  • Verify that a valid APNs Auth Key (.p8) is created.

  • Note: While legacy .p12 certificates are supported, the .p8 format is recommended as it does not require annual renewal.

• Marketing Cloud Administration:

  • Ensure the Key ID, Team ID, and Bundle ID registered in Marketing Cloud match the information in the Apple Developer Portal exactly.

• [Critical] APNs Mode vs. Build Environment:

  • Verify that the APNs Application Mode (Sandbox / Production) in the MobilePush Administration settings matches your application's build environment.

    • Sandbox: Development builds (e.g., installed directly via Xcode).

    • Production: Release builds (e.g., TestFlight, App Store distribution).

  • Note: Although the .p8 key itself is valid for both environments, the APNs endpoint (mode) configured in Marketing Cloud must strictly match the app build. A mismatch will result in delivery failure.

2. Android (FCM) Checkpoints

• Configuration File Placement:

  • Ensure the valid google-services.json file is placed in the root of the /app module directory.

• Project Integrity:

  • Verify that the package_name and project_id inside google-services.json match your target application and Firebase project.

• Marketing Cloud Administration:

  • Ensure the Service Account Key (JSON) uploaded to the MobilePush Administration console belongs to the same Firebase project as the google-services.json used in the app.

  • Note: Using a JSON file from a different Firebase project is a common cause of "Mismatch Sender ID" errors.

• Firebase Setup:

  • If the app does not include an implementation or configuration for push notifications via FCM, the system cannot retrieve a token. Without a token, MCE immediately marks the contact as Not Opted-In. When you check the Membership tab of a contact in Contact Builder and the Opt Out Source field shows "Missing or Invalid Device Token", the app may be missing FCM-related configuration.

     

    If you confirm this issue, verify the following:

    • The firebase-messaging dependency is included in the app's dependencies.
    • The Google Services plugin is correctly applied.

    Refer to Integrate the MobilePush Android SDK and the Firebase documentation for details.

Troubleshooting & Notes

Provisioning is primarily performed within your development environment (Android Studio, Xcode) and the respective developer consoles (Firebase/Apple).

Due to the dependency on external services, Marketing Cloud Support cannot directly verify or validate your client-side provisioning status (e.g., confirming file placement). If you contact Support, we will guide you through these verification steps or suggest isolation methods.

Recommended Isolation Steps:

1. Review Checkpoints: Re-verify the settings listed above with your development team.

2. Test with the Learning App: Deploy the Salesforce Learning App (sample app). This helps isolate whether the issue lies in the specific app implementation or the configuration.

3. Contact Support: If the issue persists after verifying the above, providing detailed logs and error messages will help expedite the investigation.