Troubleshooting Multiple Push SDKs
While multiple push SDKs can be integrated into a single app, this may cause issues, and we cannot guarantee results. This section provides some considerations you should keep in mind as you develop your app. Areas of concern can include 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 Marketing Cloud SDK’s initialization. If the sender id is set during initialization the Marketing Cloud 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 Marketing Cloud SDK whenever it has been retrieved/updated from the Firebase SDK.
The Marketing Cloud SDK will not send a registration request to the Marketing Cloud until the push token has been set.
Not updating the SDK with a new push token when onTokenRefresh 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
handleMessagethat are not from the Marketing Cloud will be ignored.