Our app is unable to write to its own sandbox container on macOS when run via “My Mac (Designed for iPad)”. This is not an issue when the app runs on iPhone or on iPad. So, the one thing to understand here is that the sandbox enforcement system operates at a low enough level of the system that I can't really fail*, at least not in a broad, systemic way. That's particularly true of apps running compatibility mode, which are designed to operate with very limited access. *Putting that in more concrete terms, if the basic app sandbox configuration is broken in some large-scale way, then the entire system tends to fall apart. That dynamic makes large-scale problems hard to... miss. Because of that, the assumption I'd start with here isn't may app can't read/write its files, but is instead either: I'm trying to access the wrong place. Something external to my app is interfering with my app’s ability to function. Expanding on that second point, it's important to remember that macOS is FAR more flexible/configurable
Topic:
App & System Services
SubTopic:
Core OS
Tags: