Forum Discussion
(COPE) Hide app in work profile
Hello, I have a small case I'd like to submit to the community for help please. A customer use Mobile Iron, and use Zero Touch to enroll our Android 14 products. In their DPC extras, they enabled...
Yunchuan
Can you say what the customer's purpose is for “LEAVE_ALL_SYSTEM_APPS_ENABLED:true”?
Is there a included non-system app that would otherwise not be available? Or is a certain system app simply no longer available in the Work Profile?
Has the customer tested the policies with devices from another OEM? Can apps be deactivated correctly in the Work Profile?
I don't know the current status at Ivanti regarding CustomDPC vs. AMAPI. If a CustomDPC is still in use, we actually have a good comparison with WorkspaceONE. However, I cannot reproduce the problems described.
We have the option to blacklist apps. (For Work Managed and in the Work Profile) This uninstalls (non-system) apps. System apps are blocked and hidden. However, you can also explicitly enable system apps if, for example, they have been deactivated via the DPC Extra. For example, we would only need “LEAVE_ALL_SYSTEM_APPS_ENABLED:true” for Work Managed devices if an OEM supplies a non-system app that is not available in the PlayStore.
Thanks for the suggestions.
They have indeed tested on 2 of our products, the policies work on our old model running Android 12 but don't work on our newer model on Android 14
Ivanti uses this API: https://developer.android.com/reference/android/app/admin/DevicePolicyManager#setApplicationHidden(android.content.ComponentName,%20java.lang.String,%20boolean)
Hm, that could be a bug in the newer model. It doesn't seem to be due to the configuration and we don't have any problems with Android 14.
Have you ever requested a bug report / verbose logcat logs from the customer? Ideally, you might see errors there. The policy controller triggers the action and the system gradually works through the necessary steps. Maybe an error occurs during a single action, as a result of which the app remains visible in the launcher. But that's just a guess for now.
For example, these are two of many pieces of information when Google Meet is deactivated in the Work Profile (=userId 10):02-28 12:18:37.159 1167 31382 I PackageManager: setApplicationHiddenSettingAsUser, packageName: com.google.android.apps.tachyon, userId: 10, hidden: false, callingUid: 1000, callingPackage: system 02-28 12:18:40.827 1167 1367 I SettingsProvider: onPackageRemoved (userId 10) PackageName = com.google.android.apps.tachyonThanks Alex, will do further testing, we have only verified with the test DPC that the API was working fine
