Restez organisé à l'aide des collections
Enregistrez et classez les contenus selon vos préférences.
Le processus de publication du SDK Android Management (SDK AMAPI) peut inclure une étape de version candidate dans le processus de publication standard.
Flux d'enregistrement des appareils amélioré pour les outils de contrôle des règles relatives aux appareils (DPC) personnalisés.
Cette approche simplifiée utilise le SDK AMAPI et l'application Android Device Policy (ADP) pour simplifier l'enregistrement des appareils.
Amélioration de la stabilité et des performances, avec des informations supplémentaires disponibles dans les exceptions de confiance des appareils. Consultez AmapiSdkException.
Version 1.5.0-rc01
24 juillet 2025
Cette version introduit un flux d'enregistrement des appareils amélioré pour les outils de contrôle des règles relatives aux appareils (DPC) personnalisés. Cette approche simplifiée utilise le SDK AMAPI et l'application Android Device Policy (ADP) pour simplifier l'enregistrement des appareils.
Nouveau package d'environnement
com.google.android.managementapi.environment pour configurer l'appareil pour Device Trust from Android Enterprise et, si nécessaire, pour installer ou mettre à jour l'application Android Device Policy.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/09/02 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Il n'y a pas l'information dont j'ai besoin","missingTheInformationINeed","thumb-down"],["Trop compliqué/Trop d'étapes","tooComplicatedTooManySteps","thumb-down"],["Obsolète","outOfDate","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Mauvais exemple/Erreur de code","samplesCodeIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 2025/09/02 (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 (AMAPI SDK) release process may include a release\ncandidate stage as 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| August 28, 2025 | | [1.6.0-rc01](#version-1.6.0-rc01) |\n| August 11, 2025 | [1.5.0](#version-1.5.0) | |\n\nDeclare dependencies\n\nTo add a dependency on AMAPI SDK, you must add the [Google Maven repository](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.5.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.6.0-rc01\n\n*August 28, 2025*\n\nThis version includes the following updates:\n\n- Introduce the possibility for EMMs using the Android Management API to install custom applications. See [Manage custom apps with AMAPI](/android/management/manage-custom-apps).\n- Increase `minSDK` to API Level 23.\n\nVersion 1.5.0\n\n*August 11, 2025*\n\nThis version includes the following updates:\n\n- 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.\n- Stability and performance improvements with additional information available in device trust exceptions; See [`AmapiSdkException`](/android/management/reference/amapi/com/google/android/managementapi/common/exceptions/AmapiSdkException).\n\nVersion 1.5.0-rc01\n\n*July 24, 2025*\n\nThis version introduces an improved device enrollment flow for custom Device\nPolicy Controllers (DPC). This streamlined approach uses the AMAPI SDK and the\nAndroid Device Policy (ADP) app to simplify device enrollment.\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 signals 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\n[Device Trust from Android Enterprise](/android/management/device-trust-api).\n\nThere are no differences with [v1.3.0-rc01](#version-1.3.0-rc01).\n| **Important:** Access to the device trust signals 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 Device Trust from Android\nEnterprise.\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 Device Trust from Android Enterprise 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."]]
