APK deploymentSolved

Hi @monty,

You can configure this in Hexnode so updates happen automatically whenever you upload a higher version.

You can follow the steps below:

Step 1: Prepare the new build (Android Side)

Before uploading the APK to Hexnode, make sure:

1. The versionCode is incremented (for example, from 1 to 2). This is mandatory. Android uses this value to determine whether the app is newer.
2. The versionName is updated (for example, from 1.0 to 1.1). This is mainly for tracking and visibility.
3. The app is signed with the same certificate as the previous version. If the signature changes, Android will not allow a silent in-place upgrade.

For additional reference, you can check out the Android Developer documentation on app versioning.

Step 2: Upload the new version to Hexnode

1. Log in to the Hexnode portal.
2. Navigate to Apps > +Add Apps.
3. Upload the updated APK as an Enterprise App.
4. Ensure the new build replaces or updates the existing app entry (with the higher version).

Step 3: Configure the app as Required in the policy

1. Go to Policies.
2. Select the policy assigned to your testing devices.
3. Navigate to App Management > Required Apps.
4. Click + Add, select your enterprise app, and save the policy.
5. Make sure the policy is associated with the relevant testing devices or device group.

When the device checks in, Hexnode will detect the higher versionCode and automatically deploy the update.

Regards,
Sienna Carter
Hexnode UEM

I have a similar requirement, but my devices are in kiosk mode. I don’t want to take them out from kiosk to update the app.

Hi @aitana,

If your devices are running in kiosk mode:

• Keep the app configured as a Required App in the policy.
• Ensure the updated version is uploaded correctly with an incremented versionCode.

Hexnode will deploy the newer version silently in the background, and the device will remain in kiosk mode during the update.

For more information, check out this documentation.

Regards,
Sienna Carter
Hexnode UEM