-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Noteworthy change in 10.9 Permissions #110
Comments
Confirmed. Steps (feel free to add this to your README):
Thanks for making such a useful tool! --Seth |
Hi, Would you mind adding this to the readme file in the develop branch. - I think just a link to your comment to this issue will be enough. Thanks! |
Thanks a lot! Merged |
There is some way to escalate this without the user having to check the box. I'm not sure how but it works in HyperDock with just a password http://hyperdock.bahoom.com/ |
Try this ;) |
I saw this hack (used by divvy installer). It is definitely one option, however, there is a proper one - using an auxiliary app that asks for root permissions to mark shiftit app as AX trusted. I'll try to do this asap (finally on mavericks :-) ) |
I had to use slightly different SQL to get it to work: sqlite3 '/Library/Application Support/com.apple.TCC/TCC.db' 'update access set allowed=1 where client like "%org.shiftitapp.ShiftIt%"' Note:
|
Can you please make a Retina ready icon? That would be great! |
Thanks Tim! Very helpful. |
After upgrading to 10.10, I had to uncheck the checkbox and re-check it again. Then I could run the app. |
Thank you for that comment @lookfirst . Same here, uncheck and then check again, then it works. |
@lookfirst Would you mind putting this in the readme.md? Thanks! |
The 10.9 dev preview changes the way you must enable permissions to use this app. Previously, one needed to go into Accessibility settings and enable assistive devices, now you must go into Security + Privacy settings and add ShiftIt to the list of devices allowed to access Accessibility
The text was updated successfully, but these errors were encountered: