Part of the RainforestQA service is that we run all tests in fresh VMs that we keep up-to-date, and to do this we want to automate as much of the VM build process as possible and we don’t want to babysit the build process to click “allow” when dialogs pop up.

TCC is an end-user protection feature, and tends to get in the way when you’re trying to provision machines in an automatic manner without user interaction. TCC also appears to exist and provide the same functionality on iOS, but in this post we’ll only be looking at TCC on macOS. TCC was introduced with OSX Mavericks and has gone through a number of changes since to expand what it has control over. This can include things such as location services, contacts, photos, microphone, camera, accessibility, full disk access, and a bunch more. TCC (Transparency, Consent, and Control) is a mechanism in macOS to limit and control application access to certain features, usually from a privacy perspective.

A deep dive into what the TCC database contains and the meaning of the various fields present in it.

Database for mac ios 2018