Sometimes, a device might get stuck on the provisioning screen. For Android devices, you can use the Onboarding Utility Window to diagnose, reboot, or change the network settings for the device. In this article, we’ll cover how to use the window and troubleshoot common issues.
This article describes how to address issues during provisioning. For app installation issues, see App Installation Troubleshooting.
In this article:
Using the Utility Window
If you attempt to install an incompatible app, have network interruptions, or experience other provisioning issues, your Android device may display a gear icon.
Click on the gear icon to access the utility window.
You’ll have the options to:
- Change the device’s Wi-Fi
- Reboot the device
- Or reset the device
Check the error message to determine your next steps.
Common Issues
INSALL_FAILED_NO_MATCHING_ABIS
This happens when the app’s native code does not match the CPU architecture of your device. For example, you might have an x86 app and are trying to install it on an ARM device.
To address this issue, you’ll need to update the blueprint with a compatible app. Then, the device will be converged to the new blueprint version. The converge action should allow the device to provision correctly.
Requested Range Not Satisfiable for URL
This happens when the device’s network is interrupted while trying to download an app.
To address this issue, try changing the device’s Wi-Fi from the utility window or relocate the device to an area with a stronger signal.
Use the Utility Window to troubleshoot your devices during onboarding.