You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using verifyPhoneNumber and signInWithVerificationId (Sms flow) for authenticating our users, but if the user then signs out, verifyPhoneNumber no longer works as expected.
We had debugged with our team using adb logcat, and a custom logger to trace what the cellphone is doing, and then when we called the signout and then the verifyPhoneNumber function again throws this
05-04 18:55:23.983 15867 16449 D FirebaseAuth: Notifying id token listeners about a sign-out event.
05-04 18:55:23.983 15867 16449 D FirebaseAuth: Notifying auth state listeners about a sign-out event.
05-04 18:55:24.497 15867 16449 W BiChannelGoogleApi: [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzak@62af8a3
05-04 18:55:24.526 15867 15867 W BiChannelGoogleApi: [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzak@62af8a3
05-04 18:55:25.617 15867 16163 D FirebaseAuth: Notifying id token listeners about user ( A_FIREBASE_UUID ).
05-04 18:55:25.617 15867 16163 D FirebaseAuth: Notifying auth state listeners about user ( A_FIREBASE_UUID ).
This kind of showed us that the uuid still stored on disk. What's even weirder, is that, when we call getIdToken it gives us a non expired idToken, this makes us think that maybe the sign out function is not working as expected (The expectation is that the complete data of the user is erased at least in the context of the application).
Is this the correct behavior?
What can we do for this to really clean the user's data?
Thanks.
The text was updated successfully, but these errors were encountered:
We're using
verifyPhoneNumber
andsignInWithVerificationId
(Sms flow) for authenticating our users, but if the user then signs out,verifyPhoneNumber
no longer works as expected.We had debugged with our team using
adb logcat
, and a custom logger to trace what the cellphone is doing, and then when we called thesignout
and then theverifyPhoneNumber
function again throws thisThis kind of showed us that the
uuid
still stored on disk. What's even weirder, is that, when we callgetIdToken
it gives us a non expired idToken, this makes us think that maybe the sign out function is not working as expected (The expectation is that the complete data of the user is erased at least in the context of the application).Is this the correct behavior?
What can we do for this to really clean the user's data?
Thanks.
The text was updated successfully, but these errors were encountered: