Only Telenor network operator Number is getting error 39 on requesting otp #2141

mohsiniqbalcui · 2023-10-10T08:03:17Z

Welcome to FirebaseUI and thanks for submitting an issue!

Please take a look at open issues, as well as resolved issues, to see if your issue is either already being addressed, or has been solved by someone else.

If not, please feel free to fill in the following info so we can help faster!

Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository file a GitHub issue.
For general technical questions, post a question on StackOverflow tagged appropriately.
For general Firebase discussion, use the firebase-talk google group
For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel

Step 2: Describe your environment

Only Telenor network operator Number is giving error 39 in pakistan all other network are working fine and receving otp.

Android device: Emulator and Physical
Android OS version: 5.0 and above
Google Play Services version: 23.37.17
Firebase/Play Services SDK version: 20.4.0
FirebaseUI version: 21.1.0

Step 3: Describe the problem:

Steps to reproduce:

Download this app https://play.google.com/store/apps/details?id=com.app.bikjaa
In Welcom screen press button "login with phone"
Enter any Telenor number staring from (034..........) with selecting pakistan as country code +92
[0340 7795694] [0343 7340100] [0347 1447099] [0342 4215519] with selecting pakistan as country code +92
error code 39 come
Run the app in both emulator or physical device

Observed Results:

What happened? This could be a description, logcat output, etc.
In mobile error 39 comes

[SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Error code:39
AuthUI E A sign-in error occurred.
com.google.firebase.FirebaseException: An internal error has occurred. [ Error code:39 ]
at com.google.android.gms.internal.firebase-auth-api.zzxc.zza(com.google.firebase:firebase-auth@@21.1.0:6)
at com.google.android.gms.internal.firebase-auth-api.zzxw.zza(com.google.firebase:firebase-auth@@21.1.0:1)
at com.google.android.gms.internal.firebase-auth-api.zzxx.run(com.google.firebase:firebase-auth@@21.1.0:3)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:233)
at android.os.Looper.loop(Looper.java:334)
at android.app.ActivityThread.main(ActivityThread.java:8399)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)

Expected Results:

otp should be sent to user

Relevant Code:

// code here to reproduce the problem

/**
 * Funtions for login using Mobile OTP
 */
//
private fun verifyMobileNumber() {
    // Choose authentication providers
    val providers = mutableListOf(
            PhoneBuilder().setDefaultCountryIso("PK").build()
    )
    // Create and launch sign-in intent
    startActivityForResult(
            AuthUI.getInstance()
                    .createSignInIntentBuilder()
                    .setAvailableProviders(providers)
                    .setTosAndPrivacyPolicyUrls("https://bikjaa.pk/pages/terms-of-use",
                            "https://bikjaa.pk/pages/privacy-policy")
                    .setAlwaysShowSignInMethodScreen(true)
                    .setTheme(R.style.OTPTheme)
                    .build(),
            APP_REQUEST_CODE
    )
}

my build.gradle file is
implementation 'com.google.android.gms:play-services-location:17.0.0'
implementation 'com.google.android.gms:play-services-maps:17.0.0'
implementation 'com.google.android.gms:play-services-wallet:19.1.0'
implementation 'com.google.android.libraries.places:places:3.0.0'
implementation 'com.google.android.gms:play-services-auth:20.4.0'
implementation 'com.google.firebase:firebase-messaging:23.1.1'
implementation 'com.google.firebase:firebase-core:21.1.1'
implementation ('com.google.firebase:firebase-auth:21.1.0') {
exclude module: "play-services-safetynet"
}
implementation 'com.firebaseui:firebase-ui-auth:7.0.0'

The text was updated successfully, but these errors were encountered:

thatfiredev · 2023-10-10T09:52:21Z

Hey @mohsiniqbalcui

Code 39 indicates that you have tried too many times, as explained here. Can you please wait a few minutes for it to cool down and try again?

If the problem persists or if you think this is only related to that network operator, please contact Firebase support, as that issue doesn't seem to be related to FirebaseUI-Android directly. You can reference this github issue when you fill the support form to help them understand the problem.

ba138 · 2023-10-24T09:47:06Z

"I have encountered this issue multiple times, and despite several attempts, it has not been resolved. Interestingly, the application functions properly when using a different network, such as Zong, but the problem persists when using the Telenor network

thatfiredev · 2023-10-24T14:32:14Z

@ba138 Please contact Firebase support they should be able to address the issue.

codenaveed · 2024-01-10T14:41:58Z

Hi Dears, have you found the solution for this issue? I am facing same issue with ONLY Telenor numbers.

MufakirMairaj · 2024-01-16T05:28:33Z

I am facing the issue from last 6 months both Ufone and Telenor phone numbers.

Ashad-sadiq · 2024-02-21T05:11:43Z

Is there a solution for this? Our application is stuck in production and there is no way for our users to login!
Ive tried loging from different operators:
OTP is not being received on: Ufone, Telenor.
OTP is being received on: Jazz, Zong, Warid.
as of 21st Feb 2024

Who should i contact to get this issue resolved ASAP?

Waleed065 · 2024-02-29T18:03:39Z

I am facing the issue from last 6 months both Ufone and Telenor phone numbers.

Same, Facing issue for both telenor and ufone numbers in Pakistan

Waleed065 · 2024-02-29T18:06:48Z

Is there a solution for this? Our application is stuck in production and there is no way for our users to login! Ive tried loging from different operators: OTP is not being received on: Ufone, Telenor. OTP is being received on: Jazz, Zong, Warid. as of 21st Feb 2024

Who should i contact to get this issue resolved ASAP?

Contact firebase support from the firebase account that has the issue

MufakirMairaj · 2024-03-01T15:56:40Z

Is there a solution for this? Our application is stuck in production and there is no way for our users to login! Ive tried loging from different operators: OTP is not being received on: Ufone, Telenor. OTP is being received on: Jazz, Zong, Warid. as of 21st Feb 2024
Who should i contact to get this issue resolved ASAP?

Contact firebase support from the firebase account that has the issue

I had a long conversation with firebase team they asked me logs, carrier, time and phone numbers. I shared the recorded video as well. There answer was. Here it is "Thank you for the information. I have discussed the matter with our engineering team, and they have confirmed that Telenor carrier is currently unavailable for SMS due to service reliability issues. I understand that this is an important feature for your application, however we are unable to unblock this from our side. "

SheikhSaad · 2024-03-15T15:15:25Z

Do we have any further update on this, I've been facing this issue and right now I've changed the OTP verification method.

stMerlHin · 2024-07-17T22:51:02Z

I am facing the same issue from Togo carriers are MOOV and TOGOCEL.

Musanakh · 2024-09-17T09:15:56Z

I'm encountering the same issue on the Ufone and Telenor networks. @MufakirMairaj and @mohsiniqbalcui have you managed to find a solution by any chance?

Is there a solution for this? Our application is stuck in production and there is no way for our users to login! Ive tried loging from different operators: OTP is not being received on: Ufone, Telenor. OTP is being received on: Jazz, Zong, Warid. as of 21st Feb 2024
Who should i contact to get this issue resolved ASAP?

Contact firebase support from the firebase account that has the issue

I had a long conversation with firebase team they asked me logs, carrier, time and phone numbers. I shared the recorded video as well. There answer was. Here it is "Thank you for the information. I have discussed the matter with our engineering team, and they have confirmed that Telenor carrier is currently unavailable for SMS due to service reliability issues. I understand that this is an important feature for your application, however we are unable to unblock this from our side. "

MufakirMairajAlam · 2024-09-17T10:20:07Z

No I did not find the solution, Therefore I replaced the authentication flow.

Musanakh · 2024-09-17T10:50:57Z

No I did not find the solution, Therefore I replaced the authentication flow.

Can you please guide, which platform are you using for phone number authentication?

MufakirMairajAlam · 2024-09-17T10:53:07Z

You can use email authentication or use Twilio.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Only Telenor network operator Number is getting error 39 on requesting otp #2141

Only Telenor network operator Number is getting error 39 on requesting otp #2141

mohsiniqbalcui commented Oct 10, 2023 •

edited

Loading

thatfiredev commented Oct 10, 2023 •

edited

Loading

ba138 commented Oct 24, 2023

thatfiredev commented Oct 24, 2023

codenaveed commented Jan 10, 2024

MufakirMairaj commented Jan 16, 2024

Ashad-sadiq commented Feb 21, 2024

Waleed065 commented Feb 29, 2024

Waleed065 commented Feb 29, 2024

MufakirMairaj commented Mar 1, 2024 •

edited

Loading

SheikhSaad commented Mar 15, 2024

stMerlHin commented Jul 17, 2024 •

edited

Loading

Musanakh commented Sep 17, 2024

MufakirMairajAlam commented Sep 17, 2024

Musanakh commented Sep 17, 2024

MufakirMairajAlam commented Sep 17, 2024

Only Telenor network operator Number is getting error 39 on requesting otp #2141

Only Telenor network operator Number is getting error 39 on requesting otp #2141

Comments

mohsiniqbalcui commented Oct 10, 2023 • edited Loading

Step 1: Are you in the right place?

Step 2: Describe your environment

Step 3: Describe the problem:

Steps to reproduce:

Observed Results:

Expected Results:

Relevant Code:

thatfiredev commented Oct 10, 2023 • edited Loading

ba138 commented Oct 24, 2023

thatfiredev commented Oct 24, 2023

codenaveed commented Jan 10, 2024

MufakirMairaj commented Jan 16, 2024

Ashad-sadiq commented Feb 21, 2024

Waleed065 commented Feb 29, 2024

Waleed065 commented Feb 29, 2024

MufakirMairaj commented Mar 1, 2024 • edited Loading

SheikhSaad commented Mar 15, 2024

stMerlHin commented Jul 17, 2024 • edited Loading

Musanakh commented Sep 17, 2024

MufakirMairajAlam commented Sep 17, 2024

Musanakh commented Sep 17, 2024

MufakirMairajAlam commented Sep 17, 2024

mohsiniqbalcui commented Oct 10, 2023 •

edited

Loading

thatfiredev commented Oct 10, 2023 •

edited

Loading

MufakirMairaj commented Mar 1, 2024 •

edited

Loading

stMerlHin commented Jul 17, 2024 •

edited

Loading