Troubleshooting Multiple Push SDKs

MobilePush is able to work in the same app as other push vendor SDKs. However, we recommend checking with your other SDK vendor to ensure they also support a multi-push provider implementation. This page provides considerations for multiple push SDKs to successfully work together. Common areas for poor implementation can include device registration, geolocation and more. Note that this is not an exhaustive list.

Any other push provider you choose must also allow a multiple push provider implementation.

Remove SenderId from SDK init

Do not set the sender id during the SDK’s initialization.

If the sender id is set during initialization the SDK will attempt to fetch a push token from the Firebase SDK. This could lead to inconsistencies in the token that is registered with the Marketing Cloud.

Handle Push Token

Set the push token in the SDK whenever it has been retrieved/updated from the Firebase SDK.

Not updating the SDK with a new push token when onNewToken is triggered will prevent the Marketing Cloud from sending push messages to your application.

Handle Push Message

When a push message is received from the Marketing Cloud pass it into the SDK to be presented.

Messages passed into handleMessage that are not from the Marketing Cloud will be ignored.