9fea3de8f5205a6a95252d1e9ab8eaaeaf4e3660
- The launcher package is automatically enabled for work profiles due to DPM interpreting it as a critical component since it does not have any launchable activities. Once enabled, it is possible for an explicit broadcast to update smartspace or assistant state to trigger the process to be created for the work profile user, which ends up initializing logic which may call into LauncherApps (which is not allowed from the work profile). As a workaround, we disable the launcher application immediately upon detecting that it is running in a work profile. Bug: 120550382 Change-Id: I72c52fe598d41440a1fb59304b494a000277384b
Description
No description provided
Languages
Java
57.2%
Kotlin
42.4%
AIDL
0.3%