Email enumeration protection is on by default for new projects. This breaks UniversalEmailSignInScreen and other Firebase UI Auth APIs that use fetchSignInMethodsForEmail under the hood.
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.
[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] All unit tests pass (melos run test:unit:all doesn't fail).
Description
Email enumeration protection is on by default for new projects. This breaks UniversalEmailSignInScreen and other Firebase UI Auth APIs that use fetchSignInMethodsForEmail under the hood.
Read more details here https://cloud.google.com/identity-platform/docs/admin/email-enumeration-protection
Related Issues
Closes #148
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
). This will ensure a smooth and quick review process. Updating thepubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.melos run test:unit:all
doesn't fail).Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?