IssueTracker

Hello,

Thank you for contacting the Google Cloud support team.

I have gone through your reported issue, however it seems like this is an issue observed specifically at your end within your project environment. It would need more specific debugging and analysis. To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking here. Our support team will prioritize your request and provide you with the assistance you need.

Please note that the Issue Tracker is primarily meant for reporting commonly observed issues and requesting new features. For individual support issues, it is best to utilize the support ticketing system. I'm going to close this issue which will no longer be monitored. If you have any additional issues or concerns, please don’t hesitate to create a new issue on the Issue Tracker.

Thank you, we appreciate your cooperation!

That error message is usually one of two things:

• Something is wrong with the specific devices or their ability to communicate with FCM servers. This isn't typically something that we can fix because it's either a hardware problem or a firewall problem. Further diagnosis would require a bug report. This doesn't usually represent a systemic problem, just a specific one related to that device.
  For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice
  Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
  Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

• The developer is providing invalid credentials or other invalid configuration, either via the google-services.json file or by manually constructing a FirebaseOptions object with invalid values. If this were the case, we would expect push messaging to never work for these users (i.e. registering for a token would always return AUTHENTICATION_FAILED).

Some more questions:

• Were the developers ever able to reproduce this on a local device?

• What API levels are the developers seeing these errors on?

• How are the developers creating a FirebaseApp instance? What versions of the Firebase SDKs are they using?

I'm seeing this issue in live among small percent of users.

Devices: different Sony TVs (BRAVIA 4K 2015, BRAVIA 4K GB, BRAVIA 4K GB ATV3), Panasonic GX655 (app is Android-TV only)

Different locations: Aurope, Asia

On top of that all problematic installations did successfully authorized using Firebase Auth (anonymous).

One user report I've got recently shows that client was constantly getting this error since at least 1 July. This user still getting this issue after cleaning app's data from system settings.

I do not see any correlations between issue and "installations with new SDK". There are a lot of users using same app version (same SDKs) without this issue. New users and 1-3-6 month users.

Non-fatal Exception: java.io.IOException: AUTHENTICATION_FAILED
       at com.google.firebase.iid.GmsRpc.handleResponse(GmsRpc.java:81)
       at com.google.firebase.iid.GmsRpc.lambda$extractResponseWhenComplete$0$GmsRpc(GmsRpc.java:91)
       at com.google.firebase.iid.GmsRpc$$Lambda$0.then(GmsRpc.java:6)
       at com.google.android.gms.tasks.zze.run(zze.java:5)
       at com.google.firebase.iid.FirebaseIidExecutors$$Lambda$0.execute(FirebaseIidExecutors.java)
       at com.google.android.gms.tasks.zzc.zza(zzc.java:6)
       at com.google.android.gms.tasks.zzr.zza(zzr.java:19)
       at com.google.android.gms.tasks.zzu.zza(zzu.java:104)
       at com.google.android.gms.tasks.zze.run(zze.java:15)
       at com.google.firebase.iid.FirebaseIidExecutors$$Lambda$0.execute(FirebaseIidExecutors.java)
       at com.google.android.gms.tasks.zzc.zza(zzc.java:6)
       at com.google.android.gms.tasks.zzr.zza(zzr.java:19)
       at com.google.android.gms.tasks.zzu.zza(zzu.java:104)
       at com.google.android.gms.tasks.TaskCompletionSource.setResult(TaskCompletionSource.java:8)
       at com.google.firebase.iid.MessengerIpcClient$Request.finish(MessengerIpcClient.java:20)
       at com.google.firebase.iid.MessengerIpcClient$TwoWayRequest.handleResponseInternal(MessengerIpcClient.java:7)
       at com.google.firebase.iid.MessengerIpcClient$Request.handleResponse(MessengerIpcClient.java:29)
       at com.google.firebase.iid.MessengerIpcClient$Connection.receivedResponse(MessengerIpcClient.java:42)
       at com.google.firebase.iid.MessengerIpcClient$Connection$$Lambda$0.handleMessage(MessengerIpcClient.java:14)
       at android.os.Handler.dispatchMessage(Handler.java:101)
       at com.google.android.gms.internal.firebase-iid.zze.dispatchMessageTraced(zze.java:21)
       at com.google.android.gms.internal.firebase-iid.zze.dispatchMessage(zze.java:11)
       at android.os.Looper.loop(Looper.java:164)
       at android.app.ActivityThread.main(ActivityThread.java:6541)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)

classpath 'com.google.gms:google-services:4.3.3'


implementation 'com.google.firebase:firebase-messaging:20.2.4'

I've got confirmation from user that factory-resetting device (Sony TV) solves this issue

We are also not able to get the Firebase InstanceID for many of our users. One device we can constantly reproduce is (not with us)-

1. Samsung Galaxy J5 (SM-J510FN)

Although, we are getting the following error- MISSING_INSTANCEID_SERVICE

For my case, my getToken code looked something like this

FirebaseMessaging.getInstance().getToken()
    .addOnCompleteListener(new OnCompleteListener<String>() {
        @Override
        public void onComplete(@NonNull Task<String> task) {
          String token = task.getResult(); // This causes the crash if task.isSuccessful() == false

          Toast.makeText(MainActivity.this, msg, Toast.LENGTH_SHORT).show();
        }
    });

I'm no longer seeing crashes after checking if task.isSuccessful() is true before accessing task.getResult().

Re- comment#55 You could also use the addOnSuccessListener / addOnFailureListener methods to handle the cases individually.

Am I coming today is my issue is how can I get started with the website and also make money online so I could make like others and become a great person is helping others how to be this pandemic of coronavirus healthwise and health solutions and strategies are staying healthy and take care of each other and stay away from one another be number we had to do it for the best ways of life

Really like this in quarters give us an envelope in the game of life now is wait is that really what you think about that is what you need to do in besides what you have to do to take care of your health and your ways of eating around and staying away from others because the pandemic the coronavirus is very dangerous andIf you will never have done in really have to do besides you don’t not want to go to these ways of life so you need to stay healthy and stay away from others like in the house with the steps to steps that you could do so you could complete the way of a better way of life and being in the field coronavirus no onions is one of the ones of health solutions and also staying in shape with exercises and also to remember drink as much as vitamins you could ever have never done but this is for the wait will be a better way of life sustaining how do you not eat junk food like you guys do outside I will finish off my phone take me a while to stay healthy also two bricks is another way that you could be the pandemic virus in case you were to be able to get a sickness symptoms so you could step-by-step use or onion systems and use other way of staying healthy remember to drink lots of water and also to take care of yourself and your spouse or you love persons mouth partner take care and God bless no I was time is the work in from home

   HolaHola vida que vivimos estos días debemos de saber que tenemos de portarnos bien con uno sin el otro y tratarlos como respetar uno al otro y también como pensé este mentado coronavirus que está destruyendo vidas quitando vidas y gente muriendo por eso yo digo dios mío ayúdanos echar una mano porque hay mucha gente que no comprende y no puede ni creer que esté hiciste STU mentado coronavirus coronavirus es una enfermedad mortal que por eso digo que eso que pasa con uno sobre el otro como esto coronavirus está muy peligroso por eso debes de cuidar tu salud y cambiar tu modo de comer por fuera y comer mejor haciendo comidas. Pase en su propio hogar para que sepas lo que tienes dentro de tus comidas que vas a disfrutar y también acuérdate que mucha gente no lo hace. Después debes de cambiar porque está muy duro para que nosotros vivimos por esto que pasa solo cuiden zen y a ver qué pasa y el jueves en estas tragedias pueden hacer tu vida mejor si los haces y puedes defender contra el coronavirusLo comprendo gracias y que tenga un buenos días o buenas noches y que descanses y también acuérdese en que comiendo cebollas también comiendo saludable puedes vencer esto coronavirus y también haciendo vitamina a vitamina de vitamina C vitamina de vitamina D del despertador a las vitaminas que fueras para tu salud y gracias otra vez y que dios los bendiga adiós

Registering FCM , FirebaseMessagingService has not get Token

When I actively get the token, hint

Fetch FCM token failed: java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: AUTHENTICATION_FAILED

android u

time : 06-19 11.44