Opened 4 years ago

Last modified 4 years ago

#10737 reopened Bug report

“FileZilla.app” is damaged and can’t be opened.

Reported by: LordChaos Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: OS X
Operating system version:

Description

When I try to start FileZilla 3.15 I get the following error:

“FileZilla.app” is damaged and can’t be opened. You should move it to the Trash.

OS: OSX 10.11.3

➜ ~ shasum -a 256 Downloads/FileZilla_3.15.0_macosx-x86.app.tar.bz2
05372ae7f8e88bcb7a9514a288ca2afbab25960fb538278c6c75b606ad8cc2ff Downloads/FileZilla_3.15.0_macosx-x86.app.tar.bz2

I've downloaded the file multiple times from different sources, result is the same.

Attachments (1)

filezilla.png (42.0 KB) - added by LordChaos 4 years ago.

Download all attachments as: .zip

Change History (13)

Changed 4 years ago by LordChaos

Attachment: filezilla.png added

comment:1 Changed 4 years ago by Tim Kosse

Priority: criticalnormal
Resolution: worksforme
Status: newclosed

That's the correct hash, the file isn't damaged.

The error message you are seeing can be the result of the App Store certificates being outdated. In that case, please first try rebooting your Mac. If the issue persists, open the App Store and sign out, then sign back in. Next check that there are no pending updates.

comment:2 Changed 4 years ago by LordChaos

I have done the following now:

  • Signed out of the App Store and back in
  • rebooted the macbook

(there are no pending updates)

Issue still persists. 3.14 works fine by the way.

comment:3 Changed 4 years ago by LordChaos

Resolution: worksforme
Status: closedreopened

comment:4 Changed 4 years ago by LordChaos

Now here's in something funny; when I start the app from a shell it works fine but when I double click on it's icon I get the error message.

comment:5 Changed 4 years ago by Tim Kosse

That's weird. I have no idea what might cause this.

comment:6 Changed 4 years ago by Tim Kosse

Status: reopenedmoreinfo_reopened

comment:7 Changed 4 years ago by LordChaos

Status: moreinfo_reopenedreopened

Beta1 works fine; rc1 doesn't. Same error message again!

comment:8 Changed 4 years ago by Tim Kosse

Status: reopenedmoreinfo_reopened

What does the following command print if you execute it from a Terminal? Adjust the path as needed:

codesign --verify -v /Users/myusername/Downloads/FileZilla.app

comment:9 Changed 4 years ago by LordChaos

Status: moreinfo_reopenedreopened

➜ ~ shasum -a 512 Downloads/FileZilla_3.15.0.1_macosx-x86.app.tar.bz2
96e5b2aff08f502fb7962beee400371d945210cdc0230093f083f7334ade35eda33aff0047fc72f45f269acc861cc0c8c1fd1e0fb68883bef1c4a1a746533407 Downloads/FileZilla_3.15.0.1_macosx-x86.app.tar.bz2

➜ ~ codesign --verify -v Downloads/FileZilla.app
Downloads/FileZilla.app: invalid signature (code or signature have been modified)
In subcomponent: /Users/ericd/Downloads/FileZilla.app/Contents/COPYING

comment:10 Changed 4 years ago by Tim Kosse

Status: reopenedmoreinfo_reopened

That's most interesting. The contents or location of COPYING hasn't changed since previous versions, yet not it doesn't validate anymore.

Please try this build: https://filezilla-project.org/codesquid/temp/FileZilla3.app.tar.bz2

The only difference is that COPYING has been moved into the Contents/SharedSupport directory.

If it still does not work, please run the codesign command again on this test build.

comment:11 Changed 4 years ago by LordChaos

Status: moreinfo_reopenedreopened

➜ Downloads shasum -a 512 FileZilla3.app.tar.bz2
f27f48de972d07c53bdfea8c916b25002e457988f7af15cb1d9add1e6b5baa07f9a7009faa8de514dfa9aad4a56ce2ffe3b4ab0d29ae2447c0bd4821d902bc7e FileZilla3.app.tar.bz2

➜ Downloads codesign --verify -v FileZilla.app
FileZilla.app: valid on disk
FileZilla.app: satisfies its Designated Requirement

comment:12 Changed 4 years ago by glaksmono

I'm also experiencing this issue, but that build worked: https://filezilla-project.org/codesquid/temp/FileZilla3.app.tar.bz2

Note: See TracTickets for help on using tickets.