Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codesigning: "a sealed resource is missing or invalid", file modified in Squirrel framework #424

Closed
ccnokes opened this issue May 20, 2016 · 4 comments

Comments

@ccnokes
Copy link

ccnokes commented May 20, 2016

Mac OSX: 10.11.5
Electron: 0.37.8
electron-builder: 3.25.0

I just recently started having issues with codesigning. When I was on 3.16.0 and I ran this after building:

codesign --verbose=4 --deep --strict MyApp.app/

It would return:

MyApp.app/: a sealed resource is missing or invalid
In subcomponent: MyApp.app/Contents/Frameworks/Squirrel.framework
file modified: MyApp.app/Contents/Frameworks/Squirrel.framework/Versions/Current/Resources/ShipIt

After upgrading to 3.25.0, I don't get that error. Which is great, I'm a little curious as to why though...

Anyways, since upgrading, the main problem I'm dealing with is that when I download the .dmg from Chrome, it says: "This kind of file could harm your computer, do you want to download anyways?".

I don't know if this issue is even related to electron-builder, it was just my best first guess. Any help or guidance that you can offer would be much appreciated.

@develar
Copy link
Member

develar commented May 20, 2016

I will check Chrome. Please use RB App Checker Lite to verify that your app is correctly signed.

@ccnokes
Copy link
Author

ccnokes commented May 20, 2016

Thanks --- I'll add that Firefox and Safari work. RB App Checker doesn't let me drop dmgs on it, but it looks like my .app is ok. Do you want any output from it?

tmpethick added a commit to tmpethick/campusnet-electron that referenced this issue May 23, 2016
@ccnokes
Copy link
Author

ccnokes commented May 26, 2016

@develar thanks for looking into this, let me know if you've found anything. I went ahead and opened an issue on Chromium's issue tracker (https://bugs.chromium.org/p/chromium/issues/detail?id=614057#c2).

What I was mainly trying to find out with that Chromium ticket was if Chrome is using any underlying OSX services for it's security check. They explain it doesn't, so I guess the issue isn't directly related to electron-builder or even Mac OSX.

For the record, I still see the issue described in that Chromium issue, and I have no idea how they didn't see it after trying 20 times. ¯_(ツ)_/¯. My organization has decided that occasionally getting that flag in the Chrome UI isn't a show-stopper so we're just living with it.

Thanks for the great package!

@Ali-Albaker
Copy link

I am getting this error too electron version 19.0.4

In subcomponent: {APP}/Contents/Frameworks/Electron Framework.framework
{APP}/Contents/Frameworks/Electron Framework.framework/Versions/Current/Libraries/libEGL.dylib
{APP}/Contents/Frameworks/Electron Framework.framework/Versions/Current/Libraries/libvk_swiftshader.dylib
{APP}/Contents/Frameworks/Electron Framework.framework/Versions/Current/Libraries/libffmpeg.dylib
{APP}/Contents/Frameworks/Electron Framework.framework/Versions/Current/Libraries/libGLESv2.dylib

Where {APP} is the app directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants