MacOS installer broken #95

Open
serge-rider opened this Issue Dec 7, 2015 · 13 comments

Projects

None yet

10 participants

@serge-rider
Owner
serge-rider commented Dec 7, 2015 edited

Due to some build/sign problem DBeaver can't be run on recent MacOS versions.
It fails with "damaged and can't be opened" error.
Possible workarounds:

@serge-rider serge-rider added the bug label Dec 7, 2015
@serge-rider serge-rider self-assigned this Dec 7, 2015
@serge-rider serge-rider changed the title from MacOS archive. to MacOS installer broken Dec 7, 2015
@ArloL
ArloL commented Feb 7, 2016

I am not sure if it helps but this is the result of spctl or codesign verification

$ spctl --assess DBeaver.app/
DBeaver.app/: invalid Info.plist (plist or signature have been modified)

$ codesign -v DBeaver.app/
DBeaver.app/: invalid Info.plist (plist or signature have been modified)
@NBOnGithub
NBOnGithub commented Jun 15, 2016 edited

Any chance of getting this fixed? - my company stops me selecting 'anywhere' on the preferences so I cannot install if the signature is not correct :-(
It is still happening on version 3.6.10

@serge-rider
Owner

You could try Homebrew (http://brew.sh/).
At the moment DBeaver doesn't have associated Apple developer ID (which costs money).

@NBOnGithub

That works perfectly. You can install either version with one of these commands
brew install Caskroom/cask/dbeaver-enterprise
brew install Caskroom/versions/dbeaver-community
Many thanks for the rapid reply.

@jgroves-hw

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.

@f-lima
f-lima commented Oct 12, 2016

My problem is not related with code sign. To force macOS Sierra open, it is easy as select Open from the pop-up menu (right-click with mouse). I have many apps installed that are not code signed and I open all without problem (like Meld and DBVisualizer) but DBeaver stopped to work when I tried to update and none of previous versions, not only the last one, can be installed because gives the error saying that file is corrupted. I think that is something related with the download manager used at site because I don't have this problem with any other site but DBeaver.

@ggiessen
ggiessen commented Nov 1, 2016

This works for me: xattr -rc /Applications/DBeaver.app

@cederom
cederom commented Nov 21, 2016 edited

the same here! xattr -rc /Applications/DBeaver.app solves the problem :-)

@g4brielvs

Try using Homebrew Cask for managing macOS applications from the command line!

brew install dbeaver-community

@serge-rider serge-rider added this to the 4.0 milestone Nov 21, 2016
@cederom
cederom commented Nov 21, 2016

I am using MacPorts :-) xattr fixed the problem for now so case closed thanks! :-)

@yhjhoo
yhjhoo commented Dec 11, 2016

The following works for me :

chmod +x /Applications/DBeaver.app/Contents/MacOS/dbeaver

@hgrod
hgrod commented Dec 20, 2016 edited

Note, this is for the .tar.gz archive, not the .dmg
My users were getting "DBeaver cannot be opened", with no further suggestions or details.
I had to both remove the extended attributes AND update the permissions with chmod.

The DBeaver.app was being installed without the proper permissions. For all my users, they needed to change their permissions to: drwxrwxr-x
I navigated to the Applications folder for the machines (not user's applications) and ran the following:

first remove the extended attributes
xattr -rc DBeaver.app
then recursively give permissions to all in all DBeaver folders, note this gives drwxrwxrwx not drwxrwxr-x. If you don't want ALL, please find the proper command for that.

sudo chmod -R uog+wxr DBeaver.app

@serge-rider
Owner

Problem with non-executable binary in MacOS tar.gz will be fixed in the next version.
Thanks for noticing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment