Hello
We are seeing unexpectedly low reCAPTCHA Enterprise scores for our iOS application starting around May 20, 2026.The tokens are valid, but many legitimate users are receiving low scores ( 0.1–0.2 >= ), affecting application flows.We don’t have active support plan, and there is no option to enable support plan for our project, can anyone point to right place for resolving this issueThank you.
Facing same issues. any updates here ?
We are facing the same issue.We are not completely sure when it started, but in the last few days many legitimate users have been getting very low reCAPTCHA Enterprise scores, mostly 0.1 or 0.2. The tokens are valid, but our login flow blocks them as suspicious/bot traffic.We did not make any intentional change to our reCAPTCHA implementation. Are there any updates from Google or recommended mitigations?
the same case here, mostly xiaomi user, but every device may happen, samsung, etc
and wifi or 3g,4g anything
We had been facing the same issue :|
this is the same issue which was discussed and resolved in the past
+2Hey all, Josh from the Fraud Defense team here. Can you please provide the mobile Site Keys where you’re seeing this issue so that we can dig in?
Site Keys are public information and accessible to anyone visiting your website or mobile app, so you can safely post them here, or email them to joshdorion@google.com if you’d prefer. Thanks!
I facing isuee when build module flutter for android native app. But for ios it oke.
When running in android score always is 0.2 or <0.3.
I try to change network, wifi. but it not increase score.
+2Hi all,
For the issue that started this thread, the problem has long since been resolved. If you are still experiencing problems, I recommend starting a new thread or opening a Cloud Support ticket. Thanks!
Has anyone been able to improve this?
The project I am involved in has not made any improvements at all.
Hi
+6Hi
Thanks for sharing the details — low reCAPTCHA Enterprise scores on iOS starting May 20, 2026 can happen even when tokens are valid. Here are some advanced checks you can try:
App telemetry changes → If the app stopped sending certain signals (device integrity, app attestation, network metadata), the risk model may downgrade scores.
SDK integration issues → Ensure the latest iOS SDK is used. Outdated SDKs sometimes produce incomplete signals.
Traffic anomalies → Sudden spikes in requests, shared IP ranges, or VPN/proxy usage can lower scores for legitimate users.
Score calibration → If your threshold is set too high (e.g., requiring ≥0.7), normal users with 0.1–0.2 may be incorrectly blocked.
Update SDK → Confirm you’re on the latest reCAPTCHA Enterprise iOS SDK.
Check app signals → Verify app attestation and device integrity checks are enabled.
Review traffic logs → Look for IP ranges or patterns that could bias scoring.
Adjust thresholds → Consider lowering the acceptance threshold temporarily to reduce user friction.
Use assessment API → Call the CreateAssessment endpoint to inspect why scores are low.
Since you don’t have an active support plan, the best path is:
Use the Google Cloud Support Community for peer troubleshooting.
File feedback directly in the reCAPTCHA Enterprise console — product teams monitor these reports.
👉 In short: validate SDK + app signals, check traffic anomalies, and adjust thresholds. If HX tokens are valid but scores remain low, it’s usually a signal calibration issue rather than a token failure.
Kind regards,
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
