I've managed to fix this issue (or at least avoid it) by disabling the reCAPTCHA SMS defence on Identify Platform. You'll need to open the link on that page somewhere where you're logged into the GCP Console and run it in the API Explorer tab that opens on the right. Make sure to swap the Request parameters -> Name to project/{id}/config. It'll say 'You have invalid or missing required parameter values above. If you execute anyway, the response will likely be an error.', but it worked for me.
The SDK then defaults to using the SKSafariViewController hosted captcha and provided you handle the callback via .onOpenURL or via AppDelegate then everything works as expected.
It seems that using reCAPTCHA SMS defence requires adding the reCAPTCHA SDK to your project, and configuring it, however for the Firebase iOS SDK I don't see where the configured reCAPTCHA client should be injected.
@ee99ee
Originally posted by @oliver-bevan in #17557
This issue is still live; @oliver-bevan has an appropriate workaround but please be advised that this is pretty hard to track down! See the closed issue for a description of what happens: if you enable the reCAPTCHA setting in Firebase (which enables Cloud Enterprise reCAPTCHA but is not clearly labeled as different from the built-in reCAPTCA support in Firebase settings), then disable it, your Firebase auth will continue to fail unless you disable this related setting that gets flips without confirmation or documentation.
There are multiple closed issues for this same issue; it's still reproducible today (April 2026).
Duplicates:
(Seems like this is probably a FirebaseAuth issue rather than platform SDK specific)
Originally posted by @oliver-bevan in #17557
This issue is still live; @oliver-bevan has an appropriate workaround but please be advised that this is pretty hard to track down! See the closed issue for a description of what happens: if you enable the reCAPTCHA setting in Firebase (which enables Cloud Enterprise reCAPTCHA but is not clearly labeled as different from the built-in reCAPTCA support in Firebase settings), then disable it, your Firebase auth will continue to fail unless you disable this related setting that gets flips without confirmation or documentation.
There are multiple closed issues for this same issue; it's still reproducible today (April 2026).
Duplicates:
(Seems like this is probably a FirebaseAuth issue rather than platform SDK specific)