Is there a chance we could make unsandboxing apps a little easier? I'm building a little installer tool and I'm not fond of basically telling the user "figure out where i live and unsandbox me or no-go; good luck"

My first thought is some kind of system "request unsandbox" pop-up permission request that reloads the program if granted, but that's kind of a pain and smells like a lot of new development effort.

Allowing sandboxed programs to summon their own 'about' page via create_process would be a great compromise, imo. It's already rate-limited to prevent abuse; /system/apps/about.p64 just needs to be added to the create_process whitelist for sandboxed programs. Then, a program can prompt the user to uncheck 'sandboxed' on its own about page and offer to open that for the user to eliminate needing to pick the right cart out of a folder.

I'm sure updating an app's sandboxed status at runtime is a big ask, but if it was also capable of create_processing itself while sandboxed, it could at least reload itself and, should the user have unchecked the sandbox option, launch free of limitations. Since it's subject to the same rate limit, and would just launch itself sandboxed again if the user didn't allow it, its risk seems low.

Any thoughts?