Multiple push providers

Having a double integration is possible, but requires some vigilance:

Look at the logs. No need to activate verbose logging for that, when our SDK detects a risk of mis-configuration it will always print a log, usually at startup.
Carefully test each push provider still work fine and nothing is broken.
On mobile, test with your application running in foreground, running in background, and stopped (cold boot).
Pay attention to notification receipt confirmations, clicks and deeplinks.

Android

You will need to create a FirebaseMessagingService class to receive notifications and transmit them to all SDKs. This is described in the following Troubleshooting Android / Multiple FirebaseMessagingService article.

Look closely at the 3 tabs of the code block at the end of this section of the doc.

iOS

Make sure that receipt confirmations and clicks on notifications are reported.

Otherwise, you must validate that the AppDelegate and UserNotificationCenter delegates are properly installed for each SDK.

Our SDKs use forwarding, some others use method swizzling, and it often happens that the app code defines its own delegate which overwrites the setup of other SDKs without paying attention.

Our documentation lists the methods we need, in case you need to resort to manual forwarding: