How to Package Lovable and Emergent AI Apps into Signed .aab Files for the Google Play Store

Satish Satish — Wed, 30 Sep 2026 07:26:52 +0000

Building a working prototype in AI vibe-coding platforms like Lovable or Emergent takes hours, but shipping that project to the Google Play Store is where most developers hit a wall. Neither platform has a one-click "Publish to Google Play" button, and the Google Play Console strictly requires a cryptographically signed Android App Bundle (.aab).

Because Lovable and Emergent generate completely different codebases under the hood, you have to use the right build pipeline for each platform—otherwise you will run into blank white screens on startup or broken Google OAuth logins.

Here is the quick architecture breakdown and how to compile each one for production.

Wrapping a Lovable App (React + Vite + Capacitor) Lovable generates a standard browser-based React + Vite + Tailwind single-page application. To ship it on Android, you need to export your repository to GitHub, build the production dist folder locally, and wrap it inside a native Android WebView using Ionic Capacitor:

Bash
npm install
npm run build
npm install @capacitor/core @capacitor/cli @capacitor/android
npx cap init "YourAppName" "com.yourcompany.appname" --web-dir dist
npx cap add android
npx cap sync android

The Two Biggest Lovable-to-Android Bugs:
The Blank White Screen on Launch: By default, Vite uses absolute / asset paths, which fail to resolve inside an Android WebView. You must add base: './' inside your vite.config.ts file before running npm run build.

Firebase Google Sign-In Error 403 (disallowed_useragent): Standard web signInWithPopup() calls are blocked inside embedded Android WebViews. You have to register your Android SHA-1 signing certificate in Firebase and bridge native Android authentication into signInWithCredential().

👉 Full Tutorial & Code Snippets:[https://global-money-info.blogspot.com/2026/09/how-to-publish-lovable-ai-app-to-google.html]

Compiling an Emergent Mobile App (React Native + Expo EAS) If you built your mobile project using Emergent's mobile agent workflow, your codebase is already built on React Native and Expo. You do not need Capacitor or a heavy local Android Studio installation. Instead, you can compile and sign your .aab binary in the cloud using Expo Application Services (EAS Build):

Bash
npm install -g eas-cli
eas login
eas build:configure
eas build --platform android --profile production

Watch Out for Standalone Production Crashes:
When moving an Emergent app out of the Expo Go QR preview and into a standalone .aab binary, three issues commonly break the build:

Missing .env Variables: EAS Build ignores local .gitignore environment files, causing your app to crash on launch unless you push your EXPO_PUBLIC_ keys to Expo's cloud environment.

Hanging OAuth Redirects: Deep links that worked on exp:// in development will fail in production unless you configure a custom URL scheme in app.json and whitelist your remote EAS Keystore SHA-1 fingerprint.

Google Play AD_ID Rejections: Undeclared advertising permissions injected by dependencies will block your Play Console rollout unless stripped via blockedPermissions.

👉 Full Tutorial & Code Snippets:[https://global-money-info.blogspot.com/2026/09/how-to-export-emergent-ai-mobile-app.html]

If you are currently stuck in Google Play's 12 testers for 14 days closed testing track with an AI-built app, drop a comment below with the stack you are using!

for emergent app use this link : https://global-money-info.blogspot.com/2026/09/how-to-export-emergent-ai-mobile-app.html
for loveable app use this one : https://global-money-info.blogspot.com/2026/09/how-to-publish-lovable-ai-app-to-google.html

DEV Community: Satish Satish

How to Package Lovable and Emergent AI Apps into Signed .aab Files for the Google Play Store