macOS Sierra - how to enable "Allow Remote Automation" using command line

Question

I am working on an automation stuff in macOS Sierra (10.12.2). By using python's atomac support I can launch the safari browser and make the settings enabled via Safari -> Preferences -> Advanced -> check "enable Develop Menu" and then select "Develop -> Allow Remote Automation". Looks like this is not so consistent for automation perspective. I would like to know if there is any shell command to make this possible.

Answer 1

I found the answer from: https://developer.apple.com/documentation/webkit/testing_with_webdriver_in_safari

safaridriver --enable

It will prompt for an admin password, so some people setup passwordless sudo (dangerous) or do another workaround like calling from an Applescript

I tested that this works with Mojave and Safari 12.0.3 and verified that it works regardless of if the Develop menu is enabled, though you probably want to save yourself the clicks and just enable that too:

defaults write com.apple.Safari IncludeDevelopMenu 1

Answer 2

On MacBook Pro (Apple M2 Pro) ▪ select Safari ▪ Select Setting ▪ Select “Advanced” tab ▪ Check “Show features for web developers” ▪ Now you see “develop” option is on the MacOS menu ⁃ select develop ⁃ Select “Developer settings…” ⁃ check “Allow remote automation” Now you can run your tests against safari

Answer 3

Hmm ok, so as per my comment:

You could do defaults write com.apple.Safari IncludeDevelopMenu YES to activate the development menu via terminal. You could get python to execute this command for you using the subprocess module.

According to this this question it seems that one used to be able to simply do defaults write com.apple.Safari AllowRemoteAutomation 1. However, since Safari 10 this option has apparently been subjected to a higher security protocol or something (maybe because of the System Integrity Protection that was introduced). I've been looking for the plistfile that now holds the setting, but I have not been able to find it. Maybe it's not even there in an actual plistfile anymore.

I guess this leaves you with 2 options:

1. Use apple's osascript to simulate the needed mouseclicks.
2. Repost your question on AskDifferent or Apple's own developers forum, since you are more likely to find someone with in-depth knowledge of macOS.