Phone auth on android - error when confirming code 'auth/session-expired'

[omgo]

Issue

Hello, I'm using phone auth, and it works on ios, but dont on android. After confirming code I get the error auth/session-expired - ofc I understand that is it mean, but I don't understand why, and how to fix it. Could you help me?

sendCode() {
  firebase.auth().signInWithPhoneNumber(this.store.phoneNumber)
    .then(confirmResult => {
      this.store.setConfirmResult(confirmResult)
    }).catch(error => {
      console.log(error)
    })
}

authorize() {
  this.store.confirmResult.confirm(this.store.code)
    .then(user => {
      console.log(user)
    })
    .catch(error => {
      console.log(error)
    })
}

Environment

1. Application Target Platform: Android

2. Development Operating System: macOS Sierra

3. Build Tools: Android Studio 2.3.3, Android SDK 26.1.1

4. React Native version: 0.49.3

5. RNFirebase Version: 3.0.3

6. Firebase Module: auth (phone)

[omgo]

Does anyone have the same problem? Or decision?

[chrisbianca]

@omgo Sorry for the lack of response, this one slipped through.

I've been doing lots of testing with signInWithPhoneNumber recently and haven't come across this issue so I'm not really sure what to suggest.

The only thing I can think is that there's too long a time happening between the initial request and confirming the code?

Just to confirm, are you handling the autoverified case in Android using the onAuthStateChanged listener?

[omgo]

@chrisbianca thank you for your answer.
Yes, I'm using onAuthStateChanged, and you know, actually phone auth sometimes is working, it really didn't work a few days ago (after getting code we were sending it in next 10 seconds - and 'session expired') but now it's working almost every time (sometimes still 'session expired'), it's like a magic)) I can't understand. Looks like issue can be closed

[chrisbianca]

@omgo Sounds like it might be an internal Firebase issue then. I'm going to close, but please re-open if you keep running into problems.

[sfratini]

@omgo I am having the same issue. In your case was consistent for a period of time and then it worked? Or just random? I'll try tomorrow but I wanted to be sure what is going on. Thanks!

Another weird thing. I just enabled the onAuthStateChanged and I do get a user every time I restart the app, like somehow I already got the user entity, however every time I want to verify the number, I get the SESSION_EXPIRED error.

@chrisbianca I just enabled the automatic verification and it works every single time. I do signout and as soon as the SMS gets into the phone, I receive the user and all the data.

However if I try to make it manually, I get the SESSION_EXPIRED. Could it be an issue with Android 7? I am using a Samsung S8. Maybe in the way the token is being sent when doing manually.

[rajeshzmoke]

facing the same issue as @sfratini
React native 0.51.0
React native Firebase
Android 7.1.1

And i would like to add another point that the above mentioned issue happens only on a MI device

[dmacan23]

Is there any update on this issue? I am still receiving it.
Oneplus 5,
Android 8.0.0,
RN 0.53,
RN Firebase 3.2.7,
Firebase 11.6.0

[rajeshzmoke]

If u have an onauthstatechanged() listener and also if you're trying to manually verify the phone number , you will get session expired everytime on Android ...

Reason :

• onauthstatechanged () will verify as soon as u get sms (automatically) ..so if you're trying to verify manually using the same sms it won't work.

Hope this helps.

[adirzoari]

@omgo I'm facing the same issue. did you find solution?

[numandev1]

i am also facing same issue on android 7.0 only