Push notification troubleshooting and FAQ

Why isn't my device receiving the push notification?

There are a few different reasons your device might not receive a push notification. Check the following possible causes to troubleshoot a push that doesn't seem to be sending:

Targeting issues

Your device or user info does not match the Target audience for the message.
Your device was switched to a different user who is not eligible for the push and/or was not eligible at the time the message sent.
If you are targeting a user attribute that is an array with a contains segment, the value must match one of the array items exactly. For example, if your user's array is ["Aa", "Bb", "Cc"] and your target is set to "UserAttribute contains A" the push won't send, but if your target is set to "UserAttribute contains Aa" it will work.

Push token issues

Your device doesn’t have push enabled.
Your device’s push token was added after the message was scheduled to send.
Your device does not have a push token, either because of an uninstall or because the push token migrated to another device.

Delivery issues

The time it takes for a scheduled message from the servers (push, webhook, and email) to be delivered to the respective delivery service (e.g APNS, FCM) depends on the messages volume and complexity of segmentation criteria. It’s possible that the message is still in the pipeline and will come through shortly (up to 15mins for more complex use cases).
Optimal time delivery takes time to analyze user behavior before scheduling the message delivery. This means push notifications with same-day optimal time delivery may not send until later in the day or the following day.
If your push notification delivery has a certain amount of delay, it won’t send right away unless you are using the preview button with a registered test device.
You may have set a global message/push notification limit for your app. If you’ve reached the daily limit, you won’t be able to receive any more messages unless those messages are marked as Caps Exempt. Limits can be adjusted in App Settings > Keys and settings > Messaging.

iOS specific

The app was open when the push notification was delivered to the device (only iOS users).
Your bundle ID used to generate certificates is not correct (e.g. you used 'TicTacToe' but should have used 'com.example.you.TicTacToe'). You'll need to regenerate certs after correctly setting your bundle ID in your app.

Android specific

You have the wrong Google API key.
AndroidManifest may be missing necessary code.
build.gradle dependencies using Google Cloud Messaging or Google Cloud Location version is less than the minimum v8.3.0 (if you installed via Gradle).
Missing Android notification channel

Other issues

The app was uninstalled on the device.
For messages with personalized text (Jinja), your message won’t send if the custom term or attribute text isn’t correct. Example: The if the message “Welcome, {{ userAttribute['First name'] | default('user') }}” didn’t run correctly, it won't send.
If you are still having problems with push notifications, contact [email protected] for assistance.

Why isn't my push notification's Open URL working? Why aren't any Open Actions being tracked?

If the URL is incorrect, it's possible that the Open Action won't be tracked. Make sure there is no hidden space at the end of the URL (e.g. "www.leanplum.com/example ").

Can I set a daily/weekly push message limit for users?

Navigate to your App's Settings in the dashboard and click on the Messaging tab. There you can set weekly/daily push message caps for your users.

See Campaign entry limits for more on messaging limits in general.

How do I customize my Android push?

The push notifications on Android can be customized using the LeanplumPushService.setCustomizer. For a full sample, check this HowTo article: Customize your push notifications - Android sample.

You can also customize the titles displayed in Android pushes using Data under Advanced options.