Skip to content
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

PhantomJS error after upgrading to macOS Catalina - see solution here #79

Closed
kensoh opened this issue Oct 25, 2019 · 2 comments
Closed
Labels

Comments

@kensoh
Copy link
Member

kensoh commented Oct 25, 2019

After upgrading to macOS Catalina release, users may encounter a popup window saying that phantomjs is an unrecognised application downloaded from the internet. This is because Catalina release implements stricter security and access controls for applications running on macOS.

PS - PhantomJS is the execution engine for TagUI and is a critical component for TagUI to work.


I don't have a screenshot of the popup window anymore because I have fixed this on my laptop, it looks something similar to below image (for Terraform, another popular app that's also affected)
terraform

@kensoh kensoh added the query label Oct 25, 2019
@kensoh
Copy link
Member Author

kensoh commented Oct 25, 2019

  1. From macOS Finder, click Go menu, click Go to Folder..

  2. Enter /Users/username/.tagui/src/phantomjs/bin (replace username with your user name)

  3. Right-click phantomjs icon and click Open

  4. If a macOS prompt appears to ask whether to open the application because it is untrusted and downloaded from the internet, click Open to add the app to list of trusted apps.

  5. If you enter a PhantomJS terminal prompt, press Ctrl+C to exit.

  6. Try running TagUI for Python again and the popup warning message should disappear.

kensoh added a commit that referenced this issue Oct 30, 2019
see issues #78 and #79 for details showing how to address the tighter security controls
@kensoh
Copy link
Member Author

kensoh commented Oct 30, 2019

Updated to readme with a link to this solution, keeping issue open for time being before closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 participant