Forum Discussion
Workprofile creation failure using CUSTOM DPC
We use a custom DPC to create work profiles. On certain devices, profile creation fails with errors like STORAGE_UNAVAILABLE or work profile already exists. From bug reports, we can confirm the failure cause, but is there a way to detect these conditions directly in our app and handle them gracefully?”
2 Replies
Sorry for the delayed response Emilie_B . We are referring to the same scenario.
However, consider this case: the Admin sends an enrollment invite to enroll devices as Work Profile. When the end users try to enroll their devices, they encounter issues such as Work Profile creation failures with no clear resolution.
Currently, the end users need to collect the bug report and share it with the Admin, who then forwards it to the EMM team for analysis.
Instead of this, if the DPC app could receive callbacks indicating why the Work Profile creation failed, it could handle the issue accordingly and provide appropriate guidance to the user.
Hi Ragulsurendar - hope you're well!
Apologies for the delayed answer; I've checked with the team and they said that the profile creation failing when the work profile is already there is working as intended.
Similarly, the work profile will not be created if there are not enough storage space.
When you say you can confirm the failure on the bug report, are you describing the above or was there another cause of failure? Can you give an example of what a graceful handling would you like to see?
In most cases, when a profile already exists, the work profile creation will just fail to successfully install.
Please let us know if this is helpful 🙂
