What's new 
A newly enrolled Android tablet has a required app assigned through policy, but the app is not installing. In Hexnode Action History, the install action only shows as “Initiated” and stays that way for a long time. The tablet was tested both inside kiosk mode and outside kiosk mode/admin mode, but the app still did not install. Clearing the Google Play Store app data was tried from the device’s Applications tab, and a Scan for apps action completed successfully, but the install application action still appeared stuck at “Initiated”. What else can be done when an Android app install is stuck like this?
26 Views
Replies (2)
Marked SolutionPending Review
Hexnode Expert
23 hours ago
Aug 09, 2026
Marked SolutionPending Review
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:
- Open the device in Hexnode and go to the Applications sub-tab.
- Search for Google Play Store. The package name is usually
com.android.vending. - Use Clear App Data for Google Play Store.
- After the action succeeds, run Actions > Scanning & Monitoring > Scan Device or Scan for apps to refresh the device status.
- Trigger the app installation again from Actions > Install Application.
- If the installation is still pending, use Actions > Remote App Launch and launch
com.android.vendingto 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”.
Marked SolutionPending Review
Participant
18 hours ago
Aug 09, 2026
Marked SolutionPending Review
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.
Save