Apple Juice.app is damaged and ca't be opened.
romanrehacek opened this issue · 34 comments
Hi,
after failed update to latest version, I uninstalled an app and try to install latest version, but after install and open an app, I get "Apple Juice.app is damaged and ca't be opened. You should move it to the Trash" message.
I tryed brew and dmg installation.
I have latest Mac os.
Facing the update issue myself (v1.9 to v1.10, still on former for now):
same issue here
Same
Thanks for reporting the issue. 👍
It seems I configured the App Sandbox for the last version wrong, which prevents Apple Juice from accessing the filesystem therefore preventing the installation of the update. The only solution I currently have is manually installing the latest version (with the updated Sandbox configuration).
The solution you offered did not work for me.
MacOS Mojave 10.14.5
What's the problem? Is it still saying "Apple Juice.app is damaged and ca't be opened. You should move it to the Trash"?
EDIT: I've uploaded a zipped version of 1.10.1, maybe that works for you
Still getting "damaged" error from DMG and ZIP files
After receiving this error, I was able to go back to version 1.8.1 (downloaded the DMG for that version). This version is working, but 1.10.0 and 1.10.1 are not.
Did you disable Gatekeeper? Under System Preferences: Security & Privacy:
This setting doesn't seem to exist any longer?
It exists but it's hidden and disabled by default. You can display it with the following command: sudo spctl --master-disable. OSXDaily have a great step by step guide.
Closing this due to inactivity. Seems to me disabling Gatekeeper and the new Apple Juice version fixed the issue.
Hi @raphaelhanneken,
I am waiting for you to fix this issue.
I have disabled Gatekeeper. I downloaded latest release dmg file. I have latest mac os Mojave.
After moved app file to Application folder and opened, I get the same error "“Apple Juice.app” is damaged and can’t be opened."
Still not working.
Ok, @jvimedia @romanrehacek can you send me some logs, so I can see what's happening when the update process fails?
I have this problem with install new version. Not with update the old one. I uninstalled the old version after update process failed. Now I am trying fresh install the latest version.
Fresh download shows same issue on 10.14 and 10.15.
having the same issue Mac 10.14
Sorry, I can't reproduce the issue and without some logs I can't really do anything. The latest releases all work on my machines.
i got it working. it is a permission issue :
sudo spctl --master-disable
Does this help? https://gist.github.com/WardsParadox/8e18d1265f2f39ae985a55239445dc10
This occurs when launching. If you have a way to get the logs you are seeking, let me know and I'll get them for you.
Hi @WardsParadox thank you very, very much! That is exactly what I wanted, hopefully I'm going to find some useful information. I'll look though this as soon as I can 👍
No problemo, I actually couldn't get much other than launch notices on 10.14, but on 10.15 I get that output so hopefully that's more. If you need additional, let me know.
It seems like the Launch at Login Framework is causing some problems; I've released a version without Launch at Login feature. Could someone please verify whether this solves the problem? Thanks!
Hello @raphaelhanneken
I've been subscribed to the issue since day 1 because it also affected me.
I confirm that version 1.10.2 works fine on MacOS 10.14.6 (18G95) while 1.10.1 appeared corrupted.
@raphaelhanneken I can confirm that new version works. I can run it.
Confirming to work but will need to be signed, notarized and stapled for 10.15+
That's awesome! Thanks again @WardsParadox for the logs - never would have guessed the Launch at Login is causing this. 🤔
Confirming to work but will need to be signed, notarized and stapled for 10.15+
Does that mean no unsigned Software will be able to run on 10.15? Not even with Gate Keeper disabled?
It will be able to run with an override (ie: right click) or by a root agent installer (such as Munki or Jamf), but as for the future...pretty sure Apple is making it clear.
https://developer.apple.com/news/?id=09032019a
If it's signed, notarized (with the notarization ticket stapled), the app can be pretty much fully whitelisted by Apple's gatekeeper process as it's already been scanned for malicious activity.
You can also use xattr -cr /path/to/application.app to make sure the attributes are re-written
You can also use
xattr -cr /path/to/application.appto make sure the attributes are re-written
This actually did the trick for me with the most recent release (2020.11.2). Thanks!
xattr -cr '/Applications/Apple Juice.app'
i got it working. it is a permission issue :
sudo spctl --master-disable
solved!