AI-generated Key Takeaways
-
Devices may not comply with a policy setting due to reasons like unsupported API level, management mode, or an app not being installed.
-
User actions, invalid settings, or incompatible apps and devices can also cause non-compliance.
-
Non-compliance can also occur if a required app is not updated or if the managing Google Cloud Platform project lacks permission.
-
A blocked app being installed is another reason a device might not be compliant.
-
Compliance issues can be pending, meaning the setting is expected to be applied shortly.
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. |
