[🐛] Android 13 SMS Code Has Expired, for every 13 device after release not able to verify

[ReactNativeDev2296]

Hello @mikehardy, @andymatuschak , @gilbertl @dlackty @felixclack
I am unable to log into any Android 13 device, please provide a solution

**Library version:

@react-native-firebase/analytics": "18.3.1",
    "@react-native-firebase/app": "18.3.1",
    "@react-native-firebase/auth": "18.3.1",
    "@react-native-firebase/messaging": "18.3.1",
    react-native: "0.61.3"`

**Build.gradle file(Android):

        minSdkVersion = 21
        compileSdkVersion = 33
        targetSdkVersion = 33
        supportLibVersion = "30.0.0"
        multiDexEnabled = true
        androidXCore = "1.7.0"`

***Build.gradle(android/app):

    implementation platform('com.google.firebase:firebase-bom:32.2.0')
    implementation 'com.google.firebase:firebase-auth'`

[ReactNativeDev2296]

Hi @mikehardy , @andymatuschak , @felixclack , @dlackty , @gilbertl
Please help us with the issue

[ReactNativeDev2296]

Hi @mikehardy , @andymatuschak , @felixclack , @dlackty , @gilbertl

any update for the above bug?

[mikehardy]

implementation platform('com.google.firebase:firebase-bom:32.2.0')

You are overriding the firebase BoM, that's for advanced use cases and you assume the risk of breakage. It may be the cause of this. Have you tried removing it, updating to react-native-firebase current and letting it handle the BoM resolution as it will do for you here:

react-native-firebase/packages/app/package.json

Line 84 in c9b695a

"firebase": "32.3.1",

Also, I do not believe this is necessary, the auth package will bring it in for you, so this should be removed from your gradle files along with the BoM entry

implementation 'com.google.firebase:firebase-auth'`

It does not appear that there were auth-related issues, however, you never know, and first job of reproduction is to make sure you're not just discovering old bugs, so you want to get on current software

That said, I do not see any issues in the upstream firebase-android-sdk repo about this, and the last time I saw this it was more related to using the wrong SMS code - usually a subtle issue where somehow multiple SMS codes may be requested, then there is a race condition, and the wrong one is used. Perhaps that is it, or similar to it?

No one else is reporting this and Android 13 has been out for a while though, so even though I don't have concrete evidence of it I would strongly suspect this is a project-specific issue

[ReactNativeDev2296]

Hi @mikehardy , @andymatuschak @felixclack @dlackty
I removed what you suggested but some Android 13 is working fine but Samsung a34 OS version 13 still shows invalid OTP and one more think when we are using old mobile number which are already available into fires store is was working fine but newly mobile number is not working it was throwing errors

[ReactNativeDev2296]

Hello @mikehardy ,

Today we are trying to deliver this project to the client but this issue is happening again can you give us an emergence solution?

[ReactNativeDev2296]

Hello @mikehardy @andymatuschak @felixclack @dlackty ,

I found the root cause of the issue:- The issue is with Android 13. When we try to set up accounts using a SIM card and create new accounts, the device generates an invalid OTP error. It will function well if we try to use a different cellphone number.

  package="com.SEWAMOApp">

  <!--  Keep only the permissions used in your app  -->

  <uses-feature
      android:name="android.hardware.telephony"
      android:required="true" />
    <uses-feature
        android:name="android.hardware.camera"
        android:required="true" />

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
     <uses-permission android:name="android.permission.CAMERA" />
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.READ_MEDIA_IMAGES"/>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />


    
    <application
      android:name=".MainApplication"
      android:label="@string/app_name"
      android:icon="@mipmap/ic_launcher"
      android:allowBackup="false"
      android:theme="@style/AppTheme"
      android:largeHeap="true"
        android:usesCleartextTraffic="true">
      
      <!-- Add license key in meta-data tag here. This should be inside the application tag. -->

      <activity
        android:name=".MainActivity"
        android:exported = "true"
        android:label="@string/app_name"
        android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
        android:windowSoftInputMode="adjustPan"
        >
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
      </activity>
      <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
      <meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_id"/>
    
    <!-- You will only need to add this meta-data tag, but make sure it's a child of application -->
   <meta-data
     android:name="com.google.android.geo.API_KEY"
     android:value="@string/google_maps_key"/>
  
   <!-- You will also only need to add this uses-libray tag -->
   <uses-library android:name="org.apache.http.legacy" android:required="false"/>

    </application>
    <queries>
      <intent>
        <action android:name="android.intent.action.VIEW" />
        <data android:mimeType="*/*" />
      </intent>
    </queries>

</manifest>

[ReactNativeDev2296]

Hello @mikehardy , @andymatuschak @felixclack @dlackty ,
Please read the below logs also from the firebase console side

  "insertId": "-t4elkdc8ig",
  "jsonPayload": {
    "methodName": "google.cloud.identitytoolkit.v1.AuthenticationService.SignInWithPhoneNumber",
    "status": {
      "message": "SESSION_EXPIRED",
      "code": 3
    },
    "requestMetadata": {
      "callerIp": "103.167.52.19",
      "callerSuppliedUserAgent": "Dalvik/2.1.0 (Linux; U; Android 13; M2012K11AI Build/TKQ1.220829.002),gzip(gfe),gzip(gfe)"
    },
    "@type": "type.googleapis.com/google.cloud.identitytoolkit.logging.RequestLog"
  },
  "resource": {
    "type": "identitytoolkit_project",
    "labels": {
      "project_id": "sewamo-ec72e"
    }
  },
  "timestamp": "2023-10-12T04:13:00.101Z",
  "severity": "ERROR",
  "logName": "projects/sewamo-ec72e/logs/identitytoolkit.googleapis.com%2Frequests",
  "receiveTimestamp": "2023-10-12T04:13:00.875676805Z"
}

[ReactNativeDev2296]

Hello @mikehardy @andymatuschak @felixclack @dlackty ,

Today we are trying to deliver this project to the client but this issue is happening again can you give us an emergency solution?

[ReactNativeDev2296]

Hello @mikehardy ,
Please provide me with an update, because firebase-support@google.com said that this is not our side issue it is library side issue

[ReactNativeDev2296]

Hi @andymatuschak,
Please help us with what we can do because all android 13 users are not able to login

[ReactNativeDev2296]

Hello @mikehardy @felixclack @dlackty @gilbertl ,

At Least provide a solution

[ozgencozben]

Hi, this is very critical issue, we are about to deliver our project to client but we find out that some users cannot join into our application. @mikehardy & @andymatuschak we need your help here. Please give us some help or any other suggestion ! Thanks CC : @KuldipReactNative