'Google Identity One-Tap Sign-In Exception: Caller has been temporarily blacklisted due to too many canceled sign-in prompts
I am currently working on migration to One-Tap Sign-In, and after I tried few times on the device, my device gets blacklisted with exception (Caller has been temporarily blacklisted due to too many canceled sign-in prompts). Just wondering what's the threshold from being blacklisted? And is there anyway we can remove ourself from blacklist?
Also is this a correct behavior at all? after user try to open login and cancel few times and we have to fallback to the default google sign-in instead because the one-tap gets blacklisted?
Solution 1:[1]
If you encounter this 24-hour cooldown period during development, you can reset the cooldown by clearing Google Play services' app storage.
https://developers.google.com/identity/one-tap/android/get-saved-credentials#disable-one-tap
Solution 2:[2]
If you encounter this 24-hour cooldown period during development, you can reset the cooldown by clearing Google Play services' app storage. Alternatively, to toggle on/off this cool down on a test device and/or emulator alike, simply go to the Dialer app and input the following code:
*#*#66382723#*#*. Upon submission, there will be no feedback, but your dialer will clear all input and may close. The cooldown should be toggled off after this. To toggle it back on, input the same code again.
just go to the Dialer app and input the following code: *#*#66382723#*#*
and try to call.
https://developers.google.com/identity/one-tap/android/get-saved-credentials#disable-one-tap
Solution 3:[3]
Taken from @mco post. Just making the steps more clear here,
From Android device > "Settings" > "All Apps" or "Apps"> "Google Play Services" > "Storage" > "Clear cache"
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | AdrianoCelentano |
| Solution 2 | Alexander Popov |
| Solution 3 | Arthur |