Appnatively
Appnatively
Knowledge Base
Go to Studio
Knowledge Base
Go to Studio
Getting Started
Welcome to AppNativelyCreate your first appFinding your way around the Studio dashboard
Website Connection
Connect your website to AppNativelyInstall and update the required pluginChoose which plugins power your app“Website Not Connected” – what it means and how to clear itFix a failing or dropped connection
App Editor
Build your app with AI chatWrite prompts that get the screen you wantUndo an AI change you don’t wantEdit screens and components by handManage your app’s pagesDesign your headerDesign your bottom navigationAdd and edit drawersManage your themeHow your changes reach your usersSave vs. Publish – what each one doesWhen a new release is requiredWhen AI gets it wrong
Splash & App Icon
Set your app iconAdd Android Adaptive Icon layersDesign your splash screenRecommended image sizes
Publishing Setup
What you need before your first buildSet your app’s name, slug, and package IDAdd Android credentials and your keystoreAdd iOS certificates and provisioningConnect Google PlayConnect the App StoreSet up Firebase Configuration
Build & Deploy
Connect GitHub before you buildBuild your app – and submit it to the storeFix a failed build
Push Notifications
Create and send a push campaignTrack campaign performanceNotifications aren’t arriving
Integrations
Connect a third-party service

Notifications aren’t arriving

If you’ve sent a campaign and it doesn’t seem to be reaching your users, work through these checks in order – most cases come down to one of three things.

1. Check Firebase Configuration is connected

Push notifications depend entirely on a working Firebase connection. Go to Settings → Firebase Configuration and confirm the status shows “Connected.” See Set up Firebase Configuration if it isn’t.

2. Check the campaign’s status

Open Push Notifications and look at the specific campaign’s status in the table – did it actually show as sent, or did it fail? A failed send explains missing delivery on its own, before you need to look any further.

3. Consider device-side causes

If Firebase is connected and the campaign shows as sent, the remaining causes are usually on the device itself:

  • The user has notifications disabled for your app at the operating system level.
  • The user hasn’t opened the app recently enough for their device to still be registered to receive notifications.

These aren’t things AppNatively can fix directly – they’re normal, expected behavior on your users’ end, and part of why Delivery Rate is rarely a full 100%. See Track campaign performance for what a typical delivery rate looks like.

FAQ

Track campaign performance
Integrations
Was this page helpful?
On this page
1. Check Firebase Configuration is connected2. Check the campaign’s status3. Consider device-side causesFAQI fixed my Firebase connection – do I need to resend the campaign?+Is there a way to see exactly why one specific user didn’t get a notification?+