Firebase AUTHENTICATION_FAILED on some devices

[jehadmashhour]

I use the Firebase remote config SDK , i have noted that on some devices (nearly 15 users) that the Firebase SDKs not working .

The error message is : Failed to get Firebase Instance ID token for fetch

The log shows the following error :

com.google.firebase.remoteconfig.FirebaseRemoteConfigClientException: Failed to get Firebase Instance ID token for fetch. at c.i.c.r.a.m.a(com.google.firebase:firebase-config@@19.1.1:30) at c.i.c.r.a.j.then(Unknown Source:4) at com.google.android.gms.tasks.zzf.run(Unknown Source:3) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) at java.lang.Thread.run(Thread.java:784)
Caused by: java.io.IOException: AUTHENTICATION_FAILED at c.i.c.m.P.then(com.google.firebase:firebase-iid@@20.0.2:7) at com.google.android.gms.tasks.zzd.run(Unknown Source:7) ... 3 more

Notes :

Some of devices have the same issue -> Huawei DUB-LX1 , HUAWEI JKM-LX1 , Samsung SM-A750F , Samsung SM-J700H

Let me know if you need my google api key .

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[chong-shao]

Hi @jehadmashhour , it would be better if you can report this issue by filing a Firebase Support ticket https://firebase.google.com/support, from there it will be easier for you to share your account information and credentials

[jaanmurumets-sk]

We have reported issue to google https://issuetracker.google.com/issues/143413382 and there is acknowledge by Google of problem:

"We got information from Firebase support that this AUTHENTICATION_FAILED error is caused by GPS (Google Play Services) but fix date is not clear yet."

[pnehren]

We are also affected with a custom device without Play Services.

[arbutler]

I'm still seeing the AUTHENTICATION_FAILED failure on a Samsung S8 device using the latest google play api's according to the release notes:

build.gradle (app level)
dependencies {
...
implementation 'com.google.firebase:firebase-iid:20.1.2'
implementation 'com.google.firebase:firebase-messaging:20.1.3'
implementation 'com.google.firebase:firebase-bom:25.1.1'
implementation 'com.google.android.gms:play-services-auth-api-phone:17.4.0'
implementation 'com.google.android.gms:play-services-base:17.2.0'
implementation 'com.google.android.gms:play-services-basement:17.2.0'
implementation 'com.google.android.gms:play-services-tasks:17.0.1'
...
}

Log:
...
03-20 14:36:53.917 E/FirebaseInstanceId(18116): Topic sync or token retrieval failed on hard failure exceptions: AUTHENTICATION_FAILED. Won't retry the operation.
03-20 14:36:53.919 D/MainActivity(18116): getInstanceId failed
03-20 14:36:53.919 D/MainActivity(18116): java.io.IOException: AUTHENTICATION_FAILED
03-20 14:36:53.919 D/MainActivity(18116): at com.google.firebase.iid.zzs.zza(com.google.firebase:firebase-iid@@20.1.2:82)
03-20 14:36:53.919 D/MainActivity(18116): at com.google.firebase.iid.zzs.zza(com.google.firebase:firebase-iid@@20.1.2:96)
03-20 14:36:53.919 D/MainActivity(18116): at com.google.firebase.iid.zzx.then(com.google.firebase:firebase-iid@@20.1.2:4)
03-20 14:36:53.919 D/MainActivity(18116): at com.google.android.gms.tasks.zze.run(com.google.android.gms:play-services-tasks@@17.0.1:5)
03-20 14:36:53.919 D/MainActivity(18116): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
03-20 14:36:53.919 D/MainActivity(18116): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
03-20 14:36:53.919 D/MainActivity(18116): at java.lang.Thread.run(Thread.java:762)
...

[ckurban]

Any update in this issue as we are facing the failure in our solution?

[jehadmashhour]

I'm still having the same issue , a one user who has the same issue said to me that he did reset device factory and the firebase issue is resolved !! , incredible .

Please any help , we think the issue is related to the users devices , but we don't know exactly what is the reason .

[pnehren]

I think that they stopped supporting devices with no or old versions of play services...on my device without play services firebase-config stopped working with versions higher 19.1.0. Devices with play services or emulators have no problems...

Sad that there is no information about that.

[jehadmashhour]

I was think that , but after adding some logs to check the google play services is installed or not , and what is the version , I have noticed that these devices also have the same issue with the latest version.

In addition , I have contacted a user who have the same issue and he said that his device has the latest google play services , but no avail .

Why the issue is resolved by doing reset device factory !!!!

[jehadmashhour]

Any update in this issue as we are facing the failure in our solution?