Key Takeaway
Adalo push notifications break for 4 main reasons: incorrect OneSignal App ID, missing Expo push token registration, iOS provisioning profile errors, and silent notifications failing without user permission. This guide walks through each fix. If you need guaranteed push delivery, Rehost can build a custom-coded solution with 99.9% delivery rates.
Why Adalo Push Notifications Break
Push notifications are one of the most commonly broken features in Adalo. Forum posts about "notifications not sending" outnumber almost any other topic. The root cause is usually one of four issues, and the fix depends on which layer has failed.
1. OneSignal App ID Misconfiguration
The most common issue. Adalo uses OneSignal as its push notification provider, and if the App ID or REST API key is entered incorrectly in the Adalo settings panel, notifications will silently fail with no error message. Double-check your OneSignal dashboard and make sure the App ID matches exactly, including capitalization.
2. Expo Push Token Registration Failures
Adalo builds on Expo, which requires each device to register a push token before it can receive notifications. If the user opens the app but denies notification permissions (or if the app crashes before registration completes), the token never gets stored. This means your notification technically "sends" but has zero recipients. Test with a fresh install and explicitly grant permissions on first launch.
3. iOS Provisioning Profile Errors
Apple requires a valid APNs (Apple Push Notification service) certificate linked to your app's bundle ID. If you published your Adalo app with the wrong provisioning profile, or if the certificate has expired, push notifications will work on Android but silently fail on iOS. Check your Apple Developer account for certificate expiration dates.
4. Silent Notification Failures
Adalo does not differentiate between "foreground" and "background" notifications by default. If the user has the app open, the notification may arrive but not display as a banner. This is not a bug per se, but it causes confusion when testing. Use a second device for testing, or close the app entirely before sending a test notification.
When to Switch to Custom Code
If you have tried all four fixes and push notifications still fail intermittently, the issue is likely architectural. Adalo's Expo-based notification pipeline adds multiple points of failure between your app and the user's device. A custom-coded app built with React Native or Flutter can use Firebase Cloud Messaging directly, which provides 99.9% delivery rates with full control over notification channels, priority levels, and scheduling.
Rehost builds custom notification systems for apps that need guaranteed delivery. If your church, business, or organization depends on reaching users reliably, schedule a free consultation to discuss a custom solution.
Related: Adalo App Store Rejection Fix Guide | Adalo Custom Actions Fix Guide | Adalo vs Bubble 2026 Comparison
FAQ
Why do my Adalo push notifications work on Android but not iOS?
This is almost always an Apple APNs certificate issue. Check your Apple Developer account for expired or misconfigured provisioning profiles.
Can I use Firebase instead of OneSignal with Adalo?
No. Adalo is locked into OneSignal for push notifications. If you need Firebase Cloud Messaging, you will need a custom-coded app.
How much does it cost to fix push notification issues in Adalo?
Troubleshooting is free if you follow this guide. If you want a custom-coded app with guaranteed push delivery, Rehost plans start at $250 per month.