Google Play service action required promptSolved

Have you tried switching between the G-Suite admin and user accounts instead of deleting the G-Suite admin account and then adding the G-Suite user account?

Yeah! I kept both G-Suite admin and user accounts at the same time and tried switching from admin to user account, but the result was the same.

Also, I tried adding a Gmail account instead of the G-Suite user account, and checked the following case:

1. Switched between the G-Suite admin account and the Gmail account.
2. Deleted the G-suite admin account after adding the Gmail account.

For both cases, the Google services were completely accessible.

Hi @Frida, I’ve had the same experience with G-Suite admin and user accounts. Enrolled my device using G-Suite admin credentials, and then added a G-Suite user account. When I switched to the user account, all Google services were blocked, and every Google app I opened kept redirecting me to the Hexnode UEM app homepage.

• This reply was modified 9 months ago by  ben_clarke.
• This reply was modified 9 months ago by  ben_clarke.
• This reply was modified 9 months ago by  ben_clarke.

Hi @Frida,

Thanks for reaching out to us.

Upon checking the issues you raised, we have found that the problem occurs when trying to use a Google Workspace user account on a device enrolled through Android Enterprise Device Owner using Google Workspace admin credentials. Please consider the following suggestions to solve this.

1. If you have enrolled your device as the Android Enterprise Device Owner using Google Workspace admin credentials and you wish to use Google services, it is recommended to continue using the same admin account on the device.
2. If you prefer using a different user account for Google services, it is recommended to perform a device reset. After the reset, you can proceed to enroll the device with the specific user account you want. If you opt for a Gmail account instead of a Google Workspace admin account after deleting the admin account, the access to Google services on the device remains unchanged. However, the features that can be deployed from Hexnode UEM to the device will become restricted. The issue arises when the account used to enroll the device is no longer available on the device.

By following the suggested solutions, you should be able to resolve the problem. If you have any further difficulties or questions, feel free to reach out.

With Regards,

Ben Clarke

Hexnode UEM