NativeScript / NativeScript/firebase
[@nativescript/firebase-messaging] FIS_AUTH_ERROR on Android
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 62
- Forks
- 53
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 2
Description
Hi, I am trying to use @nativescript/firebase-messaging and I cannot get it working.
"@nativescript/core": "^8.3.5",
"@nativescript/android": "~8.3.1" also not working with "@nativescript/android": "~8.2.0"
Here is my code
// main.ts
firebase().initializeApp()
.then((app: FirebaseApp) => {
console.log("Firebase init done!");
firebase().messaging().showNotificationsWhenInForeground = true;
firebase().crashlytics().setCrashlyticsCollectionEnabled(true);
}).catch((error: Error) => {
console.log("Firebase init failed", error);
});
// firebaseServices.ts
const messaging = firebase().messaging();
messaging.getToken()
.then((token: string) => {
console.log("Token", token);
}).catch((e: Error) => {
console.log("Token error: ", e);
});
So, when I try to get the PN token, I got this error.
Error: java.util.concurrent.ExecutionException: java.io.IOException: FIS_AUTH_ERROR
I have tried re-install packages & re-download google-services.json etc. Still have the same here.
Please any help?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the FIS_AUTH_ERROR using the versions and calls shown in main.ts and firebaseServices.ts, then inspect the Firebase Android configuration, including google-services.json. Done means identifying the configuration or integration cause and confirming that messaging().getToken() returns a token without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100