AMAPI application-role background activation (optional). A new, off-by-default build option lets an AMAPI-based EMM start the generated app in the background by assigning it an application role, so its contacts sync begins without the app ever being opened. This addresses the case where a force-installed app sits idle in Android's "stopped" state until someone launches it. Leave the option unticked and the app is built exactly as before, with no extra dependencies, services or permissions. Enabling it requires an AMAPI-based EMM, the app deployed through AMAPI's custom-app path with its signing certificate authorised in policy, and a free application-role slot.
Fixes
Enabling AMAPI activation no longer fails the build. The first build of the enabled option could run out of memory while packaging the larger app; enabled builds now run with sufficient headroom.
Known issues
N/A
Further support or feature requests
Are you in need of further help, or would you like to raise a feature request? You can: