Cannot create PhoneAuthCredential without either verificationProof, sessionInfo, ortemprary proof.

[baole]

Step 1: Are you in the right place?

We received a lot of crash report on the latest version 4.1.0 regarding to phone verification. The detail report are here http://crashes.to/s/77f7c50782c

The same users used our old version which is built with version 4.0.1 worked fine.

Step 2: Describe your environment

• Firebase/Play Services SDK version: 16.0.2
• FirebaseUI version: 4.1.0

Step 3: Describe the problem:

App crashes during using phone number login using Firebase Auth

Observed Results:

Expected Results:

Phone login works

Relevant Code:

We use https://firebase.google.com/docs/auth/android/firebaseui

[samtstern]

@baole thanks for the comment! Just adding some info here for my own reference:

[SUPERCILEX]

Oh, I got it. 🤦‍♂️ Users will switch to their messaging app and don't have a lot of RAM available so it kills your app. Since we only store the verification ID in memory, it gets lost. Side note: the number of times we've added bugs like this, you'd think we would learn. Nope. 😂😉

@samtstern I'll submit a PR tomorrow. 👍

@samtstern PS: Personal life has been super busy, hoping to become more active again in a month or so. 😊

[baole]

@samtstern @SUPERCILEX the issue can be reproduced by enable the "Don't keep activities" option in Developer options on your test device.

[bulej93]

am having this problem too

[samtstern]

@SUPERCILEX thanks for jumping on this! If we didn't have bugs like this, what would Android development be anyway?

[SUPERCILEX]

If we didn't have bugs like this, what would Android development be anyway?

🤣 So true

Anyway, submitted #1393

[baole]

Great. Thanks @SUPERCILEX for the fix.

@samtstern, do you have any plan for 4.2.0 release?

[samtstern]

@baole no set plan right now, you can follow along on the milestone to see as things get cleared.