Skip to main content
A
Angus
New Member
March 25, 2025
Question

How to allow Android Enterprise Org ID can access opentest (or internal test) version of OEMConfig on Google Play?

  • March 25, 2025
  • 1 reply
  • 0 views

We are trying to test OEMConfig with testing track (internal testing or closed testing) before make it public release new version to Google Play. However, the account with Enterprise Org ID is not able to access these versions. The account can only access Google Play App, private Apps. Is there any method to allow us accessing the testing track version apk in order to get the Schema of new version apk in order to submit to devices for configuration change.   Attached screenshot show the managed Play iframe. It only show the public version of this app.

Thanks

Angus

1 reply

J
jeremy
Level 1.6: Donut
March 25, 2025

I think the correct way to do this with managed configuration and with EMM not supporting different tracks, would be to have another application with another package name.

You would whitelist enterprise ID to access this "beta" package name. People with access will then be able to retrieve the correct managed configuration and test the application, as it will be another package name.

 

 

    A
    AngusAuthor
    New Member
    March 31, 2025

    Thanks Jeremy,

      I use different package name and upload to open test track and add our organization id to manage google play to allow manage EMM iframe can search and select this open test app. It works as our expetation. However, the apprestriction info cannot be parsed by the managed google play iframe. Try to rebuild another package name and upload as private app, iframe works normally. Please advise what solution I can make to resolve this issue. Thanks in advance.

     

     

    J
    jeremy
    Level 1.6: Donut
    March 31, 2025

    Hello,

    I would say that this is an issue with your configuration and your application. Please double check everything on that side but I don’t see any reason why your configuration is not appearing here when it should if this is not an issue with the configuration. 

    Terms & ConditionsCookie settingsAccessibility statement