My mobile landing does not show

Mobile Landings may fail to display in certain cases. This guide outlines the most common causes and how to fix them.

Resolve Conflicts with Other Screens

Your application may display a full-screen element — such as a splash screen or an interstitial ad — at launch. These elements can prevent Batch from displaying the Mobile Landing properly.

If the Mobile Landing appears when the application is in the background, but not after a cold start (killed state), the issue is likely caused by one of these screen conflicts.

Solution: Use Do Not Disturb Mode

Do Not Disturb (DnD) mode allows you to delay the display of Mobile Landings until the application is ready. This gives you control over when Batch displays the message, without switching to fully manual mode.

Refer to the DnD implementation guides for each platform : iOS / Android / Flutter / React Native / Cordova.

Fix Issues in Manual Mode

If you use the Manual Integration, verify that your implementation follows the integration guide.

On iOS, you must implement the UNUserNotificationCenterDelegate. Make sure you call the Batch handler in the appropriate delegate method.