Hexnode For Work crashes during Android Enterprise enrollment on iMin Swift 2 Pro Android 13Solved

Participant
Discussion
8 hours ago Oct 16, 2026

I’m trying to enroll iMin Swift 2 Pro devices running Android 13 as Android Enterprise Device Owner devices. After factory reset, I tap the welcome screen several times, scan the Hexnode QR code, and the setup starts normally. The Hexnode For Work app installs, but then it crashes before enrollment completes and the device goes back to the QR enrollment screen. The device never appears properly under Manage.

I tested this on two units, across multiple Wi-Fi networks and a mobile hotspot. Older devices of the same model that were enrolled earlier are still working fine. Android 15 iMin kiosk devices also enroll without any issue. The crashing units install Hexnode For Work v18.6.0 during enrollment, while some older working devices were enrolled before that version.

Is there any workaround for getting these Android 13 iMin Swift 2 Pro devices enrolled without the QR enrollment crash?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
47 minutes ago Oct 16, 2026
Marked SolutionPending Review

This behavior points to the Hexnode For Work app closing before the Android Enterprise Device Owner flow completes. Since the app crashes before enrollment finishes, the device may not appear correctly in the Hexnode portal, or it may appear only partially enrolled.

A useful workaround is to try Android Enterprise enrollment using the afw# identifier instead of the QR code flow. This bypasses the QR scanner portion of setup and downloads Hexnode For Work directly during Android setup.

Try the following on a factory-reset device:

  1. Power on the device and connect it to Wi-Fi.
  2. On the Google account sign-in screen, enter:

afw#hexnode

or

afw#hexnodemdm

3. Continue through the Android Enterprise setup prompts.

4. If a crash dialog appears but the Android Enterprise permissions screen remains behind it, dismiss the crash dialog and continue the setup.

5. Once the home screen loads, open Hexnode For Work.

6. If prompted, manually enter your Hexnode UEM portal URL.

7. Grant the required permissions such as notifications and battery optimization exemptions.

8. Allow the enrollment and policy application process to continue. On slower POS hardware, this may take longer than expected.

In one similar case, the device eventually completed enrollment after several minutes and reached the kiosk activation screen. This should be treated as a workaround rather than the expected enrollment experience.

Regards,
Mary Romero

Save