[🐛] Bug Report Title - [auth/internal-error] An internal error has occurred, please try again. for Cambodia Users

[lunatictiol]

Issue

I am experiencing an issue with React Native Firebase's phone number verification. When users from Cambodia attempt to sign up using phone number verification, they encounter the error:
[auth/internal-error] An internal error has occurred, please try again.

This occurs specifically when the user submits their phone number and waits for the OTP, but the OTP never arrives, and the error is shown instead.

Project Files

Javascript

Click To Expand

package.json:

"react-native-firebase/analytics": "^18.1.0",
"react-native-firebase/app": "^18.1.0",
"react-native-firebase/auth": "^18.1.0",
"react-native-firebase/crashlytics": "^18.1.0",
"react-native-firebase/messaging": "^18.1.0",

# N/A

firebase.json for react-native-firebase v6:

# N/A

iOS

Click To Expand

ios/Podfile:

• I'm not using Pods
• 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?
• [x ] I am using android/gradle.settings jetifier=true for Android compatibility?
• [ x] 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 15.2
  CPU: (8) arm64 Apple M1
  Memory: 108.73 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.12.0
    path: /opt/homebrew/opt/node@22/bin/node
  Yarn: Not Found
  npm:
    version: 10.9.1
    path: ~/Desktop/myclnq/myclnq-requester/node_modules/.bin/npm
  Watchman:
    version: 2024.12.02.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.2
      - iOS 18.2
      - macOS 15.2
      - tvOS 18.2
      - visionOS 2.2
      - watchOS 11.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12700392
  Xcode:
    version: 16.2/16C5032a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.13
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.5
    wanted: 0.74.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

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

---

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

[mikehardy]

"react-native-firebase/analytics": "^18.1.0",
"react-native-firebase/app": "^18.1.0",
"react-native-firebase/auth": "^18.1.0",
"react-native-firebase/crashlytics": "^18.1.0",
"react-native-firebase/messaging": "^18.1.0",

Please don't ask for support on outdated versions - it is the equivalent of saying "hey, you all may have fixed all the issues I'm seeing but I'd like to ask for your time anyway instead of using all of our time efficiently by making sure the issues aren't already fixed"

Beyond that, when you see "internal error" it really helps to specify the device information requesting it (you haven't even mentioned if it is iOS or android?) and to get the device logs.

I suggest you should use a VPN that has a terminator in Cambodia so that you can use your own devices to reproduce the problem, and get either the Xcode logs by launching it on device but from Xcode, or adb logcat if it was android

After you update to current versions