-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop calling GetRecaptchaConfig in phone auth when cached config is e… #8504
base: rce-phone
Are you sure you want to change the base?
Conversation
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
Purpose: Reduce calls to
GetRecaptchaConfig
and avoid exceeding its quotaAt the start of the phone number verification flow, we check the cached phone rCE enablement state. If the cached config is empty or disabled, we don’t call
GetRecaptchaConfig
, and proceed with reCAPTCHA v2 token and “NO_RECAPTCHA”.Developers who enable rCE must call initializeRecaptchaConfig to populate the cached rCE config before initiating phone auth. We recommend calling it when the app starts, ideally. This is also currently recommended for email auth flows.