MacDownApp / MacDownApp/macdown
The latest 0.7.3 release has a 0 byte file at `./Contents/_CodeSignature` with 000 permissions
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 9.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
```
➜ 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: https://github.com/Homebrew/homebrew-cask/pull/75036
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect how MacDown.app.zip is packaged for the 0.7.3 release, using the reported ./Contents/_CodeSignature path and comparing it with the 0.7.2 archive. Done means the empty 000-permission file is absent or correctly packaged, and command-line unzip no longer creates the permission problem reported for Homebrew casks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100