On iOS, Firebase may intercept the content of push notifications sent from Batch. As a result, Batch SDK may no longer able to:
- Detect push opens, resulting in broken campaigns statistics (see more here)
- Handle deeplinks. Batch SDK never receives the deeplink and cannot pass it to the app to direct your users to the right page.
- Display Mobile Landings. The information Batch SDK needs to display the In-App landing page are located in the payload of the notification intercepted by Firebase.
Detecting the issue
If you are facing one of these issues, open your app and take a look at the logs. Batch SDK will print an alert:
Fixing the issue
Here are the two steps you need to take to fix the issue:
- Switch to a manual integration, as described here: Manual Integration
- Then, make sure you intercept the payload of Batch notifications as described here: Intercepting Notifications
Here is how you can test your integration:
- You should no longer see the alert in the logs of your app
- Send a test push notification to your device and open it (see more here). You should see the following line: "
Push - App was opened from a Batch push".
- Then, try sending a test notification to your device with a deeplink. Go to the dashboard → Push → Click "New Campaign" → Head to the message edition part, edit the text of the notification, add a deeplink to the campaign in the "advanced" part → Click "Send a test", after selecting your device.
- Send a preview of an In-App message to your device. Go to the dashboard → Settings → Themes → Select a theme or create one and click the "preview button". The In-App message should be displayed as soon as you click the notification.
Note: In case the In-App message is not displayed correctly or is dismissed by the splash screen of your app, make sure you implement the "do not disturb" mode (see more here). This will allow you to pause In-App messages until the app can display them correctly.