إتاحة إمكانية تثبيت تطبيقات مخصّصة لمزوّدي خدمة إدارة الخدمات الجوّالة للمؤسسات (EMM) الذين يستخدمون Android Management API يُرجى الاطّلاع على إدارة التطبيقات المخصّصة باستخدام AMAPI.
زيادة قيمة minSDK إلى المستوى 23 من واجهة برمجة التطبيقات
الإصدار 1.5.0
11 أغسطس 2025
يتضمّن هذا الإصدار التحديثات التالية:
تم تحسين عملية تسجيل الأجهزة لوحدات التحكّم المخصّصة بسياسة الجهاز (DPC).
يستخدم هذا النهج المبسّط حزمة تطوير البرامج (SDK) لواجهة برمجة التطبيقات AMAPI وتطبيق "سياسة جهاز Android" (ADP) لتبسيط عملية تسجيل الأجهزة.
تحسينات على مستوى الثبات والأداء مع توفّر معلومات إضافية
في استثناءات موثوقية الجهاز، يمكنك الاطّلاع على AmapiSdkException.
الإصدار 1.5.0-rc01
24 يوليو 2025
يقدّم هذا الإصدار مسارًا محسّنًا لتسجيل الأجهزة في وحدات التحكّم المخصّصة في سياسة الجهاز (DPC). يستخدم هذا النهج المبسّط حزمة تطوير البرامج (SDK) الخاصة بواجهة برمجة تطبيقات إدارة Android (AMAPI) وتطبيق "سياسة جهاز Android" (ADP) لتسهيل عملية تسجيل الأجهزة.
حزمة "بيئة جديدة" (New Environment)
com.google.android.managementapi.environment لإعداد
الجهاز لاستخدام ميزة "ثقة الجهاز" من Android Enterprise، ولتثبيت تطبيق Android Device Policy أو تحديثه إذا لزم الأمر.
تاريخ التعديل الأخير: 2025-09-02 (حسب التوقيت العالمي المتفَّق عليه)
[[["يسهُل فهم المحتوى.","easyToUnderstand","thumb-up"],["ساعَدني المحتوى في حلّ مشكلتي.","solvedMyProblem","thumb-up"],["غير ذلك","otherUp","thumb-up"]],[["لا يحتوي على المعلومات التي أحتاج إليها.","missingTheInformationINeed","thumb-down"],["الخطوات معقدة للغاية / كثيرة جدًا.","tooComplicatedTooManySteps","thumb-down"],["المحتوى قديم.","outOfDate","thumb-down"],["ثمة مشكلة في الترجمة.","translationIssue","thumb-down"],["مشكلة في العيّنات / التعليمات البرمجية","samplesCodeIssue","thumb-down"],["غير ذلك","otherDown","thumb-down"]],["تاريخ التعديل الأخير: 2025-09-02 (حسب التوقيت العالمي المتفَّق عليه)"],[[["\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."]]
