Solved

FSM Android MDM distribution query

  • 21 November 2022
  • 2 replies
  • 103 views
M
Rank
Userlevel 4
Badge +9
  • Miraj
  • Sidekick (Partner)
  • 59 replies

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​​​​​​

icon

Best answer by roklde 21 November 2022, 14:05

View original

2 replies

roklde
Rank
Userlevel 6
Badge +23

Hi Miraj,

it’s exactly as you said, you will have to provide another custom app with a different identifier to allow two parallel code tracks.
For example, when distributing the iOS App through ABM we always provide two Apps. One is for the use with the production environment and the other (usually having the suffix “NEXT”) is used for non-production environments.

 

Best regards
Roman

G
Rank
Userlevel 3
Badge +8

We tried to rename packages and it works, but is a nightmare. Hundreds of references in the source code to the original package name and some you have to leave as is and some you have to change to the new package name.

I am trying this using build variants to create appended package names. It is working for prod so far, but the customer is not live and this hasn't been tested extensively. The new package name would look like: com.metrix.metrixmobile.<cust>prod.

Reply


Terms & ConditionsCookie settings