The latest 0.7.3 release has a 0 byte file at ./Contents/_CodeSignature with 000 permissions

[varenc]

➜  unzip -qq ./MacDown.app.zip
➜  ls -la MacDown.app/Contents/_CodeSignature
.--------- chris wheel 0 B Tue Jan  1 00:00:00 1980   _CodeSignature

That file is empty, so I think it doesn't need to be there? The previous 0.7.2 release didn't have a file at that path. But the reason this is causing issues is that the zip file seems to specify that that file has 000 permissions, not readable or writeable by anyone. When unzipped from the cli with unzip those permissions are preserved.

I noticed this because it's causing issues with homebrew casks. When the file is unzipped with macOS's built in "Archive Utility" the permission problem doesn't exist so probably not many people run into this.

For more context on the homebrew situation, I commented on an issue here: Homebrew/homebrew-cask#75036

[varenc]

possibly related commit? 7b93d1c

[FranklinYu]

That was a cherry-pick of 12e8a72 which is fixing #1106. I think I can fix this temporarily (maybe removing this file in build script) but it will probably in 0.7.4 because modifying current release sounds bad.

In addition, is there anyway to test whether this is the only bad file?

[varenc]

I think it's possible to update the current release's binary without changing the version...but agree that sounds risky.

I checked the latest release with these commands and that seems to be the only file with issues!

➜  wget -q https://github.com/MacDownApp/macdown/releases/download/v0.7.3/MacDown.app.zip
➜  unzip -qq ./MacDown.app.zip
➜  find ./MacDown.app \! -perm -u=r
./MacDown.app/Contents/_CodeSignature
➜  

[varenc]

Though something more helpful for your release build script...when looping through each file to create the .zip, you could assert os.access(<path>, os.R_OK)

example:

In [13]: os.access("./MacDown.app/Contents/_CodeSignature",os.R_OK)
Out[13]: False
In [14]: os.access("./MacDown.app/Contents/Info.plist",os.R_OK)
Out[14]: True

[CITguy]

Is this the reason why I get the following error?

I ask because my system is managed by my company with the following settings (cannot change):

System Preferences > Security & Privacy > General

[FranklinYu]

@CITguy No, it's unrelated. Please checkout FAQ.

I think I'll update the page with updated information for Mojave, since the current solution is to right-click the app to open.

[FranklinYu]

0.8.0d71 is released and should be good. Waiting for Homebrew to try it out before I backport the fix to stable branch.