android-management-api

问题 Background I currently maintain a Kiosk app on devices managed by the Android Management API. These devices run Android 7. I had been managing the app updates on these devices via the application minimumVersionCode , and moving the devices onto a new policy every time with a higher minimumVersionCode , forcing the affected devices to update the app. However some of the devices would factory reset if they had been off for a reasonable period of time (a week or two) even after extending the

问题 Background I currently maintain a Kiosk app on devices managed by the Android Management API. These devices run Android 7. I had been managing the app updates on these devices via the application minimumVersionCode , and moving the devices onto a new policy every time with a higher minimumVersionCode , forcing the affected devices to update the app. However some of the devices would factory reset if they had been off for a reasonable period of time (a week or two) even after extending the

问题 I am building an Android KIOSK app, and I try to enable kiosk mode with Android Management API by providing a device policy. My policy json is: { "keyguardDisabled": true, "applications": [ { "packageName": "my.own.app", "installType": "KIOSK", "defaultPermissionPolicy": "GRANT" } ] } What's interesting, the policy is from official API's example, so I suppose that works. Whatever, always get this error: Error info persistentPreferredActivities 4 And just a google search does not give me any

问题 We have some android devices attached to Android Management API as fully managed work devices. Now when we push out some changes to the device policy such as Factory Reset Disabled , Adjust Volume Button Disabled or any other such controls, the devices don't sync it immediately. In fact we have to manually open up Android Device Policy and click on Sync for it actually get the changes. This is really troublesome because at times the policy doesn't sync for hours together and the devices don't

问题 Our Android native Companion App is automatically installed on the device upon enrollment. The matching profile entry is: "packageName": "app.domain.companionapp", "installType": "REQUIRED_FOR_SETUP", "defaultPermissionPolicy": "GRANT", "managedConfiguration": { "key1": "value1", "key2": "value2" }, "delegatedScopes": [ "ENABLE_SYSTEM_APP", "PACKAGE_ACCESS" ] We have pushed an update on the Play Store more than a week ago. But the update does not install automatically on the devices, even if

问题 Our Android native Companion App is automatically installed on the device upon enrollment. The matching profile entry is: "packageName": "app.domain.companionapp", "installType": "REQUIRED_FOR_SETUP", "defaultPermissionPolicy": "GRANT", "managedConfiguration": { "key1": "value1", "key2": "value2" }, "delegatedScopes": [ "ENABLE_SYSTEM_APP", "PACKAGE_ACCESS" ] We have pushed an update on the Play Store more than a week ago. But the update does not install automatically on the devices, even if

问题 This is driving me nuts. I've successfully followed the Android Management API Quickstart to create a project/enterprise/policy and install it on a device. I stupidly didn't write down the enterprise or policy IDs. I tried to create a new set, but the non-enterprise email now gives an error that it's already part of another EMM. Is there a place in the console where I can see a list of the enterprises and/or policies that I've created? Where are these stored? Edit: I found the enterprises.get

问题 So I'm trying to get a single use, dedicated app + device to work in kiosk mode + auto launch. The app itself is built in Nativescript (with Angular), so not native Java, however this is still handled via an admin receiver etc as normal. When we use adb to set the device owner, kiosk mode works as expected. adb shell dpm set-device-owner com.domain.app/.DeviceAdminReceiver When we use an Android Management policy to enrol the device and auto install, the kiosk mode is never initiated

问题 So I'm trying to get a single use, dedicated app + device to work in kiosk mode + auto launch. The app itself is built in Nativescript (with Angular), so not native Java, however this is still handled via an admin receiver etc as normal. When we use adb to set the device owner, kiosk mode works as expected. adb shell dpm set-device-owner com.domain.app/.DeviceAdminReceiver When we use an Android Management policy to enrol the device and auto install, the kiosk mode is never initiated

问题 One of our customers wants to enable the single kiosk mode with a web app. When we apply this configuration, it doesn't work: the web app is not displayed, and the device is not usable (even if the Chrome app is installed). When the kiosk mode is disabled, the web app is perfectly usable. So I guess there is an issue on the AMAPI side. Here is the application data of the profile: "applications": [ { "packageName": "com.google.enterprise.webapp.<generated-id>", "installType": "KIOSK",