-
...first system suggestion is to throw it away, since it is damaged... |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 6 replies
-
same for me |
Beta Was this translation helpful? Give feedback.
-
yeah, that's a know issue - can you try |
Beta Was this translation helpful? Give feedback.
-
As noted on #615, this issue seems to be different than what we had before - could be a result of the new packaging mechanism that v1.0.0 was created with (which is based on jpackage). It didn't happen on my machine though, which makes me think that in order to solve it we'll need to sign the application.. |
Beta Was this translation helpful? Give feedback.
-
Just to improve findability, I am posting the error message text here: “muCommander.app” is damaged and can’t be opened. |
Beta Was this translation helpful? Give feedback.
-
This is my work laptop and they don't give me sudo access. Is there any other workaround? I really want to try this app. Thanks |
Beta Was this translation helpful? Give feedback.
-
I didn't update the website yet but the artifacts, including the dmg, of v1.0.1 have been uploaded and the dmg is now signed and should not trigger this error anymore |
Beta Was this translation helpful? Give feedback.
-
I can confirm that v1.0.1 starts without error on my system. Thanks a lot for fixing this issue :) ! |
Beta Was this translation helpful? Give feedback.
-
With macOS 13.1 new method is required. #850 |
Beta Was this translation helpful? Give feedback.
yeah, that's a know issue - can you try
"sudo xattr -cr /Applications/muCommander.app"
?