Denied app PHONE_STATE permission in Knox workspace
I have an app that listen to the regualr phone dialer incoming and outgoing calls and then takes actions.
The app works perfectly in the personal area.
The same exact app when installed in the Knox container area cause permission denial error like:
“W/BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.PHONE_STATE flg=0x1000010 (has extras) } to com.confidentialtele.call/.service.IncomingCallReceiver requires android.permission.READ_PRIVILEGED_PHONE_STATE due to sender android”.
The error occures only on outgoing calls.
The app was installed in the workspace (either by remotely by EMM or locally on device) with all required permissions (Telephony permission) and still causing the above error.
I’ve also set ALLOW to any app restriction in the Knox profile.
Please advise how to resolve this issue.
*I’m the developer of the app.
Regards
Assaf
Hi Assaf,
I was not able to completely recreate your issue. I ran an app that created a log statement with the phone number invovled in a phone call on any incoming or outgoing call (eg. "Incoming call from +17395559274") on a Note8 running Android 8.0 and Knox 3.1. When I ran this app inside and outside of a container I was able to see the phone number and whether the call was incoming or outgoing, even though I also received the same permission denial error you did. The difference in outcomes could be due to the device you are running this on. Could you please provide me with the device model, Android version, Knox version, and build number of the device you are testing on?
As well, make sure you have manually enabled the phone permission for your app inside the container, by going through the container settings. The phone permission was not automatically enabled when I installed my app.
Best regards,
Mikayla