Skip to content
This repository has been archived by the owner on Nov 14, 2024. It is now read-only.

[BUG] App does not open in macOS Monterey 12.0.1 on M1 Max #288

Open
drf-jpg opened this issue Oct 31, 2021 · 6 comments
Open

[BUG] App does not open in macOS Monterey 12.0.1 on M1 Max #288

drf-jpg opened this issue Oct 31, 2021 · 6 comments
Labels
bug Something isn't working

Comments

@drf-jpg
Copy link

drf-jpg commented Oct 31, 2021

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:

  1. Extract application using default archive utility in macOS
  2. Drag NineAnimator.app to Applications
  3. Run application
  4. Approve in security
  5. Run application a second time
  6. See error

Expected behavior
The application launches.

Screenshots
image

image

Device:
Replace the following with the device on which you're experiencing this issue.

  • Device: MacBook Pro (16-inch, 2021)
  • OS: macOS Monterey 12.0.1
  • Version: NineAnimator 1.2.7 Build 6 - April 25, 2021

Crash Log

default	08:39:15.244101-0700	runningboardd	Launch request for app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)> is using uid 501 (divined from auid 501 euid 501)
default	08:39:15.244160-0700	runningboardd	Acquiring assertion targeting app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)> from originator [daemon<com.apple.Finder(501)>:603] with description <RBSAssertionDescriptor| "LS launch maccatalyst.com.marcuszhou.NineAnimator" ID:386-603-5857 target:app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)> attributes:[
	<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"LaunchRoleUserInteractive" sourceEnvironment:"(null)">
	]>
default	08:39:15.244220-0700	runningboardd	Assertion 386-603-5857 (target:app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)>) will be created as active
default	08:39:15.244435-0700	runningboardd	Executing launch request for app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)> (LS launch maccatalyst.com.marcuszhou.NineAnimator)
default	08:39:15.244488-0700	runningboardd	Creating and launching job for: app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)>
default	08:39:15.244692-0700	runningboardd	_mutateContextIfNeeded called for maccatalyst.com.marcuszhou.NineAnimator
default	08:39:15.254926-0700	runningboardd	Invalidating assertion 386-603-5857 (target:app<application.maccatalyst.com.marcuszhou.NineAnimator.2184489.2184492(501)>) from originator [daemon<com.apple.Finder(501)>:603]
error	08:39:15.255151-0700	Finder	LAUNCH: RBSLaunchRequest FAILURE <private> maccatalyst.com.marcuszhou.NineAnimator <private> 0x0-0x66066 failed with error Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x600002eb7cf0 {Error Domain=NSPOSIXErrorDomain Code=153 "Unknown error: 153" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}
error	08:39:15.255176-0700	Finder	LAUNCH: Runningboard launch of maccatalyst.com.marcuszhou.NineAnimator <private> returned RBSRequestErrorFailed, error Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x600002eb7cf0 {Error Domain=NSPOSIXErrorDomain Code=153 "Unknown error: 153" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}, so returning -10810
default	08:39:15.254400-0700	kernel	ASP: Security policy would not allow process: 1359, /Applications/NineAnimator.app/Contents/MacOS/NineAnimator
error	08:39:15.255228-0700	Finder	LAUNCH: request execute thru runningboard of 0x0-0x66066 maccatalyst.com.marcuszhou.NineAnimator/<private> failed with error=Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x600002eb7cf0 {Error Domain=NSPOSIXErrorDomain Code=153 "Unknown error: 153" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}
error	08:39:15.266346-0700	CoreServicesUIAgent	handle LS launch error: {\n    Action = oapp;\n    AppMimimumSystemVersion = "10.15";\n    AppPath = "/Applications/NineAnimator.app";\n    ErrorCode = "-10810";\n}

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.

@drf-jpg drf-jpg added the bug Something isn't working label Oct 31, 2021
@Catta1997
Copy link
Contributor

Catta1997 commented Nov 5, 2021

Do you have Rosetta 2 installed?
Tray to lunch the app with terminal: /Applications/NineAnimator.app/Contents/MacOS/NineAnimator

@drf-jpg
Copy link
Author

drf-jpg commented Nov 5, 2021

Yes, I have Rosetta 2 installed.

If I use terminal to launch the application, I get the following error.

➜  ~ /Applications/NineAnimator.app/Contents/MacOS/NineAnimator
[1]    19529 killed     /Applications/NineAnimator.app/Contents/MacOS/NineAnimator

In Console, the follow error is raised when searching on "Nine":

default	12:48:22.302371-0700	kernel	ASP: Security policy would not allow process: 19600, /Applications/NineAnimator.app/Contents/MacOS/NineAnimator

@Catta1997
Copy link
Contributor

Try to select "open with rosetta" on the preference of NineAnimator.app

@Catta1997
Copy link
Contributor

Also, you are using the Nightly version or the realest version? If the release try to use the nightly version

@drf-jpg
Copy link
Author

drf-jpg commented Nov 6, 2021

Try to select "open with rosetta" on the preference of NineAnimator.app

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.

@gingerbeardman
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants