Skip to main content
N1ko0
New Member
October 26, 2026
Question

App ships a managed configuration schema but Play never extracts it (managedProperties absent)

  • 1 reply
  • 12 views
  • Translate All • Beta, powered by Gemini

I manage our devices with Intune and I'm also the developer of the app, so I can see both ends of this.

Our app (com.nikosoft.nikokeyboardpro) has shipped app_restrictions.xml in every production release since 22 September. No EMM offers a configuration section for it. In Intune the app config policy comes up with nothing to fill in.

It isn't Intune. Querying Google directly, from a new enterprise that has never been bound to any EMM:

GET /v1/enterprises/{enterprise}/applications/com.nikosoft.nikokeyboardpro

managedProperties isn't in the response at all. Chrome returns 243 properties, Edge 229, Outlook 47 and Teams 5 on the same call. Our record is current: updateTime 2026-10-24, appVersions showing only the latest release, recentChanges with that release's notes. So Play read the release and produced nothing from it.

The schema isn't the cause. The build in production right now deliberately ships a cut-down version to test exactly that: three restrictions, two string and one bool, no choice entries and no arrays at all. Nothing is extracted from that either. The full 50-key file before it meets every documented requirement, parses on a device with loadXmlMetaData, and aapt2 shows the meta-data resolving in the APK.

This looks like the same failure as the Gboard thread here from May 2025, where Alex_Muc found appRestrictionsSchema empty in the MGP response and Lizzie confirmed on 6 June that a fix had been pushed. Same symptom, same layer, and like those users the only thing that works for us is uploading the APK to Intune directly as a line-of-business app and hand-writing the configuration JSON.

One difference worth flagging: Gboard lost a schema it previously had, whereas ours has never appeared at all. Our Play listing is years older than the schema, so I'm wondering whether extraction only runs when a product record is first created rather than on each release. That would explain why four production releases and a fresh enterprise approval have changed nothing.

Two questions:

1. Can the same kind of re-extraction be triggered for our product record?

2. Has anyone seen an app gain managedProperties after its listing already existed, or does the schema have to be present when the listing is first created?


Thanks!

1 reply

Moombas
Level 4.4: KitKat
October 27, 2026

In my opinion this points to something developping related which means i would recommend to reach out in the developer community (https://developer.android.com/community) as they most likely can tell you more.

Translate • Beta, powered by Gemini
Android Enterprise Expert