Managed Google Play private app not available on Corporate-owned devices with work profile

Could you double check how group assignments are set? Intune is a pain for hiding assigned apps from the store

Are the two devices the same device type / device model?

I've seen this kind of behavior in the past when an app is restricted to certain display sizes via manifest.xml. (I am thinking of this) Such apps could be installed manually as apk, but Google Play refused to install them.

I am not aware that an app can be restricted to certain Android management modes via manifest.xml / Managed Play.

A privateApp available for an OrganizationID is generally available to the UEM. The UEM then releases the app for certain GoogleUserIDs/GoogleDeviceIDs in the background, making the apps available on the devices in Managed Play. (at least with the EMM API)

Either the app assignment is not quite right, or the app is not compatible with certain devices.

hi,

i want to make an update of my initial post, because there are new findings.

a bit late, but we found out that the app developer used the "same" App Identifier, but case-sensitive, so for example:

App 1: com.android.myapp

App 2: com.Android.MyApp

in my point of view, i was thinking google does not allow this, but also on android itself it's possible to install apps side-by-side with that App Identifier like in my example.

It seems, that "Intune App" which is the controller on COPE Devices is not able to handle case-sensitive App Identifier, while "Company Portal App" on BYOD Devices is able to handle this.

On COPE Devices, App 2 is not visible because (i guess) Intune App is thinking that App exists already. Also interesting finding -> if i set in Intune App 2 as "Uninstall" then App 1 will be uninstalled. If i set in Intune App 2 as "Required" then also App 1 will be installed.

I'm quite sure this is a 100% Microsoft (Intune App) issue, but Microsoft Support is telling me, i need to Contact Google Support, because the App is not visible in "Managed Google Play Store".

My Question now is:

Where and how can i contact Google Support regarding Managed Google Play Store?

Thanks.

Lizzie  - Do you have any pointers here on how to get in contact with someone at Google support in cases like this where its related to Managed Google Play and private apps ? 

Me and w4lter have had a discussion around this issue over at the Intune subreddit. Im reaching out to some of my Microsoft contacts as well and I will be looking in to reproducing this issue as well. 

Hey Timmy and w4lter,

Thanks for sharing this information - good to know. It's certainly an interesting one! I wonder would you be willing to share the app bundle(s) with me via direct message perhaps? Then I can see if I can raise this internally? 

Thanks,

Lizzie

In general i would rather recommend to really use unique bundleIDs also to be sure not creating any kind of conflicts in the background.

I wasn't even aware that the Android package names are case sensitive. I haven't found much documentation on the Internet, e.g. information on the manifest.xml: https://developer.android.com/guide/topics/manifest/manifest-element

In the past, we had apps from external devs that also used capital letters, but different versions were clearly named. (e.g. with numbers at the end) This is definitely an interesting test case. I won't be able to test it in the next two weeks, but I would like to try it out with our UEM.

In any case, I find it strange that the app works with BYOD but not with COPE.

Check the Google Developer Console settings to ensure COPE device support isn’t restricted. Verify the app's visibility settings for corporate-owned devices. Since Intune shows it as available, try re-syncing Managed Play settings