Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
El SDK de la API de Android Management (AMAPI) permite que apps específicas se comuniquen directamente con Android Device Policy (ADP). Incluye compatibilidad con lo siguiente:
Asegúrate de que el objeto minSdkVersion de tu app esté configurado en el nivel de API 21 como mínimo.
Agrega las dependencias de la versión más reciente del SDK de la AMAPI a tu aplicación. En la página de notas de la versión del SDK de la AMAPI, puedes encontrar la versión de la biblioteca más reciente disponible y cómo agregarla a tu aplicación.
Agregar elemento de consultas
Si tu app se segmenta para el SDK 30 o versiones posteriores, se necesita el elemento queries en AndroidManifest.xml para especificar que interactuará con ADP.
Algunas funciones requieren la creación de un NotificationReceiverService, y otras lo usan de forma opcional. Para usarlo, define una clase que extienda NotificationReceiverService, agrégala como un service a tu AndroidManifest.xml y asegúrate de que se exporte.
importcom.google.android.managementapi.notification.NotificationReceiverService;...publicfinalclassMyAppNotificationReceiverServiceextendsNotificationReceiverService{@OverrideprotectedvoidsetupInjection(){// This method can be optionally used to inject dependencies at the// beginning of the service lifecycle.}}
Por lo general, el ComponentName de tu clase que implementa NotificationReceiverService debe pasarse a través de una API adecuada.
Los detalles varían según la función en cuestión, y cada función que lo necesita lo documenta.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-07-24 (UTC)"],[],[],null,["The [Android Management API (AMAPI) SDK](https://maven.google.com/web/index.html#com.google.android.libraries.enterprise.amapi) enables specific apps to\ncommunicate directly with Android Device Policy (ADP). It includes support for:\n\n- [Local execution of Commands](/android/management/sdk-local-commands).\n- [Migrate devices managed with a custom DPC to AMAPI](/android/management/dpc-migration)\n- [Device Trust from Android Enterprise](/android/management/device-trust-api)\n\nThe following steps must be taken to integrate the AMAPI SDK with your\napplication:\n\n1. [Add the AMAPI SDK library](/android/management/sdk-release-notes#declare_dependencies).\n2. [Add the queries element](#add_queries), if target SDK \\\u003e= 30.\n\n| **Note:** If you are developing an extension app, you will also need to provision the device with an [extensibility policy](/android/management/sdk-local-commands#policy).\n\nPrerequisites\n\n- Ensure that your app's `minSdkVersion` is set to at least API level 21.\n- Add the dependencies for the latest version of the AMAPI SDK to your application. You can find the version of the latest available library, and how to add it to your application, in the [AMAPI SDK's release notes](/android/management/sdk-release-notes) page.\n\nAdd queries element\n\nIf your app targets SDK 30 or later, then queries element is needed in the\n`AndroidManifest.xml` to specify that it will interact with ADP. \n\n \u003cqueries\u003e\n \u003cpackage android:name=\"com.google.android.apps.work.clouddpc\" /\u003e\n \u003c/queries\u003e\n\nSee [Package visibility filtering on Android](https://developer.android.com/training/package-visibility) for more information.\n\nImplement a NotificationReceiverService\n\nSome features require creating a\n[`NotificationReceiverService`](/android/management/reference/amapi/com/google/android/managementapi/notification/NotificationReceiverService), and some features\nmake optional use of it. To use it, define a class extending\n`NotificationReceiverService`, add it as a `service` to your\n`AndroidManifest.xml`, and make sure it is exported. \n\n\n import com.google.android.managementapi.notification.NotificationReceiverService;\n\n ...\n\n public final class MyAppNotificationReceiverService extends NotificationReceiverService {\n\n @Override\n protected void setupInjection() {\n // This method can be optionally used to inject dependencies at the\n // beginning of the service lifecycle.\n }\n }\n\nIn your `AndroidManifest.xml`, add \n\n \u003cservice\n android:name = \".MyAppNotificationReceiverService\"\n android:exported = \"true\" /\u003e\n\nTypically the `ComponentName` of your class which implements\n`NotificationReceiverService` needs to be passed to us through a suitable API.\nThe details vary depending on the feature in question, and each feature which\nneeds this documents it."]]