Android APK stuck on Initiating during Hexnode onboardingSolved

Hello,

Thank you for reaching out to Hexnode Connect!

Since this issue is isolated to a single APK while all other required apps install normally, your Hexnode policy and device communication channels are functioning as expected.

When an APK gets stuck on “Initiating” until a manual scan is triggered, it typically points to an OS-level compatibility or background execution restriction on the device rather than a portal configuration issue.

I recommend checking the following:

1. Compare OS Versions: Check if the tablets where the app stalls are running a newer Android OS build compared to devices where it installs seamlessly.
2. Test Manual Installation: Try pushing the APK individually via Manage > Actions > Install Application. If it also hangs until a device scan is performed, the OS is holding the package installation process.

If the behavior is tied to specific OS builds, the newer Android version is likely delaying the APK’s background installer process until a manual sync forces the pending action to execute.

Best regards,
George
Hexnode UEM.

You hit the nail on the head! I tested this further and found that our older tablets are on an earlier Android version, while the new ones came with an updated OS build. When I flashed one of the newer tablets back to the older Android OS, the exact same APK installed automatically during onboarding.

Is there any setting on the Hexnode side that can bypass this OS restriction and force the APK to install silently on the newer Android version, or are we forced to change our deployment strategy?

Hello,

Thank you for reaching out to Hexnode Connect!

Thank you for confirming those test results! Because Hexnode uses the exact same deployment mechanism across all devices, there is no Hexnode-side policy setting or toggle that can override how a specific Android OS build handles an incompatible APK.

The manual device scan serves only as a temporary workaround by forcing an immediate sync to retry the pending command. For a permanent and reliable deployment across your fleet, you have two primary options:

• Update the APK: Have your development team rebuild or update the target APK to fully support the newer Android API levels and account for its background installation policies.
• Maintain Compatible OS Builds: Continue deploying devices on the verified, older Android OS version where the APK installs without intervention.

For high-volume onboarding, updating the APK for full compatibility with the target Android OS build is the best long-term solution.

Best regards,
George
Hexnode UEM.