Recent discussions
GSF ID not generated after device enrollment on Android 15
Hi everyone, We’re facing an issue with devices running Android 15 — after successfully enrolling them in our Android Enterprise setup (Device Owner / Fully Managed mode), the Google Services Framework (GSF) ID is not being generated. This issue did not occur on Android 13 or 14; the GSF ID was available immediately after enrollment. However, on Android 15, the GSF ID remains empty even after waiting and rebooting. We’ve already tried: Factory reset and re-enrollment Checking Google Play Services version Ensuring the device is connected to the internet Waiting for Play Store sync Despite that, the GSF ID is still missing. Could anyone confirm if there’s a known change in Android 15 related to GSF ID generation, or if additional permissions/configuration are required for enterprise-enrolled devices to obtain it? Any guidance or workaround would be greatly appreciated.You're Invited! Join us for the upcoming Android Enterprise CAFÉ Takeover!
Hello Community Members, The Android Enterprise team is excited to invite you to our upcoming in-person CAFÉ Takeover events in New York City and Paris! What is the Android Enterprise CAFÉ? The Android Customer Advisory Forum for Enterprise (CAFÉ) is an exclusive, invite-only group of customers who actively engage with the Android Enterprise Product team. As a member, you get a front-row seat to the future of Android Enterprise. Look out for more details about the Android CAFÉ in a future post. Join Us for the CAFÉ Takeover! We’re opening the CAFÉ experience to non-CAFE members with two in-person events. This is a fantastic opportunity to meet the Android Enterprise team, network with your peers, and share your feedback directly with us. These events are exclusively in-person. CAFÉ Takeover: NYC Date & Time: October 14th 10:00am (9:30 Check-in) Location: Google NYC RSVP here CAFÉ Takeover: Paris Date & Time: October 21st 10:00am (9:30 Check-in) Location: Google Paris RSVP here Please note: These are customer-only events and registration confirmation is required to attend. Space is limited, so please RSVP at your earliest convenience to secure your spot. We look forward to seeing you there! Best, The Android Enterprise Team
Gmail does not show certificate selection dialog when "exchange_login_certificate_alias" is not specified in managed configuration
Hi, I am trying to configure Gmail to work with Exchange ActiveSync within a work profile via managed configuration according to the documentation - https://support.google.com/work/android/answer/7065453 The following parameters are specified: "exchange_host", "email_address", "exchange_username", "exchange_authentication_type" (allow_modern_authentication) The "exchange_login_certificate_alias" parameter is not set. I expect that the user will have to select a certificate via the system dialog. But as a result of such a configuration, the certificate selection dialog is not displayed to the user. The mail setup process is interrupted and the error message "Try again later, or contact your IT admin" is displayed However, if I specify any random value in the "exchange_login_certificate_alias" parameter, the certificate selection dialog is displayed. I would like to know whether this is expected behavior or a known issue? Versions Info Gmail client - 2025.08.25.800175820.Release Android 13-16
URGENT: Unable to complete action required for account verification
2 of our accounts got emails this morning that we have to verify our org address because it no longer matches. However, going through verification we get an error at the end to contact support.... going through the support system and answering their questions led to the below need help ASAP as it states we will lose all our apps on July 10th!!!
getting ready for work setup get the issue of something went wrong your app cannot become device owner by the qr code provisison by json in android
i am facing the issue in android 14 or 15 when ever i build the unsigned build it work fine for the android 13 after that it give the error like something went wrong please contact to the it admin and i am build the singed build it give error for the checksum error cannot setup but same thing if i make my app as a device owner by adb command it work fine for me let me know how to fix this issue? i try to replace the checksum and i match both checksum both are same it getting error for me why? below is my mention qr code json, {"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.abc.abc/com.abc.abc.utils.receiver.MyDeviceAdminReceiver", "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "F-EJlegNKdVupdJupPmWz34s2INjWVUDS5ErL-DuETc=", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://downloadapk", "android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": true}
QR code provisioning - Run OEM Wizard
Hi, I've got a device owner app I've written, it's working well when I install it via a QR code, but I want the stock Pixel / Moto setup wizard to run during / after the device owner setup wizard. I've done quite a lot of research, this doesn't appear to be easy! Any pointers / leads in the right direction to how I might achieve this would be greatly appreciated. Methods, source code to read, etc. Thanks, Richard
Getting DEVICE_POLICY_MANAGEMENT role
I'm stuck with getting DEVICE_POLICY_MANAGEMENT role for my application. DevicePolicyManager reports that my application is active admin (isAdminActive() returns 'true') and device owner (isDeviceOwnerApp() returns 'true'). But role is not assigned ('dumpsys role' reports no holders for android.app.role.DEVICE_POLICY_MANAGEMENT). Pre-requisites for getting this role seem to be fulfilled (like required-components from roles.xml) Found this article from @jasonbayton saying "Only an OEM can grant this permission to an application". Does this mean there's no way for downloaded application to get DEVICE_POLICY_MANAGEMENT role and device's configuration files to be modified for granting this role (config_devicePolicyManagement)? Thank you!
Zero Touch Customer API Feature Request
{written in Gemini ;) who literally wrote this out perfectly} I'm requesting an enhancement to the Android Device Provisioning API (Zero Touch) to include filtering capabilities, specifically the ability to filter devices by serial number (and other relevant fields) in the initial API call. Current Situation: Currently, the API lacks direct filtering. As demonstrated in the code below, to find a device by its serial number, we must: Make a call to list all devices for a customer. Iterate through the entire list of devices in the response to find the specific device. Iterate through any following pages if not found on the first page. This is inefficient, especially for customers with a large number of provisioned devices. const listDevicesUrl = `https://androidprovisioning.googleapis.com/v1/customers/${customerId}/devices`; // ... const listResponse = await fetch(listDevicesUrl, { ... }); const listData = await listResponse.json(); let foundDevice = null; if (listData && listData.devices) { foundDevice = listData.devices.find(device => device.deviceMetadata && device.deviceMetadata.serialNumber === serialNumber); } Desired Feature: I propose adding a filter parameter to the device listing API, allowing us to directly query for devices based on specific criteria, such as serial number, manufacturer, model, and IMEI. For example, the API call could look like this: https://androidprovisioning.googleapis.com/v1/customers/{customerId}/devices?filter=serialNumber={serialNumber} This would significantly improve the efficiency of device management and reduce the amount of data that needs to be transferred and processed. Benefits: Improved Efficiency: Reduces the number of API calls and the amount of data transferred. Faster Processing: Speeds up device identification and management operations. Reduced Load: Decreases the load on Google's API servers and client applications. Simplified Development: Makes it easier for developers to integrate with the API. I believe that adding filtering capabilities to the Android Device Provisioning API would be a valuable improvement and would greatly benefit the Android Enterprise community. Thank you for considering our request.
