Hi Brian,
Thanks for looking into this and filing the GitHub issue.
To clarify the behavior:
- With Two-Factor Authentication enabled, the user is unable to log in via Google Login at all — the login attempt fails.
- With Two-Factor Authentication disabled, the user logs in via Google Login successfully with no issues.
I also captured the console error during a failed login attempt for a 2FA-enabled user:
The request has been aborted.[GSI_LOGGER]: FedCM get() rejects with AbortError: signal is aborted without reason
This suggests Google’s FedCM sign-in request is being aborted mid-flow — likely because the redirect to the 2FA challenge screen interrupts it before the credential request completes.
Thanks,
Tejas