You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the mechanisms used to make sure that after an upgrade, chromedriver is still allowed to run without requiring to manually allow it in Settings is by setting the right label with spctl:
However, there isn't really an obvious way to check if the label is already placed on the executable (especially without annoying the user for Touch ID).
An idea could be to check if the checksum of the chromedriver installation has changed, and only then run the quarantine removal + spctl.
The text was updated successfully, but these errors were encountered:
One of the mechanisms used to make sure that after an upgrade,
chromedriver
is still allowed to run without requiring to manually allow it in Settings is by setting the right label withspctl
:However, there isn't really an obvious way to check if the label is already placed on the executable (especially without annoying the user for Touch ID).
An idea could be to check if the checksum of the chromedriver installation has changed, and only then run the quarantine removal + spctl.
The text was updated successfully, but these errors were encountered: