Firebase Google Sign-In now works in your APKs and AABs! If your app uses Google login, you can now build Android apps where users sign in with their Google accounts just like they do on your website.
What This Means
Previously, if your web app used Firebase Authentication with Google Sign-In, it would work perfectly in the browser but fail when you built it as an APK. Users would tap “Sign in with Google” and nothing would happen — or they’d get an error.
Now, when you build your app with AI Studio APK, Google Sign-In works natively on Android. Your existing Firebase code doesn’t need to change — we handle the Android-specific setup automatically.
How It Works
Here’s what happens when a user taps “Sign in with Google” in your APK:
- The app detects the Google Sign-In request
- It opens the native Android Google account picker
- User selects their Google account
- The app securely passes the credentials to Firebase
- User is signed in — same as on your website
From the user’s perspective, it feels like any other Android app with Google login. From your perspective, your existing Firebase code just works.
What You Need to Set Up
To enable Google Sign-In in your APKs, you’ll need to connect your Firebase project. Here’s the simplified process:
Step 1: Get Your Package Name
When building your app, you’ll choose an Android package name (like com.yourcompany.yourapp). This needs to match exactly in Firebase.
Step 2: Add Your App to Firebase
- Go to Firebase Console
- Select your project
- Click “Add app” → “Android”
- Enter your package name (same as in the build form)
- Add the SHA-1 fingerprint shown in our dashboard
- Download the
google-services.jsonfile
Step 3: Upload to AI Studio APK
In our dashboard, you’ll see a “Firebase Google Sign-In Setup” section. Just upload your google-services.json file there. We’ll automatically extract the necessary configuration.
Step 4: Build and Test
Build your APK or AAB as usual, install it on your device, and test Google Sign-In. It should work immediately!
Common Setup Issues (And How to Fix Them)
“Error 10” or “Developer Error”
This usually means the SHA-1 fingerprint in Firebase doesn’t match your build. Make sure you:
- Use the SHA-1 shown in our dashboard (not a local debug key)
- Use the exact same package name in Firebase and our build form
Works on Web, Not in the App
If Google Sign-In works in your browser but not in the built APK:
- Make sure you uploaded
google-services.jsonin our dashboard - Verify Google is enabled as a sign-in provider in Firebase
- Rebuild the APK after uploading the config file
Publishing to Google Play Store
If you’re publishing an AAB to Google Play, there’s one extra step:
- After publishing, go to Play Console → Release → Setup → App signing
- Copy the SHA-1 for the “App signing key”
- Add this SHA-1 to your Firebase Android app (in addition to the one from our dashboard)
- Download an updated
google-services.jsonand re-upload it
This ensures Google Sign-In works for users who download from the Play Store.
What Doesn’t Change
The great news: you don’t need to change your code. Keep using Firebase Auth exactly as you do now. We handle all the Android-specific bridging automatically.
Ready to Add Google Sign-In?
If your app uses Firebase Authentication with Google, you can now offer the same seamless login experience in your Android app.
👉 Build your app with Google Sign-In at aistudioapk.com
Need help with the setup? Join our community at r/aistudioapk