Improved device enrollment flow for custom Device Policy Controllers (DPC).
This streamlined approach uses the AMAPI SDK and the Android Device Policy (ADP)
app to simplify device enrollment.
Stability and performance improvements with additional information available
in device trust exceptions; See AmapiSdkException.
Version 1.5.0-rc01
July 24, 2025
This version introduces an improved device enrollment flow for custom Device
Policy Controllers (DPC). This streamlined approach uses the AMAPI SDK and the
Android Device Policy (ADP) app to simplify device enrollment.
New Environment package
com.google.android.managementapi.environment to set up the
device for Device Trust from Android Enterprise and, if necessary, to install or
update the Android Device Policy app.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[[["\u003cp\u003eIntegrate the Android Management SDK by adding the Google Maven repository and necessary dependencies to your project's \u003ccode\u003ebuild.gradle\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eUtilize the \u003ccode\u003ecom.google.android.libraries.enterprise.amapi:amapi\u003c/code\u003e dependency, ensuring you always use the latest version for optimal performance and stability.\u003c/p\u003e\n"],["\u003cp\u003eVersion 1.1.4 introduces a new DPC Migration package to facilitate device migration to AMAPI, with guidance available in the provided documentation.\u003c/p\u003e\n"]]],["To use the Android Management SDK, add the Google Maven repository to your project's `repositories` block. Include the necessary artifacts in your app's `build.gradle` file within the `dependencies` block, using `implementation`. The latest stable version of the library, such as 1.1.5, is recommended for bug fixes. Version 1.3.0-rc01 includes the Device Trust signal APIs, while version 1.1.4 introduced a DPC Migration package.\n"],null,["The Android Management SDK release process may include a release candidate stage\nas part of the standard release process.\n| **Key Point:** A release candidate is a prospective release implementing the final API surface.\n\nLatest Update\n\n| | Stable Release | Release Candidate |\n|---------------|-------------------------|-------------------|\n| June 18, 2025 | [1.4.0](#version-1.4.0) | |\n\nDeclare dependencies\n\nTo add a dependency on Android Management SDK, you must add the [Google Maven\nrepository](https://developer.android.com/build/remote-repositories#google-maven) to your project: \n\n```groovy\nrepositories {\n ...\n google()\n}\n```\n\nAdd the dependencies for the artifacts you need in the `build.gradle` file for\nyour app or module: \n\n```groovy\ndependencies {\n def amapi_version = \"1.4.0\"\n\n implementation \"com.google.android.libraries.enterprise.amapi:amapi:$amapi_version\"\n}\n```\n\nFor more information about dependencies, see [Add build dependencies](https://developer.android.com/build/dependencies).\n| **Key Point:** Always use the latest available stable version of the library to benefit from the available bug fixes and improvements.\n\nVersion 1.4.0\n\n*June 18, 2025*\n\nThis version includes the [`Device.WorkProfileState`](/android/management/reference/amapi/com/google/android/managementapi/device/model/Device.WorkProfileState) signal to identify the\ndevice [management state](/android/management/device-trust-signals#management-state).\n\nThere are no differences with [v1.4.0-rc01](#version-1.4.0-rc01).\n| **Important:** Access to the Device Trust from Android Enterprise API is restricted using an allowlist to prevent unauthorized usage. For additional information see: [**Device Trust from Android Enterprise - API access**](/android/management/device-trust-register).\n\nVersion 1.4.0-rc01\n\n*June 02, 2025*\n\nThis version includes the [`Device.WorkProfileState`](/android/management/reference/amapi/com/google/android/managementapi/device/model/Device.WorkProfileState) signal to identify the\ndevice [management state](/android/management/device-trust-signals#management-state).\n\nVersion 1.3.0\n\n*Apr 14, 2025*\n\nThis version includes the first release of the\n[Device Trust from Android Enterprise](/android/management/device-trust-api) API.\n\nThere are no differences with [v1.3.0-rc01](#version-1.3.0-rc01).\n| **Important:** Access to the Device Trust from Android Enterprise API is restricted using an allowlist to prevent unauthorized usage. For additional information see: [**Device Trust from Android Enterprise - API access**](/android/management/device-trust-register).\n\nVersion 1.3.0-rc01\n\n*Feb 18, 2025*\n\nThis version includes the first release candidate for the Device Trust signal\nAPIs.\n\n- New Device Trust Signal package [`com.google.android.managementapi.device`](/android/management/reference/amapi/com/google/android/managementapi/device/package-summary)\n- New Environment package [`com.google.android.managementapi.environment`](/android/management/reference/amapi/com/google/android/managementapi/environment/package-summary) to set up the device for the Device Trust from Android Enterprise API and, if necessary, to install or update the Android Device Policy app.\n\nVersion 1.1.5\n\n*May 13, 2024*\n\nThis version includes the following updates:\n\n- Bug fixes and internal improvements.\n\nVersion 1.1.4\n\n*January 24, 2024*\n\nThis version includes the following updates:\n\n- New DPC Migration package [`com.google.android.managementapi.dpcmigration`](/android/management/reference/amapi/com/google/android/managementapi/dpcmigration/package-summary) to support device migration to AMAPI. For additional information you can review the guide [*Migrate existing devices to AMAPI*](/android/management/dpc-migration).\n\nVersion 1.0.1\n\n*February 15, 2022*\n\nThis version includes the following updates:\n\n- Bug fixes and internal improvements.\n\nVersion 1.0.0\n\n*September 20, 2021*\n\nThis version includes the following updates:\n\n- Initial release."]]
