“Dbeaver” is damaged and can’t be opened. You should move it to the Trash.
See original GitHub issueTried both .dmg and tar.gz version of 3.6.0, deleted the .dbeaver directory, but I’m still getting this error:
“Dbeaver” is damaged and can’t be opened. You should move it to the Trash.
If I run: spctl --asses DBeaver.app
I’ll get: DBeaver.app: invalid Info.plist (plist or signature have been modified)
I’m on iOS 10.11.3 (15D21)
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
“Dbeaver” is damaged and can't be opened. You should move ...
Cannot open DBeaver application after installing: “Dbeaver” is damaged and can't be opened. You should move it to the Trash.
Read more >Dbeaver is damaged and can't be opened, you should move ...
Dbeaver is damaged and can't be opened, you should move to trash, as per the error shown in Image – 1. This error...
Read more >Unable to open when running OS X
Hello, when I try and open DBeaver I'm prompted with: “Dbeaver” is damaged and can't be opened. You should move it to the...
Read more >Replace invalid code signature in Mac apps - adhocshare
Symptoms. MacOS gives messages like – “Dbeaver” is damaged and can't be opened. You should move it to the Trash.
Read more >Big Sur - Working / Not Working Apps | Page 46
First one just offered to chuck it in the trash as if I had just tried to ... DBeaver; Deepl; Devonthink; Dexcom Clarity...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had a similar issue and forcing the code sign wasn’t enough to resolve this issue:
So I’ve followed this: https://developer.apple.com/library/content/qa/qa1940/_index.html
And I have resolved the issue.
I resolved this by replacing the invalid code signature with a new one with the following command:
sudo codesign --force --sign - /Applications/DBeaver.app
OS X will then treat the app as a normal unsigned application and allow you to open it accordingly
The answer by user495470 in http://apple.stackexchange.com/questions/18306/fixing-a-sealed-resource-is-missing-or-invalid-warning lead me to this solution.