Forum Discussion
Accessibility Service with Managed Configurations not possible due to possible Work Profile bug?
Hi Moombas, that makes a lot of sense - I hadn't considered it in that way, thanks.
Although, if you put the accessibility service in the Personal profile and activate it, it sees the Work Profile fine, so if one doesn't work, the other probably shouldn't either! (Thankfully to us, it does)
I guess ideally it would only work against apps which are running in the same container, but given that it works in the public profile, it should probably work in the work profile too no? Otherwise companies cannot distribute these apps via their EMM.
No, i think it works as it should.
If the app is in work profile on private device (BYOD), work apps shouldn'T take affect on the DEVICE behavior which accessibility is part of.
If the app is on the personal profile this should affect the entire device (also the work profile regarding accessibility) as this is a system functionality somehow.
And yes i agree that such kind of apps won't work in BYOD. Not sure about COPE but definitely in fully managed (COBO).
Not sure if one of those is a possible use case on your end but otherwise you may need to provide it via apk/public maybe locked with a password/serial or similar.
Ok thanks for clarification. Going back to my original post, does that we can't use Managed Configuration in our app? Or is there a way to use Managed Configuration, Intune variables and install the app on the Public profile? Thanks again,
