Understanding Google's Play Integrity API Changes

Google has recently introduced changes to its Play Integrity API to enhance security and ensure that Android apps run on trusted environments. As part of these updates, we are now using the enhanced MEET_DEVICE_INTEGRITY verdict of the Play Integrity API to determine if a device meets Google's security requirements.

What Happens When MEET_DEVICE_INTEGRITY Fails?

If a device fails the MEET_DEVICE_INTEGRITY check, it indicates that it does not meet the security standards established by Google Play. This failure can be due to several reasons, including:

1. Rooted Device

A rooted device grants superuser (administrator) access, allowing users to modify system files and install unauthorized applications, bypassing Android's built-in security mechanisms.

• Why it fails: Rooting can interfere with tampering detection or compromise the device's security, resulting in a failed integrity check.

2. Custom ROM

A custom ROM is a modified Android version replacing the default firmware, often developed by third-party developers to alter the device's functionality.

• Why it fails: Custom ROMs may lack essential security features or certifications required by Google Play Integrity checks, making the device appear non-compliant.

3. Uncertified Device

Uncertified devices have not passed Google's compatibility tests and are not officially listed to run Google apps and services.

• Why it fails: Such devices do not support Google Play Protect and may lack essential security standards, triggering an integrity check failure.

How We Are Incorporating These Changes

To align with Google's updated security measures, we have implemented an advanced security check within our platform. This check ensures that your app operates only on trusted and compliant devices, enhancing content security.

Steps to Ensure Your App's Security

Follow these steps to manage the new security settings and maintain your app's safety across all user devices:\

1. Go to your dashboard and navigate to "Mobile App".

2. Under the "Apps" section, select "App Builder" and click on "Configuration".

3. Scroll down to locate "Learner Permissions."

4. You will see an option titled "Skip Advanced Security Check." By default, this option is turned off, ensuring that all security measures are in place.

5. If you enable this option, please note that we will no longer guarantee content security across different user devices, although a basic security check will still be provided.

By keeping the "Skip Advanced Security Check" option disabled, you can rest assured that your content remains secure and protected from unauthorized access.

Common Error Codes

Below are the common error codes users may encounter and their explanations:

• 001 - Google Play Services Unavailable

  • Google Play Services are not available on this device.

• 002 - Device is Rooted

  • The device has been detected as rooted or modified.

• 003 - Integrity Token Response Failure (No Error)

  • The integrity token response failed, but no specific error was returned.

• 004 - Unexpected Play Integrity Token Response Exception

  • An unexpected exception occurred while processing the Play Integrity token response.

• 005 - Integrity Token Response Failure

  • The integrity token response failed to process successfully.

• 006 - Device Integrity Failed

  • The device failed the integrity check and does not meet security requirements.

• 007 - Play Integrity API Verification Failure

  • The Play Integrity API verification failed due to an unknown issue.

• 008 - SafetyNet API Response Failure

  • The SafetyNet API response failed to process successfully.

If you have any questions or require further assistance, please reach out to our support team at support@graphy.com