Hi Experts,

One of our customers is using Intune MDM to distribute the FSM Android application. This required to rebuild the mobile application with a new application id (to sidestep the “Upload a new APK file with a different package name” stated here) and they had to generate a new google maps api key for this.

The question is w.r.t maintaining different versions of the application to cater for different environments (Dev, Test, Prod).

In the conventional approach of sideloading the app, I take it that there is only one APK file (with one Google Maps API key) and copies of this are maintained in separate locations for the respective environments. Hence, in the case of an upgrade or a customization rollout it’s possible to have the mobile application gradually be tested and upgraded across dev, test, prod. 

In the case of using an MDM, since it’s not possible to load in multiple APK’s with the same application id, is it the case that separate applications (copies of the same app) will have to be uploaded with different application id’s (by extension, different google maps API keys) to distinguish among separate environments (Dev, Test , Prod)? 

Has anyone had this setup with your customers who happen to use MDM for app distribution?

Cheers,
Miraj​​​​​​