[AppCheck] Remove reCAPTCHA site key support #8457
Conversation
Introduced `RecaptchaAppCheckProviderFactory.getInstance(String)` to allow passing the reCAPTCHA site key directly. Deprecated the site key methods in FirebaseOptions in favor of this new approach and updated the factory to support singleton provider initialization when using an explicit site key. Internal b/535703681
Removed `getRecaptchaSiteKey` from `FirebaseOptions` and deprecated `RecaptchaAppCheckProviderFactory.getInstance()` methods. Site keys must now be provided explicitly via `RecaptchaAppCheckProviderFactory.getInstance(String)`.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request deprecates the reCAPTCHA site key configuration in FirebaseOptions and moves it directly to RecaptchaAppCheckProviderFactory.getInstance(String). The feedback suggests removing the stateful caching of the provider and double-checked locking in RecaptchaAppCheckProviderFactory to avoid issues in multi-app environments. Additionally, it recommends updating the corresponding tests to verify delegation on every call and removing obsolete @SuppressWarnings("deprecation") annotations in FirebaseOptionsTest.
|
As mentioned in the description, it's expected that metalava will complain, but it's OK to ignore and not mark it as a major version bump. |
Removed
getRecaptchaSiteKeyfromFirebaseOptionsand deprecatedRecaptchaAppCheckProviderFactory.getInstance()methods. Site keys must now be provided explicitly viaRecaptchaAppCheckProviderFactory.getInstance(String).While the API existed, the support from the backend didn't. Because of it we are marking the change as non-breaking.