[macOS] Enable Process support on MacCatalyst

[MaximLipnin]

For these API's, they should work near equivalent as they do on OSX. There may be small behavior differences when App Sandbox is enabled. We should determine where the spots are and account for them.

PNSE for Process on iOS / tvOS, but enabled for MacCatalyst.

@akoeplinger @steveisok

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to 'os-ios': @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Since the private Apple APIs are not available on iOS/tvOS (e.g. see #61265 (comment)), they are going to be excluded on those platforms but still may work on MacCatalyst.
To handle such cases, we need to add code to detect App Sandbox at runtime. For example, Process.Start() would need to know whether it can work.
Also it would make sense to throw a proper PlatformNotSupportedException() when sandbox is enabled.

@akoeplinger @steveisok

Author:	MaximLipnin
Assignees:	-
Labels:	untriaged, os-ios
Milestone:	-

[mdh1418]

Do we only want to throw PlatformNotSupportedException for private Apple APIs when App Sandbox is enabled? Does using the APIs when the sandbox isn't enabled throw errors?

Is it clear yet what all the private APIs/system resources we would want to throw PlatformNotSupportedException when Sandbox is enabled? (are these the only ones? _proc_listallpids, _proc_pid_rusage, _proc_pidinfo, _proc_pidpath)

[MaximLipnin]

Do we only want to throw PlatformNotSupportedException for private Apple APIs when App Sandbox is enabled? Does using the APIs when the sandbox isn't enabled throw errors?

If I'm not mistaken, that's mostly about Mac Catalyst so if one wants to publish catalyst app to App Store then they have to enable sandbox and must not use those private API. In this case we will throw PNSE.
Otherwise, in case the sandbox is off, theoretically some apple APIs might not work (tbh, no idea which ones), then we could throw PNSE as well.

Is it clear yet what all the private APIs/system resources we would want to throw PlatformNotSupportedException when Sandbox is enabled? (are these the only ones? _proc_listallpids, _proc_pid_rusage, _proc_pidinfo, _proc_pidpath).

Perhaps, this list is not full atm. Having done app sandbox detection, we can handle all such APIs one by one.

[steveisok]

If I'm not mistaken, that's mostly about Mac Catalyst so if one wants to publish catalyst app to App Store then they have to enable sandbox and must not use those private API. In this case we will throw PNSE. Otherwise, in case the sandbox is off, theoretically some apple APIs might not work (tbh, no idea which ones), then we could throw PNSE as well.

Yes, this is correct. Some customers will use MacCatalyst as a desktop application and never publish to the AppStore. It would make sense for that group to not have the sandbox enabled and use the api's that would otherwise be restricted.

[mdh1418]

Because it sounds like Sandbox contains damage, then should there be warnings if Sandbox is disabled and some private Apple APIs and system resources are accessed to let the customers know that it might affect their system? Is that something that should be from our end?

[steveisok]

Because it sounds like Sandbox contains damage, then should there be warnings if Sandbox is disabled and some private Apple APIs and system resources are accessed to let the customers know that it might affect their system? Is that something that should be from our end?

I think it may depend on how we want to surface the PNSE.

@rolfbjarne do you know if turning the sandbox on and off is a project setting?

[rolfbjarne]

@rolfbjarne do you know if turning the sandbox on and off is a project setting?

It's an entitlement that's configured per project, so yes, it's effectively a project setting.

I have a few thoughts:

• Apple may change what's allowed and not in the sandbox in the future. For instance, Apple might introduce a new entitlement that allows apps in the sandbox to launch processes.
• Normal macOS apps can also be sandboxed, it's not restricted to Mac Catalyst (although I believe what the app can and can't do inside the sandbox differs).
• I think the sole purpose of detecting the sandbox would be to able to give the developer useful information if something fails - it's not in any case meant to replace/substitute/replicate the sandbox itself.
• To our knowledge, Apple does currently not scan macOS/Mac Catalyst apps for usage of private/disallowed APIs when publishing them on the App Store - the only restriction is that the app has to be sandboxed, and then at execution time, some APIs will fail in a sandboxed environment (this isn't restricted to private APIs: posix_spawn and other process-launching APIs aren't private, they're just not allowed in the sandbox).