Forum Discussion
[Feedback] App installs: share your experiences & suggestions
The limitation is based on the AMAPI's REQUIRED_FOR_SETUP, and not limited to which EMM we're using. See this policy here:
https://developers.google.com/android/management/reference/rest/v1/enterprises.policies#installtype
I think, from what i read, you do the app providing the wrong way.
You provide apps the normal way after the enrollment is done and then you can use for example https://developers.google.com/android/management/reference/rest/v1/enterprises.policies?hl=de#installtype:~:text=Anwendungen%20delegiert%20werden.-,BLOCK_UNINSTALL,-Gew%C3%A4hrt%20Zugriff%20auf to block the unintallation if needed (without a limit of apps being provided) which i see as the only reason for using your option mentioned before.
Users must not be able to uninstall the app, which is provided for us through "required for setup"
The app(s) also needs to be installed before the device is provisioned, as its functionality is critical to the additional setup that needs to be done before a user can use it for it's provided use-case.Hmm, sounds weird foir me but as i don't know the background of your setup won't target on that as on my understanding it's like:
Enroll device into MDM (which requires max. one app (the app needed by the MDM to enroll the device into it)), then the MDM provides all apps and settings to the device.
And on our end one step between, as we need the enduser to type in something which is grabbed by the MDM to provide the final configurations/apps and after that is ready to use.
Means, the device is not used before all apps and settings are provided by the MDM. And we don't need the "setting" you mention but can provide one that endusers are not allowed to manage apps (install/uninstall,...).
