Distribute apps with existing package names via Managed Google Play / MDM

[Schwerdti]

Hi,

in general, Android Enterprise devices are always getting the latest version of an app that is available via Managed Google Play. But, there are some edge cases like:

• older version needed (example: Citrix Workspace app deprecated app for Android 11 and below, might be problematic for special devices like handheld-scanners)
• beta tests (example: Microsoft Teams, would be awesome to provide this inside the Work profile)

In both cases you are receiving APKs from the vendors. For Citrix Workspace they are available here: Download Earlier Versions of Workspace app for Android - Citrix

I've tried to discover possibilities to publish them via Intune (should be equal for other MDMs):

• Private App in Managed Google Play
  • Problems:
    • Package Name not unique:
      The package name com.citrix.Receiver is already used by another application.
    • APK too big.
      Limit of 100 MB 
• Distribute app via Google Play Console / Developer
  • private app scoped to Org. ID
  • but, same problems as on Managed Google Play
• Change package name to something like "com.citrix.Receiver.contoso"
  • tested with: https://apktool.org/
  • upload: package name now OK, but signature invalid
    "APK signature is invalid or does not exist. Error from apksigner: string_arg: "ERROR: JAR_SIG_NO_MANIFEST: Missing META-INF/MANIFEST.MF"

Did I oversee something? Asking the vendors to build a custom app with own bundle name isn't feasible.
Is there no way to publish such apps via MDM to Android Enterprise devices?

[jasonbayton · Accepted solution]

Hi @Schwerdti 

To start with the question - no there's no way to push an app with a duplicate package name via iFrame as one that's already on the store. The store mandates a unique package name, and won't support a duplicate. You really should work with the vendor to generate a custom package name for an app where this is your desired approach. 

For Betas, the vendor should offer a dedicated app track to subscribe to from their existing developer account ideally, especially since it's not legacy, but will likely get promoted to production. Microsoft may already have this set up.. and then you can stipulate a track ID within the EMM.

Your alternative to either is to deploy outside of play, and the EMM you're using would need to support this. Plenty do - SOTI, WS1, some OEM MDMs do for their own devices. Depends on what you're using.

[Schwerdti]

Thanks for the fast reply! This proves my observations and tests.

Let me address this topic on Microsoft Intune side as deployment outside of Google Play is the only way...