Get your Base44 app store-ready by scanning, improving, and packaging it for the Apple App Store and Google Play, and set up push notifications.
When your Base44 app is ready for mobile, you can manage the entire store prep from inside your app editor. Scan your app against Apple and Google guidelines, use the Base44 AI chat to improve any problem areas, then generate the files you need to submit your app in your Apple and Google developer accounts.
Your mobile app runs your published Base44 app inside a secure web view. This is a lightweight native wrapper around your web app that opens only your app’s URL. When you publish most content and design changes in Base44, they also appear in your app without sending a new version to the Apple App Store or Google Play. You can also add push notifications when you generate your store files, so your app can send updates straight to someone’s phone.
Important: You can run the scan to prepare your app for stores on the Free plan, but to download the files for app submission you must be on the Builder plan or higher.
Before you begin
Store submission is a multi-step process that involves both Base44 and your Apple and Google dashboards. Keep your developer credentials nearby and set aside time to complete each part.Make sure you have the following ready:
A published Base44 app with a stable URL
An Apple Developer Program account with access to App Store Connect and API keys
A Google Play Console developer account
Permission to create and manage apps in both accounts (if you are working in a team)
A logo that meets Apple and Google icon requirements, or a clear prompt to generate one with AI
A privacy policy and terms of use page that explain how your app handles data and device permissions, and that are reachable from your main app pages
Information about selling products:
Physical goods and services: Using Stripe is allowed in the app stores.
Digital goods (for example, subscriptions or in-app features): Do not use Stripe for payments inside your mobile app. Apple and Google require their own billing systems for digital content. If your app uses Stripe for digital content, your app is rejected. We are working on a built-in integration for StoreKit and Google Play Billing to handle digital purchases and keep your app compliant.
Already done all the preparation and ready to submit? Follow our step-by-step visual guide for submitting your app to Apple App Store and Google Play Store.
Before you can generate store files and submit your app, you need active Apple and Google developer accounts. These accounts let you own your listings, manage releases, and handle reviews directly in each store.
You are responsible for setting up and paying for your Apple and Google developer accounts, as well as managing your app listings and submissions. Base44 helps you prepare your app for submission, but does not create or manage your developer accounts.
Use your Apple Developer account to submit your iOS app in App Store Connect and manage releases. Make sure you have an Apple ID you can use for your business.To create your Apple Developer account:
Sign in with your Apple ID and start the enrollment process.
Choose the account type that fits your situation:
Individual: Select this if you are publishing as yourself.
Organization: Select this if you are publishing on behalf of a company. Apple may ask for your legal business name and D-U-N-S number.
Review and accept Apple program terms.
Complete the payment to activate your Apple Developer Program membership.
After your enrollment is approved, sign in to App Store Connect with the same Apple ID to manage your apps.
Creating an Apple Developer account
Note: Apple sends you an activation email after your enrollment payment is processed. This can take up to 2 business days. Once your account is active, sign in to App Store Connect and then return to Base44 to continue generating your App Store files.
Use your Google Play developer account to submit your Android app in Google Play Console and manage releases. Make sure you have a Google account you can use for your business.To create your Google Play developer account:
After the scan finishes, use the results panel to see how ready your app is for the stores and let the AI chat suggest fixes. You can review each issue, apply recommended changes, and rerun the scan until you are happy with your score.
Note: You do not need a readiness score of 100 before you submit, but the higher the score, the smoother the submission process can be. Aim for a readiness score that is as high as possible, with no unresolved critical issues, before you generate store files.
To review and fix issues with the AI chat:
Look at your Readiness Score and the number of passed, partial, and failed checks in the scan results panel.
Choose how you want to fix the issues:
Apply with AI: Open the AI chat with a tailored fix prompt based on your scan results.
Copy Fix Prompt: Copy the fix prompt so you can paste it into the AI chat yourself and edit it first.
Let the AI chat apply the suggested changes.
Using AI to fix issues for app submission to stores
Check your score again:
Go back to Preview and test key flows such as browsing, sign up, log in, and checkout.
Publish the changes.
Run another app scan to see your updated readiness score and check that critical issues are resolved.
Generate the files for each store directly from the Mobile app tab so you do not have to leave the app editor. Use your scan-ready app to create the files you need to submit in the App Store and Google Play.
Important: You must be on the Builder plan or higher to download your app files.
Creating App Store and Google Play files from the Mobile app tab
When your app is ready for iOS, use your Apple Developer credentials in the Mobile app tab to generate an App Store ready IPA bundle. When generation completes, download the file from Base44, keep it in a secure location, and use it when you upload your app to App Store Connect.To create App Store files:
Go to your app editor.
Click Publish at the top-right.
Click the Mobile app tab.
Click Build Stores Files, then Create App Store files.
Add your Issuer ID, Key ID, Team ID, and upload the .p8 API key file from App Store Connect, then click Continue.
Note: To send push notifications from your app, turn on Add push notifications in this window before you continue. See adding push notifications.
Where do I find my IDs and API key file?
You need to generate your API key and then add the details to Base44. To generate your key:
Go to App Store Connect and sign in with your Apple Developer account.
Click Download to save the .p8 file to your computer and store it in a secure location. To find your Team ID:
Go to your Apple Developer account.
Look for the Team ID value listed under Membership details.
Review your app logo. Upload a new logo from your computer or generate one with AI, then click Generate Files.
When your files are ready, click Download.
Important:
Apple only lets you download each .p8 key file once. If you lose it, you need to revoke the key and create a new one.
If you do not see the Keys tab in App Store Connect, your Apple Developer account is still being processed. It can take up to 48 hours after payment for Apple to activate your account and show the Keys tab. Wait for the activation email before you try to create API credentials.
Do not share your Issuer ID, Key ID, Team ID, or .p8 file outside of trusted tools. Treat them as sensitive credentials. If you ever believe a key is exposed, revoke it in App Store Connect and create a new one.
Changing the logo in the Generate App Store files window also updates the logo you currently use for your app. Make sure you are happy with the logo before you generate the files.
When your app is ready for Android, use the Mobile app tab to generate a Google Play ready AAB bundle. After generation, download the file from Base44, keep it in a secure location, and upload it in your Google Play Console release.To create Google Play files:
Go to your app editor.
Click Publish at the top-right.
Click the Mobile app tab.
Click Build Stores Files, then Create Google Play files.
Follow the on-screen steps to review your app logo, upload a new logo from your computer, or generate a new one with AI.
Notes:
Changing the logo in the Generate Google Play files window also updates the logo you currently use for your app. Make sure you are happy with the logo before you generate the files.
To send push notifications from your app, turn on Add push notifications in this window before you generate your files. See adding push notifications.
Push notifications appear on someone’s phone even when your app is closed. You turn them on in the same window where you generate your store files, then upload credentials from your Apple Developer account or your own Firebase project. iOS and Android are separate, so do both to reach everyone using your app.
Before you begin:
For iOS: You need an active Apple Developer Program membership and an APNs auth key.
For Android: You need a Google account and your own Firebase project. The free Spark plan is enough.
Setting up push notifications for iOS
You need an APNs auth key from your Apple Developer account. Create it under Certificates, Identifiers & Profiles, then Keys, and select Apple Push Notifications service (APNs). Apple gives you a .p8 file and a 10-character Key ID.This is a separate key from the App Store Connect API key you add earlier in the same window. Each has its own Key ID, and both files end in .p8, so keep track of which is which as you download them.
Important: Apple only lets you download your APNs auth key once. Save the .p8 file somewhere safe, because you cannot download it again. If you lose it, revoke the key in your Apple Developer account and create a new one.
Click How to create an APNs auth key for the Apple steps, if you still need to create your key.
Upload your key under Upload the APNs auth key (.p8).
Check the APNs Key ID field. Base44 fills it in when you upload your key. If it stays empty, paste the Key ID you copied.
Click Continue, then finish the flow to generate and download your files.
Adding your APNs auth key in the Generate App Store files window
The built-in guide for creating an APNs auth key
Setting up push notifications for Android
You need two files from your own Firebase project. Your google-services.json file is built into your app so it can receive notifications, and your service account key lets Base44 send them. Create your project in the Firebase console, register your Android app against the package name Base44 shows you, then download both files from that same project.
Important: Your service account key lets Base44 send notifications on your behalf. Treat it as a sensitive credential and keep it private.
You send notifications from your app’s backend with the SendPushNotification integration. Each one carries a title, a message, an optional action button label, and an optional link to a specific page in your app.The first time someone opens your app, they choose whether to allow notifications. You can send to everyone who accepts.Learn more about sending push notifications.
Important: People who already installed your app receive push notifications after you generate new app files and submit an updated version to the Apple App Store or Google Play.
If your app uses login with Google, you need to add the Google Play App Signing SHA-256 fingerprint to Base44 so that Google login works in the version people install from Google Play.To find your SHA-256 fingerprint in Google Play Console:
Go to Google Play Console and sign in with your developer account.
In the side panel, go to Setup, then click App integrity.
Under App signing key certificate, copy the SHA-256 fingerprint value.
To add your Google Play App Signing SHA in Base44:
Go to your app editor.
Click Publish at the top-right.
Click the Mobile app tab.
Click Build Stores Files, then in the Google Play files section, click the More Actions icon .
Click Add Google Play SHA.
Paste your SHA-256 fingerprint into the SHA-256 Fingerprint field.
Click Save.
Adding your Google Play App Signing SHA from the Mobile app tab
Note: You only need to add the SHA if your app supports login with Google. If you change signing settings in Google Play later, update the SHA-256 fingerprint in Base44 so Google login continues to work in the distributed app.
When you register your package name in Google Play Console, Google may provide an ADI registration snippet to verify your package name ownership. If prompted, you need to add this snippet to your Base44 app. Google is rolling out this requirement gradually, so not all accounts are affected yet.To add your Google Snippet in Base44:
Go to your app editor.
Click Publish at the top-right.
Click the Mobile app tab.
Click Build Stores Files, then in the Google Play files section, click the More Actions icon .
Click Add Google Snippet.
Paste your ADI snippet into the Google Snippet field.
Click Save & Build.
Adding Google snippets for your app submission.
Clicking Save & Build automatically triggers a new Android build. Your updated files are ready to download in about 5 minutes. You only need to add the Google Snippet if Google Play Console prompts you to register your package name. If you are not prompted, you can skip this step.
After you generate your App Store and Google Play files, complete submission in your Apple and Google dashboards.Base44 helps you get your app ready, but everything that happens after you submit in App Store Connect or Google Play Console is between you and the app stores. You are responsible for checking your submission status, responding to store emails, and applying any changes the stores request.Follow our step-by-step visual guide for submitting your app to Apple App Store and Google Play Store.
Important:
Base44 cannot guarantee that an app is approved, even with a high readiness score.
Base44 support does not check on the status of your submission, contact Apple or Google on your behalf, or manage store review feedback for you. Take any feedback directly from the app stores and make changes yourself or work with a partner.
Your Google Play package name: When creating your app listing in Google Play Console, you are asked to enter a package name. Your Base44 package name is com.base[app-id].app, where [app-id] is your Base44 app ID. You can find your app ID in the URL when you are in your app editor. For example, if your editor URL contains 69e0c4bdd31bdu8fda51775g, your package name is com.base69e0c4bdd31bdu8fda51775g.app.
Prepare your store listing assets
When you submit your app in App Store Connect and Google Play Console, you need assets for your store listings. Before you start the submission forms, prepare:
A short and long description for your app
Screenshots of your app on common phone sizes, and tablet screenshots if you plan to support tablets. You can capture screenshots by opening your published app on a device or simulator, navigating through your main flows, and taking native device screenshots that you upload in each store.
Your app icon and any required feature graphics that follow Apple and Google size and format guidelines
A support URL and privacy policy URL from your Base44 app
If you see a message similar to “UNAUTHENTICATED: App Store Connect rejected the authentication token”, your App Store Connect API key details are missing, invalid, or expired.To fix error 401:
Go to App Store Connect and sign in with your Apple Developer account.
Click Users and Access, then click Integrations.
Check that the Issuer ID, Key ID, and Team ID values you entered in Base44 match the values shown in App Store Connect.
Confirm that the .p8 API key file you uploaded is the correct file and that the key has not been revoked or expired.
If anything looks incorrect, generate a new API key in App Store Connect, download the new .p8 file, update all fields in Base44, and try generating the files again.
Error 403 when generating iOS IPA files
If you see a message similar to “PERMISSION_DENIED: This operation is not allowed. Your App Store Connect API key may need the Admin role”, the API key you are using does not have enough permissions.To fix error 403:
Go to App Store Connect and sign in with your Apple Developer account.
Click Users and Access, then Integrations.
Check the Access role for the API key you are using.
If the key is not set to Admin, create a new key:
Click + to add a new key.
Enter a name and select the Admin role.
Click Generate and download the .p8 file.
In Base44, update the Issuer ID, Key ID, Team ID, and upload the new .p8 file, then try generating the App Store files again.
Error 409 when generating iOS IPA files
If you see a message similar to “ALREADY_EXISTS: You’ve reached the limit for iOS Distribution certificates. Revoke an existing iOS Distribution certificate in App Store Connect to create a new one”, your Apple Developer account has reached the limit for active iOS Distribution certificates.Every time you generate an IPA in Base44, Apple creates an iOS Distribution certificate. The standard Apple Developer Program allows up to 3 active production distribution certificates at the same time.To fix error 409:
Go to your Apple Developer account and open Certificates, Identifiers & Profiles.
Click Certificates and filter to iOS Distribution certificates.
Revoke at least one iOS Distribution certificate that you no longer need.
Try generating the App Store files again from the Mobile app tab in Base44.
Note:
An iOS Distribution certificate can usually be revoked after an app has been approved, without affecting people who already installed the app.
Apple typically allows:
Up to 3 active production/distribution certificates for the standard Apple Developer Program
Up to 2 active enterprise distribution certificates
Up to 12 development certificates
App Store or Google Play rejection for charging through Stripe
If your app was rejected because it charges for digital content through Stripe, the fix is to move the purchase off the app. Apple and Google require their own billing systems for anything digital, such as a subscription, a course, or an in-app feature, and there is no setting that makes a Stripe purchase acceptable to them.You can keep the paywall itself in your app. What has to change is where the payment happens.To recover a rejected app:
Move the purchase to the web version of your app, so people pay there rather than inside the mobile app.
Keep the paywall in your mobile app, but have it tell people to go to your website. Remove any button that opens a Stripe checkout, and make sure any link you keep opens a browser rather than a payment flow inside the app.
Have your mobile app check who has paid and show or hide the content accordingly.
Publish the change and generate your app files again.
Reply to the reviewer through Apple’s Resolution Center or Google Play’s appeals process, explaining that the purchase now happens on the web.
Resubmit your app.
Google Play rejection for a missing billing permission
If Google Play rejects your app for a missing com.android.vending.BILLING permission, this is not something you can add. The permission sits at the platform level rather than in your app, so no change in Base44 clears it.Contact Base44 support with your app ID. This one needs a platform-level fix.
App Store rejection due to HealthKit entitlement
If your app is rejected by App Store Connect with an error about a missing NSHealthShareUsageDescription key in Info.plist, this is caused by a HealthKit entitlement included in the iOS build.Base44 does not support HealthKit, and there is currently no way to add NSHealthShareUsageDescription to the build configuration. If your app does not use HealthKit, you do not need to take any action on your end. This is a known limitation of the current iOS build.
Bundle ID or signing key mismatch when uploading an update
If you previously uploaded a native app to the stores and now generate files from Base44 for the same brand, you might see errors about a Bundle ID or signing key mismatch.Base44 automatically configures a Bundle ID and signing key for your app files. These values cannot be changed inside the generated IPA or AAB files. If the values do not match a previous version that you uploaded manually or from another tool, the stores block the update.To resolve Bundle ID or signing key mismatches:
Review the existing app listing in App Store Connect or Google Play Console and compare the Bundle ID and signing key with the values from your Base44 build.
If they do not match and you cannot update the existing listing, create a new app entry in the store and submit the Base44 build as a new app.
Update your icon, app name, or description if needed so people can clearly identify the new app.
Permissions, privacy policy, and app review feedback
Every mobile app package includes device-level permissions. Base44 uses AI to scan your app and set the permissions it needs. These permissions are not editable in the Base44 interface. Each permission also gets a purpose string, the short explanation the store shows when your app asks for access, generated in all 24 languages Base44 supports. Apple’s automated review reads these strings, so this helps your app clear review.Apple and Google expect your privacy policy and store listing to explain which types of data your app collects, how you use it, and which device features your app accesses.If your app is rejected due to permissions or privacy issues:
Read the rejection email carefully to see which permission or behavior the store is concerned about.
Update your privacy policy and terms pages on your Base44 app so they:
Describe the types of data your app collects (for example, location, camera, or microphone)
Explain why you collect the data and how people can contact you about privacy
Make sure links to your privacy policy and terms appear before people register or sign in (for example, in your home page footer or login screen).
Resubmit your app after updating the content.
Main URL and access to legal pages
Base44 automatically chooses the main entry URL for your mobile app based on your published app. You cannot currently select a different start page just for the app.Apple and Google require that people can access your Privacy Policy and Terms of Use before they create an account.To keep your app compliant:
Make sure your privacy and terms pages are live on your Base44 app.
Add visible links to these pages from the entry page of your app, such as in the footer or a menu.
If your app uses a gated or members-only home page, ensure that privacy and terms links are still accessible before sign-up (for example, from the login or sign-up page).
Click a question below to learn more about submitting your Base44 app to the Apple App Store and Google Play.
Do I need to reach a readiness score of 100 before I submit?
You do not need a readiness score of 100. A higher score usually means your app follows more store guidelines and may have a smoother review. Focus on resolving all critical issues and as many partial issues as you can before you submit.
Can I submit to only one store, not both?
Yes. You can submit your app to only one store. You do not have to publish to both stores. Use the App Store scan and Create App Store files if you only need an iOS app, or use the Google Play scan and Create Google Play files if you only need an Android app.
What happens if the scan still shows failed checks after fixes?
You can still generate files and submit your app, but there is a higher chance that Apple or Google ask for changes during review. It is best to reread the scan descriptions for each failed check, decide whether the risk is acceptable for your app, and run another scan after any updates so you see the latest readiness score.
Can Base44 submit my app to the stores for me?
Base44 helps you scan your app against store guidelines, improve it with AI, and generate the IPA and AAB bundles. You still need to submit the app through your own App Store Connect and Google Play Console accounts, where you control the listing details, pricing, and release settings.
Can Base44 support check on my submission or talk to the app stores for me?
No. Base44 support does not track the progress of your submission, contact Apple or Google, or manage conversations with the review teams. To see the status of your app, sign in to App Store Connect and Google Play Console, read their emails, and follow any instructions they provide.
Do I need a custom domain to submit my app?
No. You do not need a custom domain to submit your app to the Apple App Store or Google Play. Base44 can scan your app and generate the App Store and Google Play files using your default Base44 URL. A custom domain is optional and can help with branding and SEO, but it is not required for store submission.
Do I need to resubmit my app every time I update my Base44 app?
No. Your Base44 mobile app loads your live app in a web view. This is a native wrapper that opens only your app URL, so when you change content or design in Base44 and publish your app, those updates usually appear in the app without submitting a new version to the Apple App Store or Google Play.You only need to generate new app files and submit an update when something in the app shell changes, such as the app name, icon, or bundle identifiers. The same applies if you add push notifications, or a feature that needs new device permissions. In those cases, regenerate the files in Base44 and submit an updated version to the stores.
Which native features does the Base44 mobile app support?
Your Base44 mobile app runs your web experience inside a secure web view. You can also add push notifications, which you set up when you generate your App Store or Google Play files.Current limitations:
Full offline mode and HealthKit are not supported yet.
Some native capabilities may still require additional review by Apple or Google, depending on the permissions your app needs.
Base44 continues to expand native feature coverage over time. Check product updates and release notes to see which new native features are available for your app.
Can I charge for digital content in my mobile app?
Not yet. Apple and Google both require their own billing systems for anything digital, and Base44 does not support them yet, so the purchase has to happen on the web for now.Counts as digital, so it cannot be bought in the app:
Premium or subscription tiers
Unlocking features or content inside your app
Virtual currency, credits, or extra AI generations
Counts as physical or a service, so Stripe is fine:
A physical product you ship
Booking a real-world service, such as an appointment or a table
A service delivered outside your app, such as coaching
Donations
If you are not sure which yours is, treat it as digital. Apple in particular rejects borderline cases.The usual approach in the meantime is to sell the subscription on the web version of your app with Stripe, and have your mobile app check who has paid and show or hide the content. You can show a paywall in the app and point people to your website, as long as nothing in the app opens a payment flow.Third-party purchase plugins are not an alternative. RevenueCat’s native SDK and Capacitor in-app purchase plugins need access to the native layer that Base44 apps do not expose, so they do not work, they can break your build, and they still get your app rejected.
How long do people stay logged in to the app?
Base44 uses token-based authentication with a default session duration of up to 90 days. Someone who signs in to your app stays signed in on that device until they sign out or clear the app’s cache, or until the 90-day period ends. You do not need to configure this manually.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.
