Bug Report: Managed Google Play private app publishing fails with "INTERNAL" error

Summary

Publishing a private app via the Managed Google Play iframe embedded in Microsoft Intune (Apps → Android → Add → Managed Google Play app → Private apps) consistently fails with a generic "Can't publish app. Try again in a few minutes." UI error. Inspecting the underlying network request shows the backend RPC call returns an INTERNAL error code.

Environment

• Intune tenant: trial (Intune Plan 1)
• Managed Google Play enterprise: created via Intune's standard "identity" connection flow (no Google Workspace domain)
• Device tested against: Android, enrolled via Company Portal as Personally Owned Work Profile, showing Compliant in Intune
• Browser: [fill in your browser + version]
• Tested across: original Google account binding, and a completely fresh account after a full retire + unbind + reconnect cycle — same result both times
• Tested across two networks (to rule out local network/firewall interference) — same result on both after resolving an initial ERR_CONNECTION_CLOSED on one network

Steps to reproduce

1. In Intune admin center: Apps → Android → Android apps → Add → App type: Managed Google Play app.
2. In the embedded Google Play iframe, go to Private apps (grid icon in left rail).
3. Enter a Title (tested: "MAM POC", well under 30 char limit).
4. Upload an app file — tested with both a signed .apk and a signed .aab, both under 100MB.
5. Accept the Play App Signing terms (for .aab).
6. Click Create.

Expected result

App publishes successfully and syncs back into Intune's Android apps list.

Actual result

UI shows: "Can't publish app. Try again in a few minutes."

Inspecting the network request in browser DevTools (Network tab) for the failing request:

• Request: batchexecute?rpcids=McREPd with source-path=/managed/privateapps/createapp
• Response body: [["wrb.fr","McREPd","[null,\"INTERNAL\"]",null,null,null,"generic"], ...]

This confirms the request reaches Google's backend successfully (HTTP 200) but the specific McREPd RPC (private app creation) fails with Google's internal generic error code INTERNAL.

What's been ruled out

• Third-party cookies / browser extensions (tested in Incognito with extensions disabled)
• File size (well under 100MB limit)
• Package name collision (applicationId is a unique, non-generic reverse-domain name)
• Play Developer Distribution Agreement / pending account verification (none found)
• Local network/firewall blocking (tested on multiple networks; one network showed ERR_CONNECTION_CLOSED which was resolved by switching networks, but the underlying INTERNAL error persisted afterward)
• Stale/stuck account binding (fully retired device, unbound, and reconnected Managed Google Play with a brand new, never-before-used Google account — same error)
• "Reset to basic mode" — unavailable/greyed out, account already in basic mode

Ask

Please advise whether this is a known issue with private app publishing on "identity"-type Managed Google Play enterprises (i.e. those not bound to a verified Google Workspace domain), and/or whether there's a server-side fix or workaround available.