SafetyNet API: Change in classification for some developer devices

[SafetyNet API Clients Team]

Dear SafetyNet API Clients,

SafetyNet is rolling out a policy change next week that affects the classification of a small amount of devices typically used for software development.

Devices with an active, root capable adb debugging session are going to be classified as non CTS compliant and will also be failing basic-integrity checks. 

The change will affect ~0.1% of all devices, primarily developer devices*. 

Most of the affected devices (96%) are already being classified as CTS non-compliant for other reasons. Many (12%) have been failing basic-integrity checks as well.

Should this change cause user-visible impact in your product, we suggest updating your help center articles. A simple remedy for the affected users is to switch off USB debugging when using your app.

Regards

SafetyNet API Team

--

* Creating a root capable adb debugging session is a deliberate process. Users have to flash the device to a developer build, enable Developer Options, enable USB debugging, connect the device to a host machine, and approve the connection.