Hi @eliiza,
Thank you for reaching out.
Your understanding of the sequence is spot on, provided a specific setting is enabled within the original policy. Here is the breakdown of how Hexnode will handle this once the device transitions from offline to online:
The Critical Requirement: For the automatic uninstallation to occur, the original policy must have the following toggle enabled:
- Android > App Management > Required App > “Remove apps from the device on policy removal.”
If this is checked, Hexnode will queue an uninstall command the moment the policy is disassociated.
Execution Flow (When Device comes Online): Once the device reconnects, it processes the pending commands in the order they were received by the server:
- Uninstall Command: Triggered by the disassociation of the first policy.
- Install Command: Triggered by the association of the second policy.
Alternative Approaches: If you do not have the “Remove apps from the device on policy removal.” setting enabled, the app will remain on the device. In that case, you have two options:
- Manual Uninstall: Trigger a remote Uninstall Application action from Hexnode UEM.
- App Update: If the new APK has the same Package Name as the old one, you don’t need to swap policies. Simply update the APK file in the existing policy, and Hexnode will push it as a version update.
Regards,
Eden Pierce