"Internal Server Error" when approving Play Store apps: Google Service Account misconfiguration

Android

Title: "Internal Server Error" approving Play Store apps — fix Google Service Account

When approving or installing an app from Google Play in the Esper Console, the page returns an Internal Server Error try again! message and the app cannot be added.

Why this happens

Esper communicates with Google Play through a Google Service Account that is created automatically when you bind your tenant to Android Enterprise. If that binding is missing, inactive, or the underlying service account credentials have been revoked or rotated, Esper loses the ability to query Google Play and the request fails with this error.

Steps to resolve

1. Check your Android Enterprise binding status.
   In the Esper Console, go to Company Settings → Android Enterprise. Confirm that a Google account is shown as linked and that the binding status reads as active or enrolled. If the status shows as inactive, broken, or no account is listed at all, skip to step 3.
2. Verify the linked Google account is still active.
   Log in to your Google Admin Console and confirm the following:
   • Android Enterprise (or Android Device Management) is enabled for your organization.
   • The Google Workspace admin account used to create the Esper binding has not been suspended or deleted.
   • No service account credentials have been revoked or rotated since the binding was created.
   Any of these changes will silently break the service account link and trigger this error.
3. Re-establish the Android Enterprise enrollment.
   If the binding is broken or absent, re-enroll the tenant to generate a fresh service account:
   1. In the Esper Console, go to Company Settings → Android Enterprise.
   2. If an existing binding is present, unenroll it.
   3. Re-enroll using the standard Android Enterprise enrollment flow with a valid managed Google Play or Google Workspace account. Esper will automatically create and link a new Google Service Account when enrollment completes.
4. Attempt the app approval again.
   In the Esper Console, go to Apps & Configuration → Apps → Add App and select Play Store. Search for the app and complete the approval flow.

Verify: The app search returns results and the approval completes without an error message. The approved app should appear in your app library immediately and be available to assign to devices or Blueprints.

If this doesn't resolve it

If the error persists after re-enrolling, or if your Android Enterprise binding appears healthy but the problem continues, contact Esper Support and include the following:

• The exact name of the app you attempted to approve.
• Your tenant ID or company name (visible in Company Settings → General).
• A screenshot of the Internal Server Error try again! message.
• Confirmation of the binding status shown in Company Settings → Android Enterprise.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.