Environment
- FirebaseUI version:
com.firebaseui:firebase-ui-auth:10.0.0-beta03 (Compose FirebaseAuthScreen)
- Device: OnePlus 10 Pro (NE2213), Android 16 (API 36)
- Google Play services: 26.26.34
Steps to reproduce
- Configure
FirebaseAuthScreen with an Email provider (plus others).
- Sign in with email once, then sign out and return to the auth screen.
- The method picker now shows a prominent "Continue with email" button with the
previously used address as subtitle (from SignInPreferenceManager).
- Tap it.
Observed
The email entry screen opens completely blank — identical to tapping the regular
"Sign in with email" button below the divider. The saved identifier shown on the
button is not used anywhere in the flow.
Expected
A "Continue as " affordance implies the identifier is carried into the flow:
either skip straight to the password step for that address, or at minimum pre-fill the
email field. Otherwise the button is a duplicate of the provider button and confuses
users (two buttons, same destination).
Analysis
In AuthMethodPicker.kt, ContinueAsButton's click handler is just
onProviderSelected(lastProvider) — the same callback and provider object as the plain
provider button. The preference.identifier is passed to the button only as display
subtitle, and there is no mechanism to hand it to the provider flow —
AuthProvider.Email has no defaultEmail-style parameter that the picker could populate.
The same applies to the other "Continue with X" variants, though for federated providers
the provider's own account picker masks it; for email the button is pure decoration.
Environment
com.firebaseui:firebase-ui-auth:10.0.0-beta03(ComposeFirebaseAuthScreen)Steps to reproduce
FirebaseAuthScreenwith an Email provider (plus others).previously used address as subtitle (from
SignInPreferenceManager).Observed
The email entry screen opens completely blank — identical to tapping the regular
"Sign in with email" button below the divider. The saved identifier shown on the
button is not used anywhere in the flow.
Expected
A "Continue as " affordance implies the identifier is carried into the flow:
either skip straight to the password step for that address, or at minimum pre-fill the
email field. Otherwise the button is a duplicate of the provider button and confuses
users (two buttons, same destination).
Analysis
In
AuthMethodPicker.kt,ContinueAsButton's click handler is justonProviderSelected(lastProvider)— the same callback and provider object as the plainprovider button. The
preference.identifieris passed to the button only as displaysubtitle, and there is no mechanism to hand it to the provider flow —AuthProvider.Emailhas nodefaultEmail-style parameter that the picker could populate.The same applies to the other "Continue with X" variants, though for federated providers
the provider's own account picker masks it; for email the button is pure decoration.