[firebase_auth]: An internal error has occurred. [ Error code:39 ]

[Arhidev]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

App Check, Auth

Which platforms are affected?

Android, iOS

Description

Hello Firebase team,

I’m encountering a critical issue using Firebase Phone Authentication in Côte d’Ivoire (Ivory Coast) In Flutter App.

While phone numbers from MTN CI are able to receive OTP messages correctly, users with phone numbers from Orange CI and Moov Africa CI are not receiving any OTP SMS. This prevents a large portion of users from signing in via phone number.

🔍 Observations:
OTP works only with MTN phone numbers.

For Orange and Moov, the following error is thrown:

E/FirebaseAuth(11511): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Error code:39
I/flutter (11511): verificationFailed() -> error: An internal error has occurred. [ Error code:39 ]

SMS simply never arrives to the Orange or Moov users, even though the verification process is triggered.

✅ E.164 Format Example:
✅ +2250595025164 (MTN — works)

❌ +2250749435429 (Orange — not working)

❌ +2250153441343 (Moov — not working)

This affects over 60% of mobile users in Côte d’Ivoire and renders Firebase Auth unusable for most local customers.

Reproducing the issue

E/FirebaseAuth(11511): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Error code:39
I/flutter (11511): verificationFailed() -> error: An internal error has occurred. [ Error code:39 ]

Firebase Core version

3.13.0

Flutter Version

3.29.2

Relevant Log Output

Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments

No response

[sayan-avantai]

android 10,11,12 and latest 16 are getting the otp, only 13,14,15 has play integrity issue. We are also facing this thing.

[Arhidev]

android 10,11,12 and latest 16 are getting the otp, only 13,14,15 has play integrity issue. We are also facing this thing.

@sayan-avantai really, ok I understand, I hope this problem will be solved

[SelaseKay]

Hi @Arhidev, thanks for the report. This seems to be related to #13103. Unfortunately, it appears to be an upstream issue and goes beyond the scope of FlutterFire. I recommend you contact Firebase Support for further assistance.