SOTI Pulse

Home
Community
When App Catalog rule modified to remove an app, uninstalls other flavor of app along with expected flavor.

When App Catalog rule modified to remove an app, uninstalls other flavor of app along with expected flavor.

Solved

Hi All,
We've an android app with 2 flavours: AppFlavor1 & AppFlavor2.
Both are having same Application Bundle Id : "com.mycompany.newapp"
AppFlavor1 distributed using Google PlayStore.
AppFlavor2 distributed through SOTI using package & not released to Play Store.
For a Customer, Application catalog rule is used to install AppFlavor1 on few devices.
On few devices AppFlavor2 was installed.
Customer modified this existing Application catalog rule. He removed AppFlavor1 from App Catalog rule.
This resulted in uninstalling of AppFlavor1 as well as AppFlavor2 from devices.
Uninstalling of AppFlavor2 was not expected here. This has happened because of same application bundle id.

Is there a way where SOTI can distinguish between 2 apps so that when application catalog rule changed,
it uninstalls app which is installed through PlayStore only.
Here in this case, it should uninstall AppFlavor1 & NOT AppFlavor2.

Thanks in advance.

appflavors appbundleid appcatalogrule

3 years ago

Android

ANSWERS

Raymond Chan

3 years ago

Hi Sandip,

How do you know and make sure that the installed app from EACH of those devices with both App-catalog rule and package deployed had been installed from package rather than from the App-catalog rule? In fact, for any device with the two conflicting policies targeted, which policy is entertained first in real-time on each device is actually a random process. It is the administrator's responsibility to make sure that CONFLICTING policies are not deployed. This principle also applies to other policies deployed with profiles for any device platform, not just Android.

Hence, those group of devices with app deployed with package should NOT have the conflicting app-catalog rule deployed in the first place.

Solution