Android app installation stuck at Initiated in HexnodeSolved

This usually happens when the managed Google Play Store component on the device is inactive or unable to process the app installation request.

In some cases, kiosk restrictions or an overlapping allowlist configuration can also prevent the required Play Store/system activity from running correctly. Try the following remediation sequence:

1. Open the device in Hexnode and go to the Applications sub-tab.
2. Search for Google Play Store. The package name is usually com.android.vending.
3. Use Clear App Data for Google Play Store.
4. After the action succeeds, run Actions > Scanning & Monitoring > Scan Device or Scan for apps to refresh the device status.
5. Trigger the app installation again from Actions > Install Application.
6. If the installation is still pending, use Actions > Remote App Launch and launch com.android.vending to wake the Play Store service on the device.

Also review whether both a kiosk policy and a separate allowlist restriction profile are applied to the same device. If both are configured to restrict apps or system components, they may overlap and block the Play Store processes needed for app installation. Streamlining the kiosk/allowlist setup can prevent future installs from stalling at “Initiated”.

Clearing Play Store data helped, but the action history still showed a new install action stuck at Initiated for a bit. Running a device scan and then launching the Play Store remotely seemed to kick it forward.