java.io.IOException: FIS_AUTH_ERROR in Android Firebase

Question

I'm getting following error with Firebase services.

 E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: FIS_AUTH_ERROR. Won't retry the operation.
 D/AndroidRuntime: Shutting down VM
    com.google.android.gms.tasks.RuntimeExecutionException: java.io.IOException: FIS_AUTH_ERROR
        at com.google.android.gms.tasks.zzu.getResult(Unknown Source:15)
        at com.myApp.MainActivity$2.onComplete(MainActivity.java:349)
        at com.google.android.gms.tasks.zzj.run(Unknown Source:4)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:237)
        at android.app.ActivityThread.main(ActivityThread.java:7804)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
     Caused by: java.io.IOException: FIS_AUTH_ERROR
        at com.google.firebase.iid.zzs.zza(com.google.firebase:firebase-iid@@20.1.0:82)
        at com.google.firebase.iid.zzs.zza(com.google.firebase:firebase-iid@@20.1.0:96)
        at com.google.firebase.iid.zzx.then(com.google.firebase:firebase-iid@@20.1.0:4)
        at com.google.android.gms.tasks.zzd.run(Unknown Source:5)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:919)

Here is the part of the code where crash occurs:

        FirebaseInstanceId.getInstance().getInstanceId().addOnCompleteListener(new OnCompleteListener<InstanceIdResult>() {
            @Override
            public void onComplete(@NonNull Task<InstanceIdResult> task) {
                if (task.getResult() != null && task.isSuccessful()) {
                    // Get new Instance ID token
                    firebaseToken = task.getResult().getToken();
                    prefs.edit().putString("firebaseToken", firebaseToken).apply();
                    registerToken();
                }
            }
        });

The error occurs in onComplete. Here is firebase dependencies which I use:

    // FIREBASE
implementation 'com.google.firebase:firebase-analytics:17.2.3'
implementation 'com.google.firebase:firebase-messaging:20.1.2'
implementation 'com.google.firebase:firebase-appindexing:19.1.0'
implementation 'com.google.firebase:firebase-ads:19.0.0'
implementation 'com.google.firebase:firebase-crashlytics:17.0.0-beta01'

I found this issue on Github related with my crash but there is no conclusive solution at all. Does anybody encountered this kind of issue? Thanks in advance.

Note: I don't use Flutter however the error occurs without flutter too. Device is Samsung A51 with Android 10.

Note 2: Firebase removed firebase-core. Problem can be related with that.

Answer 1

All you have to do is just make the API key you are using has permission to the following APIs:

1. Firebase Installations API
2. Firebase Cloud Messaging API
3. FCM Registration API
4. Cloud Messaging

You can change the restrictions from your google cloud -> APIs & Services -> Credentials

Answer 2

All of a sudden the same error (FIS_AUTH_ERROR) appeared in one of my apps, where I use Firebase Cloud Messaging. Everything was working without any issues, and suddenly the app was not able to get the app/device token with getToken(). After hours of research I discovered something, which solved the problem for me. I decided to check the values in the file google-services.json to see if they match the corresponding parameters in the Firebase Console at the settings of my project. First I downloaded a brand new google-services.json, which I compared with the one I already had in my app's folder, and they both were simply the same without any difference. In the Firebase Console I was checking one by one the Project ID, the Project number, etc. When I got to the Web API Key its value looked quite similar to api_key from google-services.json, but still both values were different. Then I decided to edit the file, and in the place of api_key I've put the value from Web API Key. Then I've cleaned the project and rebuilt, and afterwards everything again started working just perfectly.

Answer 3

The FIS_AUTH_ERROR means Authentication for Firebase installation sdk has failed. If you use a service that depends on Firebase installation sdk (or FIS), you need a valid authorization.

According to Firebase cloud messaging v20.1.1 release note:

Apps that use the Firebase auto-initialization process and the Gradle plugin to convert google-services.json into resources are unaffected. However, apps that create their own FirebaseOptions instances must provide a valid API key, Firebase project ID, and application ID.

So if you (or a service using fcm added by you) uses FirebaseOptions, it has to pass some additional values for the FIS.

Solutions

• Downgrade to v20.1.0 of firebase-messaging (Not recommended though. It's like running from the problem)
• Provide additional keys if you use FirebaseOptions

Answer 4

I found a solution to this problem

1) in Android Studio , in left panel "Project" swich Android view to Project view

2) copy file google-services.json NOT into "app" folder (like it says in instruction) ... but copy this file into the upper root folder

and it will work

Answer 5

In addition to Steeve's answer, the Firebase Messaging credentials should be restricted to these 3 Selected APIs:

Firebase Cloud Messaging API
Firebase Installations API
FCM Registration API

Go to the credentials on Google Cloud Console (APIs & Services -> Credentials), Click on the relevant key and select the 3 APIs above.

If you restrict usage to your Android apps, make sure to add SHA-1 fingerprints for your specific app. If you use internal app sharing, make sure to also add the SHA-1 of the internal app bundle as described here.

Answer 6

The correct fix is to add "Firebase Installations API" to the restrictions of your Google API Key (see google-services.json).

In your Google Cloud console, it's in APIs & Services, then Credentials. Open the API Key is look at "Restrictions".

No need to recompile.

Answer 7

If you have recently changed google-services.json file, you need to remove build file of your project and rebuild the project.

update: I got this error when I was testing my app in debug mode. In release version it was solved and worked correctly.

https://stacklearn.ir/course/android-introductory-training-course

Answer 8

This is for sure, (if you finished all configuration) then version of firebase messaging is not compatible with other dependencies.

you can check dependencies here, my solution was to downgrade from implementation 'com.google.firebase:firebase-messaging:20.1.3' to implementation 'com.google.firebase:firebase-messaging:20.1.0'

Answer 9

@mahdi-malv, @ambrose-bako, @steeve are right.

---

Firebase Android SDK updates on February 27 (M65) and afterwards introduced a new infrastructure service, the Firebase Installations SDK which comes with a dependency on the Firebase Installations API.
Firebase Installations requires valid Firebase options API key, project ID, and application ID (a.k.a. "appId") in order to successfully communicate with Firebase servers.

Errors during communication with the Firebase Installations API indicate invalid Firebase options or misconfigurations regarding API keys.

To mitigate the issue

• make sure that your application is using valid Firebase options from the latest google-services.json file from your Firebase console: Firebase options: instructions and background.
• If you use API restrictions, make sure that the API key used by your application is white-listed for the Firebase Installations API (and for your application): API restrictions: instructions and background
• Regarding Application restrictions: Either set the radio button to None or make sure that your app is white-listed (with the correct SHA-1 certificate).

---

For details, please visit:
https://firebase.google.com/support/privacy/init-options

Answer 10

Just in case, renamed the package name, deleted google-services.json, and going into firebase checked firebase-database (read\write).

Then deleted the old package and its hash from the firebase project settings, after adding a new package and hash, received a new google-services.json, after that everything worked

I think the error is that a package was specified in firebase but there was no hash

Answer 11

Maybe a bit late, but hopefully this info may help someone out there.

I had the problem too with firebase-messaging:21.0.1. I followed all the instructions given in this thread, but nothing helped.

What was curious is that before the error E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: FIS_AUTH_ERROR. Won't retry the operation appeared the logcat showed Firebase Installations Service is unavailable.

After some investigation the solution was as follows. I used a self-signed certificate on my dev-server and trusted it in my app as described here: https://developer.android.com/training/articles/security-ssl.html#CommonProblems
Somehow this broke the whole SSL handshake stuff in android and I couldn't authenticate to the Firebase Installations Service anymore. After removing this and using plain http for my dev environment everything works again like a charm. (of course, for my prod server I'm using a ROOT trusted certificate, so no problems here)

Answer 12

Hope this helps someone:

In my situation, I used self-signed ca. So I need to use network-security-config.xml

After huge try and error, finally I add system directory in trust-anchors like below, FIS_AUTH_ERROR is gone and Firebase worked.

<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
    <base-config>
        <trust-anchors>
            <certificates src="system" />  <!-- for Firebase -->
            <certificates src="user" /> <!-- for tooling.   Ex:Charles --> 
            <certificates src="@raw/ca_1"/> <!-- my self-signed ca-->
        </trust-anchors>
    </base-config>
</network-security-config>

Answer 13

Best solution worked for me is upgrading dependencies and clean & re-build project

Answer 14

I had fight with this exception almost 2 days, and now solved.

1. First make sure the restrictions API as mentioned Ambrose's answer
2. add ALL SHA-1 on firebase console and cloud console credential, in my case I need 4 SHA-1, from:

• debug keystore
• release keystore
• firebase distribution (if using .AAB )
• release certified from playstore's signing like this:

I think add the last SHA-1 to cloud console make my app works nicely. Hope this answer will help other. Happy code!

Answer 15

I had the same problem when I redownloaded Android Studio on a new computer. I hadn't set up Google Play services in my SDK Tools, and my emulator didn't have the Google Play store. See this discussion https://github.com/firebase/firebase-android-sdk/issues/1286#issuecomment-951403455

Also note that FirebaseInstanceId requires Google Play services to create a token and it will fail on devices without it.

After creating a new Emulator with Google Play and restarting my IDE, the problem was solved.

Answer 16

you need to add

apply plugin: 'com.google.gms.google-services'

implementation platform('com.google.firebase:firebase-bom:x.x.x')
implementation 'com.google.firebase:firebase-analytics'

to your app/build.gradle , these code will give to you when create google.services file on firebase console

Answer 17

To remove this line:

FirebaseApp.initializeApp(getApplicationContext());

and let the SDK auto-initialize with the google-services.json solved it for me.

Answer 18

it's very-very confused, how I search a soltion for this error (with FIS_AUTH_ERROR), but with @Andreas Rayo Kniep's answer, especially with CURL command test, I know what's wrong with my problem.

CURL command to test firebase conf : curl -H "content-type: application/json" -d "{appId: 'YOUR-APP-ID', sdkVersion: 't:1'}" https://firebaseinstallations.googleapis.com/v1/projects/PROJECT-NAME/installations/?key=API-KEY;

I must change API key at google-services.json, because it's status : PERMISSION_DENIED, message : Requests from referer are blocked.

so I create new API key from google console, with restrict API for : Cloud Messaging, FCM Registration API, Firebase Cloud Messaging API, Firebase Installations API. and application restriction : None.

and problem was fixed!

I use : com.google.firebase:firebase-messaging:20.1.0 firebase_messaging: ^10.0.2

Answer 19

In my case Crashlytics reports this only on a few Samsung devices, I think this is something with how Google services are implemented on certain Samsung devices so there is not much you can do.

Answer 20

Tried all solutions above. They didn't work for me. But then I deleted the app from the device and installed again. This helped.

Answer 21

Method 1

Go to your google cloud console https://console.cloud.google.com/

Then choose your project and check auto-created by firebase token in credentials -> API keys. Select your key and check if there are any restrictions you have to configure. Clear the restrictions and again build your app newly.

Method 2

Check your fingerprints -> project settings -> in firebase console and cross check with your keystore file's fingerprint algorithms. Then download your new google-services.json file and replace it with your existing file in android/app

Answer 22

For me, I forgot we had implemented SSL pinning in the early stages of our app, so we had to download and trust the root Google Trust Services CA.

Thanks to this GitHub thread for reminding me to consider SSL pinning: https://github.com/invertase/react-native-firebase/issues/5522#issuecomment-884960850

I guess a good giveaway was that curl would work fine, but it would fail on Android.

Answer 23

For me, it just was:

build > clean project

Because I was changing google-services.json file many times.