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

Set up Firebase Configuration

This is the step most likely to get skipped by accident, because it’s easy to assume it’s only for apps sending push notifications. It isn’t – no build can be triggered at all without it.

Before you start

Your Package ID needs to already be set. This page is disabled with an “Action Required” message until Set your app’s name, slug, and package ID is done.

Steps

1. Go to Firebase Configuration

Open Settings → Firebase Configuration.

2. Upload three files

  • Android Configuration – your Android config file from Firebase (google-services.json)
  • iOS Configuration – your iOS config file from Firebase (GoogleService-Info.plist)
  • Service Account Key – a separate service account key file from Firebase

3. Save, then check the connection

Save your changes, then click Check Connection to confirm.

Why this matters even if you’re not sending push notifications

Skipping this doesn’t just disable push notifications – it also blocks your ability to trigger a build at all. It’s one of the five requirements checked in What you need before your first build, independent of whether you ever plan to use push.

FAQ

Connect the App Store
Build & Deploy
Was this page helpful?
On this page
Before you startSteps1. Go to Firebase Configuration2. Upload three files3. Save, then check the connectionWhy this matters even if you’re not sending push notificationsFAQWhere do I get these three files?+I only care about iOS – do I still need the Android file?+