Can't add a new private app to a Collection in Managed Google Play Store (Intune)
Hello, i've recently published a new private app to our Managed play Store through the iFrame in Intune. I can assign the app now, install it and search for it on the Work Profile Play Store on my phone but i can't find the app when i want to add it to a collection. We have a few similar private apps already published and these work fine. It is only the most recent one i can't find in the collections. Is there another Sync i am missing or is it a problem with our Managed Play Store? Thanks for the help. BR SebUsing paid apps in corporate environments
Hi all, I'm just wandering about using paid apps on work devices and wanted to know how others here are working with paid apps. Another brand I shall not name makes it possible to purchase apps via a portal and then deploy those apps to your end users. But Google / Managed Google play does not offer such a solution. It makes it difficult to deploy paid apps. While most apps offer license options outside the playstore, not all of them do. How do people on the community deploy paid apps that need to be purchased through the playstore? As said before, just wandering what solutions people use to better advise our customers in such cases. I don't get this question a lot, but every few weeks it pops up somewhere (mainly because we also provide services on the dark side hardware). I'm aware that this has been mentioned a few years ago on this community, but just seeing if this have evolved. Distributing Paid Apps | Android Enterprise Customer Community - 653 Thanks! Michel
Intune Managed Google Play Store Risk
Wondering if anyone has come across a way to restore an "app collection" in the Managed Google Play Store? I would like to be able to take a back up and restore the collection should it be deleted in error. On a shared tenant basis and having only 1 account for the MGPS is something we need to have steps in place for.
Issue with Copy/Paste Restriction in Intune MDM on Android Devices (Clipboard Editor Interaction)
Hi all, I’m currently experiencing an issue while setting up Intune MDM on Android devices related to restricting copy and paste to unmanaged apps. Specifically, the issue occurs when users copy text from the Teams app and try to paste within teams app. Here's what happens: After copying text, a message "Your organisation's data cannot be pasted here" immediately appears in the clipboard hud. The copied data seems blocked from being viewed, as the error message appears even before a paste attempt. Despite this, users can manually paste the copied content by long-pressing or selecting "Paste" from the text box. However, when trying to use the "paste from clipboard" feature, the warning message above is pasted instead of the copied content. We’ve set the Intune policy to allow copy/paste within managed apps, but the clipboard interaction seems to be problematic, especially with Gboard. It appears that Gboard, possibly due to Android 13 and 14’s Clipboard Editor, is treated as an unmanaged app, causing Intune’s data protection policies to block its access to the clipboard in a read-only state. Just to clarify: I want users to be able to copy and paste txt within managed apps only. So the allowed behavior of pasting with long press is fine, but I want to get rid of the block that we're getting. Here’s what we’ve tried: Added various exclusions to the Intune policy, including Gboard, Clipboard Editor, and other related apps (full list below), but the issue persists. Testing different configurations hasn’t led to a final solution, and there seems to be limited documentation specifically addressing this clipboard component in relation to Intune's data policies. We’ve escalated the issue internally but wanted to see if anyone in the community has encountered a similar problem or found a solution. Here’s the list of exclusions we’ve already added to the policy: Clipboard: com.android.clipboard SMS: com.google.android.apps.messaging SMS: com.android.mms SMS: com.samsung.android.messaging Native phone app: com.android.phone Google Play Store: com.android.vending Android system settings: com.android.providers.settings Android system settings: com.android.settings Google Maps: com.google.android.apps.maps Gboard: com.google.android.inputmethod.english Samsung: com.sec.android.inputmethod Gboard: com.google.android.inputmethod.latin Gboard: com.google.android.apps.inputmethod.hindi Gboard: com.google.android.inputmethod.pinyin Gboard: com.google.android.inputmethod.japanese Gboard: com.google.android.inputmethod.korean Gboard: com.google.android.apps.handwriting.ime Gboard: com.google.android.googlequicksearchbox Gboard: com.samsung.android.svoiceime Gboard: com.samsung.android.honeyboard Gboard: com.android.inputmethod.latin Teams app: com.microsoft.teams Any insights or suggestions would be greatly appreciated! This is my first time posting so apologies if this is the wrong space.
AE managed apps are not auto installed on devices after device enrollment
Hello, We manage Android mobile devices with an Ivanti MobileIron MDM. For the past few days, we have been experiencing issues with forced installations—they are no longer being pushed to our devices (silent install). Ivanti has indicated that Google support tickets have been opened. Bug referenced at Ivanti: It shows gms complaining about bad authentication in bugreport: [RequestTokenManager] getToken() -> BAD_AUTHENTICATION. App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/experimentsandconfigs Current understand of possible cause is that when issue occurs, google play account failed to got authenticated and re-auth could not recover it properly in time. Resolution We have several tickets open with google for now, and working with google on this issue. Google ticket number: 399818918 398768257 395681748 393388830 Google is rolling out a backend fix. Do you perhaps have more information about the issue and/or its resolution ? Are other people affected ? Thank you in advance for your help :) Adam
The Ongoing Evolution of Android: Where Do We Go From Here?
Android has come a long way since its early days, evolving from a basic smartphone OS to a powerful platform that powers billions of devices worldwide. With every major release, we see improvements in performance, security, design, and user experience. From Android’s open-source flexibility to the introduction of Material You and AI-driven features, the platform keeps pushing the boundaries. One of the strengths of Android has always been its customization. Users love being able to tweak their device—from launchers and widgets to ROMs and root access. However, as Android becomes more polished and secure, some of these freedoms have become more limited. Is the trade-off worth it? Another topic worth exploring is Android’s fragmentation. While it gives manufacturers flexibility, it also creates inconsistency in updates and app performance. With initiatives like Project Treble and Android One, Google has made strides, but are we seeing real results? And now with AI integration, foldable phones, and powerful chipsets becoming the norm, it’s exciting to think about where Android is headed next. What are your thoughts on the current state of Android? Are you satisfied with the direction it’s going, or do you miss the old Android freedom? What improvements would you like to see in the next version? Looking forward to hearing everyone’s thoughts!
Help Needed: Issue with Deploying Managed Google Play private App
I'm trying to deploy a Managed Google Play app on Samsung Galaxy tablets using Intune. The devices are enrolled as Corporate-owned with a work profile. The app is uploaded to the Play Console, approved by Google, and synced with Intune, but it's not deploying. Intune reports the devices as not applicable, and the app isn't visible in the work-badged Play Store. I've tried different assignment settings, switching between "required" and "available," and tested both user-based and device-based groups separately. I also experimented with BYOD enrollment types, but none of these approaches worked.
Common identifier between AMAPI & Require for setup app for validation
We are enrolling devices using AMAPI by generating a QR code with an assigned policy either for work profile or fully managed enrollment. During enrollment, the device prompts for a require for setup app, which, after configuration, returns RESULT_OK, marking the setup as complete and finalizing the device enrollment. Before returning RESULT_OK, To identify the enrolling device, the backend gets the device ID and enterprise ID from the Pub/Sub provisioning notification. The device ID (which matches the GSF ID) is then sent by the require for setup app to the backend for validation. This identifier is also used to enforce enrollment limits based on the enterprise license count. The Issue: Up to Android 14, retrieving the GSF ID was possible. However, in Android 15, it now returns null. Question: Is there an alternative identifier that can be used to identify the enrolling device—one that the backend can retrieve and that the setup app can also access during enrollment? Below is the information we receive from Pub/Sub when a device is enrolled: { "name": [*Hidden for privacy reasons] "managementMode": "PROFILE_OWNER", "state": "PROVISIONING", "enrollmentTime": "2025-04-04T06:17:02.751Z", "lastPolicySyncTime": "2025-04-04T06:17:02.817Z", "softwareInfo": { "androidVersion": "15", "androidDevicePolicyVersionCode": 10323580, "androidDevicePolicyVersionName": "128.32.3 (10323580)", "androidBuildNumber": "AP3A.240905.015.A2", "deviceKernelVersion": "5.15.149-android13-8-00010-gc2e0ba41ba85-ab12040008", "bootloaderVersion": "unknown", "androidBuildTime": "2025-03-11T13:26:50Z", "securityPatchLevel": "2025-03-01", "primaryLanguageCode": "en-IN", "deviceBuildSignature": "c9009d01ebf9f5d0302bc71b2fe9aa9a47a432bba17308a3111b75d7b2143456", "systemUpdateInfo": { "updateStatus": "UP_TO_DATE" } }, "hardwareInfo": { "brand": "Redmi", "hardware": "mt6835", "deviceBasebandVersion": "MOLY.NR17.R1.TC8.PR2.SP.V1.P51,MOLY.NR17.R1.TC8.PR2.SP.V1.P51", "manufacturer": "Xiaomi", "serialNumber": [*Hidden for privacy reasons] "model": "23124RN87I", "enterpriseSpecificId": [*Hidden for privacy reasons] }, "policyName": [*Hidden for privacy reasons] "memoryInfo": { "totalRam": "5865836544", "totalInternalStorage": "806965248" }, "userName": [*Hidden for privacy reasons] "enrollmentTokenName": [*Hidden for privacy reasons] "securityPosture": { }, "ownership": "PERSONALLY_OWNED" } *Updated by Community admin - removed due to privacy reasons 4 April
