Hello,
I am looking for guidance on how to pre-provision TCC permissions for automated desktop app testing on the macOS 27 beta.
We have maintained a CI testing setup by saving snapshots of VMs with pre-configured user TCC databases. This allowed our UI tests to run without being blocked by permission prompts. This included permissions like screen recording, full disk access or apple events.
On the macOS 27 beta, this workflow appears completely broken. While the system TCC database seems to function as it used to, the user TCC database has been moved into a ProtectedSystem container. Direct modifications to the user database now seem impossible.
Is there any officially supported way to pre-provision user-level TCC permissions on macOS 27 VMs for automated CI environments? Is Apple's intention here that the system DB is the only one that's actually editable (with SIP disabled)?
How does Apple recommend CI platforms handle user-level permission prompts in headless or automated VM environments moving forward?
Any insights or recommended alternative workflows would be greatly appreciated. Thank you!