Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIS_AUTH_ERROR #284

Open
ppetree opened this issue Aug 29, 2024 · 4 comments
Open

FIS_AUTH_ERROR #284

ppetree opened this issue Aug 29, 2024 · 4 comments

Comments

@ppetree
Copy link

ppetree commented Aug 29, 2024

Bug Report

Error requesting a token on Android devices (Apple works fine)

Admittedly this could be an FCM issue but some sources online say that going to firebase 20.0.1 solves this problem.

Expected Behaviour

Get a token back as I always have.

Actual Behaviour

on register I get an error stating
java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR

Reproduce Scenario (including but not limited to)

Registering a device for push notifications using

Steps to Reproduce

Platform and Version (eg. Android 5.0 or iOS 9.2.1)

Android 13, Android 14

(Android) Device Vendor (e.g. Samsung, HTC, Sony...)

Pixel, Teclast (tablet), Samsung and Blu

Sample Push Data Payload

Can't push without a token

Sample Code that illustrates the problem

java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR

Logs taken while reproducing problem

java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR

All online resources point to an FIS authorization problem but I have granted that permission (repeatedly), updated my sha1/256 fingerprints and done everything else and then checked it all thrice. I still get the error. One post suggests going back to firebase sdk 20.0.1 to solve the problem.

BTW, I'm updating 3 projects that I've not touched in over a year (cancer). I'm trying to get back at it but my update plans are sticking on this error.

@ksch10bob
Copy link

@ppetree did you solve your problem?
If yes, what did you do?
If no, did you build a minimal reproduction scenario to narrow down the root cause?

@ppetree
Copy link
Author

ppetree commented Oct 4, 2024

@ppetree did you solve your problem? If yes, what did you do? If no, did you build a minimal reproduction scenario to narrow down the root cause?
No I did not find a solution. I've googled my brains out and nothing seems to work.

@ksch10bob
Copy link

@ppetree
i would suggest the following:
Update your cordova tooling to the latest Versions

  • create a sample cordova app via cordova cli
  • add the push plugin in the latest published version
  • add some logic for push registration in the deviceready event handler
  • add cordova-android platform veersion 13.0.0
  • add your google-service.json to the app
  • build the app and test the registration logic

If this works you can be sure your google-service.json is generated properly and the root cause is another one.

@ppetree
Copy link
Author

ppetree commented Oct 16, 2024

@ksch10bob None of that is the problem and, in fact, downloading a new google-service.json was the problem.

The new google-services.json has the wrong Web API Key. Get the correct key off the General Project Settings tab and MANUALLY update your google-services.json.

There should be better error handling around this than what's provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants