firebase / firebase/firebase-android-sdk
FirebaseAuth crash on captcha link when no browser is installed
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 710
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 34
Description
Hi, we're using Firebase Auth's phone number method for users to signin. We've seen crashes when user doesn't have a browser installed & firebase tries opens captcha link. Crash is always a bad experience for users & since I believe there's nothing we can do here, maybe it would be nice to have exception thrown instead of causing a crash.
#### Steps to reproduce:
- Browser app doesn't exist
#### Observed Results:
* Application crashes with:
```shell
No Activity found to handle Intent { act=android.intent.action.VIEW }
android.app.Instrumentation.checkStartActivityResult (Instrumentation.java:1809)
com.google.firebase.auth.internal.RecaptchaActivity.zzf (com.google.firebase:firebase-auth@@21.0.1:12)
com.google.android.gms.internal.firebase-auth-api.zztr.zza (com.google.firebase:firebase-auth@@21.0.1:7)
com.google.android.gms.internal.firebase-auth-api.zztr.onPostExecute (com.google.firebase:firebase-auth@@21.0.1:2)
```
#### Expected Results:
* Exception thrown for captcha handling
Contributor guide
Research direction
Start by reproducing the Firebase Auth phone-number flow on an Android device without a browser installed. Trace the failure reported in com.google.firebase.auth.internal.RecaptchaActivity.zzf and determine how the missing browser case is surfaced. Done means the captcha-link path no longer causes an unhandled crash and reports the failure through the expected exception behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, java
- Domain
- authentication, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100