Pyautogui doesn't seem to work on macOS Mojave
See original GitHub issueI recently updated to macOS Mojave (10.14 Beta). Commands like pyautogui.moveTo(1027,73)
, pyautogui.click(1027,73)
, etc. don’t seem to work at all. Neither any error messages are thrown nor do the method calls work. pyautogui worked perfectly on macOS High Sierra.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:23
- Comments:19
Top Results From Across the Web
Why doesn't pyautogui hotkey work all of the time on mac?
Yeah it doesn't work when you move with touchpad or hold other keys. If you don't touch anything there will be no issues....
Read more >Can't run pyautogui on Mohave - Python Forum
Tried to search in Google, didn't find the solution. I have mac Mohave 10.14.6. Just installed Python 3.7.4 from Python org
Read more >PyAutoGUI trouble after Mac OSX 10.15 Catalina update
pyautogui.click() almost seems to work. Clicks work in the window that I tell it to, but it's as if immediately after a click,...
Read more >Spyder Ide - Pyautogui Not Working (Mac Catalina) - ADocLib
Re: Mac OS X Catalina install problems Has anyone found a similar solution for ReportWorks? ... Pyautogui doesn't seem to work on macOS...
Read more >QuickTip: How Do I Install pip on macOS or OS X?
Install pip for Python on macOS or OSX in one single command via command line. ... X as this doesn't work for Python...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not a pyautogui user, but on Mojave, there’s a new security feature where you must explicitly allow applications to use your mouse/keyboard. Have a look in Security Preferences > Security & Privacy > Privacy > Accessibility - you might have to allow your terminal application in the list.
@DimitriosLisenko You are right! This actually worked, personally I’m using iTerm so I had to add it in Accessibility as you described!