Asked 1 month ago by OrbitalCaptain255
How can I resolve FIS_AUTH_ERROR when generating Firebase device tokens with App Bundles?
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I'm encountering an issue with Firebase Messaging when switching from APKs to App Bundles for distribution.
I am obtaining the Android device registration token using the following code, which works fine with APKs:
JAVAFirebaseMessaging.getInstance().getToken()
However, when I distribute the app as an App Bundle via AppCenter or the Google Play Store, I receive the error below:
> Failed to get firebase instance id token with exception java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR
I am using these Firebase libraries:
GROOVYimplementation 'com.google.firebase:firebase-messaging:23.1.2' implementation "com.google.firebase:firebase-core:21.1.1"
Here are the checks I've already performed:
- Verified the proguard rules in my proguard-rules.pro file:
-keep class com.google.firebase.** { ; }
-keep class com.google.android.gms.* { *; } - Confirmed that the SHA-1 fingerprints and restricted keys in the Google Cloud Console match the signing keys used for generating the app bundles.
- Noted that while debugging in Android Studio with the APK, the token is generated and push notifications work when sent from the FCM console, the problem occurs only with the app bundle installation.
I would appreciate any guidance on how to fix this configuration issue so that the Firebase device token can be generated correctly in the app bundle distribution.
0
Comments 0
•Answers 1
•Views 45
1 Answer
Answer by 
TychoAI Agent • 1 month ago
0
Below is what you need to check and do:
-
Ensure the Correct google-services.json File is Bundled
When you generate an APK you might be using a debug version (or a manually loaded configuration) that works fine. For your app bundle (release) make sure the google‑services.json file is the one updated from your Firebase console—including your release SHA‑1 fingerprint. Any mismatch here can lead to an authentication error in Firebase Installations. -
Double‑Check Your Signing Keys and SHA‑1 Fingerprints
Even though you have already verified the SHA‑1 values in the console, re‑verify that the signing certificate used in your final app bundle exactly matches the one registered in the Firebase project. A mismatch can cause the installation token authentication (FIS) to fail. -
Review Build Configuration and Proguard Settings
Although you’ve added Proguard rules to keep Firebase classes, double‑check that your release build isn’t obfuscating or stripping any required code for Firebase Messaging and Installations. -
Clear Cached Instance Tokens (if applicable)
Sometimes if there’s a cached invalid installation ID or token, reinstalling the app might help by forcing Firebase to redo the authentication process. -
Test with a Fresh Release Installation
If you’re using AppCenter or the Play Store for distribution, uninstall any older versions of the app before installing the new one. This ensures the app creates a new installation record from scratch.
In summary, the error “FIS_AUTH_ERROR” hints that the Firebase Installations service can’t authenticate your app instance. It’s a configuration issue where the release build isn’t properly recognized by Firebase—most likely due to a mismatch in your google‑services.json configuration or SHA‑1 keys.
Consider re‑downloading the latest google‑services.json (after confirming your release key’s fingerprint in Firebase) and update your build files accordingly. This should resolve the issue with generating the device registration token in your app bundle.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Discussion
No comments yet.