Paris and I chatted about your issue and we realised that it has a bit more subtlety than we first thought.
First up, it’s not clear whether the app that hits this issue is one of your apps, or whether you’re hitting it an app created by a different third-party developer. We can help you in the first case, but in the second case you should talk to that app’s developer.
Assuming that you are the one creating this app, the alert you’re seeing is the result of a feature known as app group container protection. There’s a link to the WWDC video that introduced this feature in Trusted Execution Resources. I also have a bunch of info about app groups in general in my App Groups: macOS vs iOS: Working Towards Harmony post.
As explained in that last post, you don’t see this alert if all the apps accessing the app group are from the same team. However, there’s no way to avoid it if you’re trying to access an app group associated with some other team. The example you posted suggests you’re accessing a Microsoft Office app group. So, unless you happen to be working for Microsoft, it’s going to be tricky to avoid this alert.
My general take an that is that, if an app vendor expects other folks to be messing around with their files, they should create some sort of service to mediate that access.
Finally, one last thing that’s important to note here is that when the user allows this access it’s only persists for the lifetime of the calling process. There’s no way to grant this privilege persistently.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
