Hi Milan,
What I mentioned was having the Agent inside the admin profile and invoke
work profile creation from the Agent. Then preferences problem will not
occur. Anyway we will try this as well as all possible methods and finalize
the best approach by the end of this week.
What's critical for us
Hi Kasun,
I have tried this flow for AFW and we cannot actually follow that flow. The
reason because when we enroll an user to EMM, we store some private data in
the device's shared preference. In AFW scenario, it creates a new instance
of the agent in a secured container and we cannot access that
Adding dev@.
Given below will be the flow that we will implement for Android for work.
As I have studied, all the AFW is based on profile concept. Android M have
introduced some powerful APIs to give a better meaning to this. Refer the
thread "[EMM] Android M EMM features + Android for work" threa
