NonComplianceReason

  • Device non-compliance can stem from various factors, including unsupported API levels, incompatible management modes, or pending policy application.

  • User actions, invalid settings, and missing or outdated apps can also contribute to non-compliance.

  • Policy incompatibility may arise from the Android Device Policy version, blocked app installations, or app incompatibility with the setting.

  • Devices themselves might be incompatible with policy requirements, leading to non-compliance.

Reasons a device might not be compliant with a policy setting. See also specificNonComplianceReason.

Enums
NON_COMPLIANCE_REASON_UNSPECIFIED This value is not used.
API_LEVEL The setting is not supported in the API level of the Android version running on the device.
MANAGEMENT_MODE The management mode (such as fully managed or work profile) doesn't support the setting.
USER_ACTION The user has not taken required action to comply with the setting.
INVALID_VALUE The setting has an invalid value.
APP_NOT_INSTALLED The app required to implement the policy is not installed.
UNSUPPORTED The policy is not supported by the version of Android Device Policy on the device.
APP_INSTALLED A blocked app is installed.
PENDING The setting hasn't been applied at the time of the report, but is expected to be applied shortly.
APP_INCOMPATIBLE The setting can't be applied to the app because the app doesn't support it, for example because its target SDK version is not high enough.
APP_NOT_UPDATED The app is installed, but it hasn't been updated to the minimum version code specified by policy.
DEVICE_INCOMPATIBLE The device is incompatible with the policy requirements.
APP_SIGNING_CERT_MISMATCH The app's signing certificate does not match the setting value.
PROJECT_NOT_PERMITTED The Google Cloud Platform project used to manage the device is not permitted to use this policy.