Can't no longer create macOS universal binary with @castlabs/electron-releases
See original GitHub issueI received this error when building macOS universal binary with @castlabs/electron-releases v15.2.0
Error: Expected all non-binary files to have identical SHAs when creating a universal build but "Contents/Frameworks/Electron Framework.framework/Versions/A/Resources/MainMenu.nib/keyedobjects-101300.nib" did not
I checked the path, Contents/Frameworks/Electron Framework.framework/Versions/A/Resources/MainMenu.nib
in the electron@15.2.0
and @castlabs/electron-releases@15.1.2
is a file but is a directory in @castlabs/electron-releases@15.2.0
with two files: keyedobjects.nib
and keyedobjects-101300.nib
.
Is there a way to fix this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:19
Top Results From Across the Web
Building a Universal macOS Binary
Create macOS apps and other executables that run natively on both Apple silicon and Intel-based Mac computers.
Read more >XCode 12.0.1 and 12.1 Do not build universal applications
I've had older Xcode-Projects that just wouldn't build universal binaries. It was due to a VALID_ARCHS user defined variable in one of the ......
Read more >Automated Malware Analysis Report for MolotovSetup-4.2. ...
File Type: UTF-8 Unicode text, with very long lines, with no line terminators. Size (bytes):, 2750. Entropy (8bit):, 4.264566206153985. Encrypted: false.
Read more >Links 07/10/2022: KaOS 2022.10 and EasyOS 4.4.1
When developers don't like something about a piece of software written on Linux, they often make their own version and release it free...
Read more >Brave Improves Its Ad-Blocker Performance with New ...
In practice, it follows chrome's release cycle very closely. Since brave is based on chromium, I don't see why this model can't work...
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 can confirm this was resolved in electron-builder 23.0.4. All good now.
@sulf, check this comment out. In short, the
.sig
files are VMP signatures and they are safe to remove before creating your universal build (they would be invalidated anyway, and you would need to use EVS to re-sign).Edit: Ideally some kind of mechanism for creating actions on a per file-type or path could be added to @electron/universal, which would allow easier handling of cases like this. I’ve been playing with some ideas around that but I’ve not had time to realize anything and submit a PR.