Troubleshoot Multiple Push SDKs on Android
While you can integrate multiple push SDKs into a single app, this approach can lead to complications and we can’t guarantee reliable results. The following sections highlight some considerations you must keep in mind as you develop your app with multiple push SDK integrations. Areas of concern can include registration, geolocation, and more.
Any other push provider you choose must also allow a multiple push provider implementation.
Don’t set the SenderId during the SDK’s initialization.
If the SenderId is set during initialization, the SDK attempts to fetch a push token from the Firebase SDK. Doing so can lead to inconsistencies in the token that is registered with Engagement.
Set the push token in the SDK whenever it has been retrieved or updated from the Firebase SDK.
Not updating the SDK with a new push token when onNewToken is triggered prevents Engagement from sending push messages to your application.
When a push message is received from Engagement, pass it into the SDK to be presented.
Messages passed into handleMessage that aren’t from Engagement are ignored.