Menu
I have an app which has been using the SafetyNet Attestation API for some time.
All of a sudden, all calls to the API started failing. Did something happen to the SafetyNet Attestation API?
276
asked Jun 21 '18 04:06
SafetyNet tripping and its consequences If you root your Android device or replace the stock firmware with a custom ROM, you will pretty much end up with a SafetyNet failed status. As a result, you can't use apps and games that employ SafetyNet validation on the device.
The SafetyNet Attestation API provides a cryptographically-signed attestation, assessing the device's integrity. In order to create the attestation, the API examines the device's software and hardware environment, looking for integrity issues, and comparing it with the reference data for approved Android devices.
As mentioned in the documentation and Google's checklist for SafetyNet Attestation integration, it is now mandatory to use an API key to use the SafetyNet Attestation API.
Previously, it was possible to use the SafetyNet Attestation API without an API key, and you would get a default quota (not specifically assigned to your project). This default quota is now deprecated.
The usage of the shared quota unnecessarily exposed your traffic to project-specific throttling and may have caused errors for other users of the API.
Around April 2018, Google started blocking new users of the SafetyNet Attestation API (as identified by the application's package name) from using this default quota.
Most existing clients now use API keys, but if your project doesn't, all unauthorized traffic without an API key started failing permanently from August 1, 2018.
If you were using the SafetyNet Attestation API without a key, you must now use a key. The good news is that doing so is free, and it's very easy!
108
answered Sep 28 '22 07:09
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With