-
Notifications
You must be signed in to change notification settings - Fork 99
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
[BUG] App does not open in macOS Monterey 12.0.1 on M1 Max #288
Comments
Do you have Rosetta 2 installed? |
Yes, I have Rosetta 2 installed. If I use terminal to launch the application, I get the following error.
In Console, the follow error is raised when searching on "Nine":
|
Try to select "open with rosetta" on the preference of NineAnimator.app |
Also, you are using the Nightly version or the realest version? If the release try to use the nightly version |
This worked. I didn't try to run the nightly; I got some package resolution errors when building. It's strange that Rosetta isn't selected by default for this application if it's an Intel binary. Not sure if I should close this issue if this requires some kind of bug fix in the latest "stable" release. |
I recommend checking SIP. If SIP is set to Permissive then in some situations apps will fail to launch and there will be no visual error message other than cryptic console logs. SIP needs to be on Full or Reduced. |
Describe the bug
See Screenshots. I get an error pop-up saying "The application NineAnimator cannot be opened" with no further information.
This occurs after the application has been manually allowed through Security & Preferences.
To Reproduce
Replace this with the steps to reproduce the behavior:
Expected behavior
The application launches.
Screenshots
Device:
Replace the following with the device on which you're experiencing this issue.
Crash Log
Additional context
Looking at the crash log, it looks like macOS Monterey is refusing to launch it because of a security policy issue. This is despite allowing the application through security settings.
The text was updated successfully, but these errors were encountered: