Hello,
Thanks for reaching out to Hexnode Connect.
Since you have already isolated the issue from your corporate network and Kiosk Mode restrictions, this error typically points to a localized server handshake failure on the devices themselves. This is most frequently caused by corrupted cached data within Google’s core services or a conflict with the device’s web rendering component.
Here are the two primary solutions to resolve this issue:
1. Clear Google App Cache and Data
A corrupted cache often prevents Google Play Services from communicating properly during a fresh account sign-in. You will need to clear the data for three specific system applications.
- On the device, navigate to Settings > Apps & Notifications > See all apps.
- Locate Google Play Store, select Storage & cache, and clear both the cache and data.
- Repeat this exact process for Google Play Services and Android System WebView.
- Restart the tablet and attempt to add the Google account again.
Tip: If you need to perform this action across your entire batch of logistics tablets, you can execute the Clear App Data action remotely from your Hexnode portal instead of doing it manually on each device.
2. Rollback or Update Android System WebView
The embedded Google sign-in browser window relies heavily on Android System WebView. An outdated or corrupted update to this component can directly interfere with account authentication.
- If you have access to the Play Store, check if there is a pending update for Android System WebView and install it.
- Alternatively, if it was recently updated in the background, navigate to Settings > Apps > Android System WebView and select Uninstall updates. Rolling it back to the factory version often instantly resolves these sign-in crashes.
I hope this helps. If you find any more issues or need further assistance feel free to reach out.
Best regards,
George,
Hexnode UEM
15 Views
