React-native-firebase: 🔥 auth/unknown an internal error has occurred on android

[eambutu]

Issue

When trying to login with email/password, I get an error on my Android Version 9.0 phone (Pixel 2):

WARN  Possible Unhandled Promise Rejection (id: 0):
Error: [auth/unknown] An internal error has occurred. [ 7: ]
NativeFirebaseError: [auth/unknown] An internal error has occurred. [ 7: ]

There is very little code here, it's merely:

import auth from '@react-native-firebase/auth';
...
auth().signInWithEmailAndPassword(email, password);

When I run this exact code on my Android Version 7.0 phone (Samsung Galaxy Note 5), it works just fine.

---

Project Files

iOS

Click To Expand

#### `ios/Podfile`: - [ ] I'm not using Pods - [x] I'm using Pods and my Podfile looks like:

# N/A

#### `AppDelegate.m`:

// N/A

---

Android

Click To Expand

#### Have you converted to AndroidX? - [ ] my application is an AndroidX application? - [ ] I am using `android/gradle.settings` `jetifier=true` for Android compatibility? - [ ] I am using the NPM package `jetifier` for react-native compatibility? #### `android/build.gradle`:

// N/A

#### `android/app/build.gradle`:

// N/A

#### `android/settings.gradle`:

// N/A

#### `MainApplication.java`:

// N/A

#### `AndroidManifest.xml`:

<!-- N/A -->

---

Environment

Click To Expand

**`react-native info` output:**

System:
    OS: macOS Mojave 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Memory: 223.98 MB / 8.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.1.0 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 24, 27, 28
      Build Tools: 27.0.3, 28.0.2, 28.0.3
      System Images: android-27 | Intel x86 Atom_64, android-27 | Google Play Intel x86 Atom, android-28 | China version of Wear OS Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.6156.11.34.5522156
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.2 => 0.61.2
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-fbsdk: 0.8.0

- **Platform that you're experiencing the issue on**: - [ ] iOS - [ ] Android - [ ] **iOS** but have not tested behavior on Android - [x ] **Android** but have not tested behavior on iOS - [ ] Both - **`react-native-firebase` version you're using that has this issue:** - 6.0.1 for /app and /auth - **`Firebase` module(s) you're using that has the issue:** - auth - **Are you using `TypeScript`?** - N

---

Think react-native-firebase is great? Please consider supporting all of the project maintainers and contributors by donating via our Open Collective where all contributors can submit expenses. [Learn More]

• 👉 Check out React Native Firebase and Invertase on Twitter for updates on the library.

[developerashish01]

any clue on this? I am stuck

[rafalzawadzki]

I'm having a similar issue with phone authentication, on firebase.auth().signInWithPhoneNumber(phoneNumber) call.

Affects users on:
Android 7, 9
Devices HTC U11 EYEs, Galaxy S8+

[Rushabhshroff]

Did anyone find the fix?

[tarunjuneja]

Guys i was getting this because i was on Airplane mode
Ensure you are on a valid n/w
the moment i enabled that it started working

[stale[bot]]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

[switch13]

Still having the same issue.

[tarunjuneja]

Still having the same issue.

Have you already tired adding a pre-validated mobile number on firebase portal

Moreover you will need to build your application with valid deployment key certificate in release mode (which you can generate it on your machine and add it to your app on firebase on firebase portal)

Until i built using release mode with valid certificate i was not able to test it.

[afx31]

My app which I started building last year worked fine with the auth, now coming back it it I'm getting the API key not valid message as well.. Was there any solution for this in the end?

Following error when using '.createUserWithEmailAndPassword' method

[Error: [auth/unknown] An internal error has occurred. [ API key not valid. Please pass a valid API key. ]]

[mikehardy]

@afx31 install fresh google descriptors (GoogleService-Info.plist google-services.json)

[afx31]

@mikehardy I have already re-installed fresh google-services.json files which didn't do anything.

[stale[bot]]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

[theronic]

Make sure to enable the sign-in method you are using via the Firebase console. It's a non-descriptive error.

[stale[bot]]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

[bimix]

Still having this issue when calling a function in the cloud while authenticated with email and password

[stale[bot]]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

[stale[bot]]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

[mrlego]

i am having the same problem please help

[tarunjuneja]

i am having the same problem please help

1 add a pre-validated mobile number on firebase portal

2 generate new deployment key certificate in release mode on your machine

3 add this certificate it to your app on firebase on firebase portal

4 build in release mode

5 run your app.

that worked for me.

I was never able to test in debug mode with development certificate.

[stale[bot]]

Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?

This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.

[stale[bot]]

Closing this issue after a prolonged period of inactivity. If this is still present in the latest release, please feel free to create a new issue with up-to-date information.

[lyseiha]

any update on it?

[mikehardy]

@lyseiha why would there be an update on a closed issue? It's open source --> all updates are visible. And all comments generate notifications.

[Anadi9]

I'm having a similar issue with phone authentication, on firebase.auth().signInWithPhoneNumber(phoneNumber) call.

Affects users on:
Android 7, 9
Devices HTC U11 EYEs, Galaxy S8+

have you found any fix for it? i am facing same issue