Expo Push Notifications Not Working From Lovable? Fix It

Push notifications dead in your Lovable export? The short answer: push that works nowhere is almost always a missing setup step, not a code bug. The capability, APNs credentials, the permission prompt, and token registration all have to line up, and one missing link kills the whole chain. Work them in order and test on a real device. Build the UI from a free VP0 design, the free iOS design library for AI builders, and verify the full push path before you rely on it. To put that in perspective, about 76% of developers now use or plan to use AI tools in their work.

Who this is for

This is for developers whose Lovable-exported Expo app does not receive push notifications, and who want the specific setup chain and where it breaks.

Why push silently fails

Push is a chain, and it is silent when a link is missing. The push notifications capability must be enabled on the app. APNs credentials must be configured in EAS so Apple will deliver. The app must request notification permission and the user must allow it. The device push token must be registered with your server so you know where to send. And you must send through the right environment, dev or production. Lovable exports often miss one of these, and the simulator does not receive remote push at all. The Expo push notifications documentation covers the setup, and Apple Push Notification service is the delivery layer.

Link in the chain	If missing	Fix
Push capability	No delivery	Enable the capability
APNs credentials	Apple will not send	Configure in EAS
Permission	No token	Request and read the result
Token registration	Server cannot target	Register with your backend
Dev vs prod	Works in one only	Send to the matching environment

Build the UI free with a VP0 design

The notification UI and settings are yours to build cleanly. Build from a VP0 reference:

Build an Expo React Native notifications setup from this design: [paste VP0 link]. An in-context permission prompt, a notifications settings screen, and the token registration flow with your backend, handling granted, denied, and undetermined states. Match the palette and spacing from the reference, and generate clean code.

For related Lovable and Expo fixes, see a Lovable export missing Info.plist in Xcode, does Lovable handle iPhone and iPad screen sizes, the Bolt.new export to iOS App Store fix, and a Rork Xcode build failed solution.

Work the chain on a real device

Debug top down and on hardware. Confirm the push capability is enabled and APNs credentials are set in EAS. Request permission in context and check the result, because a denied or never-requested permission means no token. Confirm the device token is actually registered with your server. Then send a test push through the environment matching your build, dev or production, since a mismatch is a classic “works for me, not in production” trap. Always test on a physical device, never the simulator. Once each link is verified, push works reliably, and the fix is setup, not rewriting code.

Common mistakes

The first mistake is testing push on the simulator, which does not receive it. The second is APNs credentials not configured in EAS. The third is never requesting permission or ignoring the result. The fourth is the token not registered with the server. The fifth is a dev versus production environment mismatch.

Key takeaways

• Push failing from a Lovable export is almost always a setup gap, not code.
• The chain: capability, APNs credentials, permission, token registration, environment.
• Test on a real device; the simulator does not receive remote push.
• A dev versus production mismatch is a classic cause of “works in dev, not prod.”
• Build the notifications UI from a free VP0 reference and verify the full path.

Sources

• Expo push notifications overview: the supported way to send push on Expo.
• Expo: sending notifications: the official send flow and token handling.
• Expo EAS Build documentation: how Expo compiles a project into a real iOS binary.

Frequently asked questions

Why are Expo push notifications not working from my Lovable export? Almost always a setup gap: capability not enabled, APNs not configured, permission not requested, or token not registered. Work the chain and test on a real device.

How do I fix push notifications in an Expo app? Enable the capability, configure APNs in EAS, request permission, register the token with your backend, and send to the correct environment, testing on hardware.

Why do push notifications work in development but not production? Usually a dev versus production APNs mismatch, so a token from one environment will not receive pushes sent through the other. Send to the matching environment.

Do push notifications work in the iOS Simulator? Remote push generally requires a physical device. Test on real hardware.