This behavior usually indicates that the Android Enterprise binding is no longer syncing correctly with Google’s Android Enterprise API.
When the API returns “No enterprise was found for the given id,” Hexnode cannot validate the existing Enterprise ID. As a result, the Managed Google Play app inventory may appear empty, and Android app deployments can remain stuck in the Initiated state.
If this started immediately after an Android Enterprise reconfiguration, avoid repeatedly disenrolling and reconfiguring the integration until the sync issue is cleared. Reconfiguring while the binding is not being accepted will not restore app deployment.
Once the synchronization issue is resolved, test app deployment again. If the app inventory is still empty or deployments remain stuck, re-establish the Android Enterprise connection:
- Go to Admin > Android Enterprise.
- Disenroll the current Android Enterprise setup.
- Reconfigure Android Enterprise with the correct managed Google account.
- Re-add the required Managed Google Play apps so the app inventory can sync again.
- Retry the app deployment from Hexnode.
After the binding is restored, apps should move past Initiated and deploy normally.
Regards,
Mary Romero