Invalid Signature - The nested app bundle Electron Framework
See original GitHub issueHi,
I try to sign my app with electron builder, with my package.json :
{
"scripts": {
"start": "electron ./app --enable-logging",
"dev": "NODE_ENV='development' npm run start",
"dist": "npm run dist:osx",
"dist:osx": "build --platform darwin"
},
"devDependencies": {
"gulp": "~3.9.0",
"gulp-concat": "~2.6.0",
"gulp-rename": "~1.2.0",
"gulp-uglify": "~1.5.0",
"gulp-sass": "~2.3.1",
"gulp-sourcemaps": "~1.6.0",
"gulp-cssnano": "~2.1.0",
"electron-builder": "3.23.0",
"electron-prebuilt": "1.1.0"
},
"build": {
"productName": "MyApp",
"app-bundle-id": "com.myapp",
"app-category-type": "public.app-category.productivity",
"osx": {
"title": "MyApp",
"background": "build/background.png",
"icon": "build/icon.icns",
"icon-size": 128,
"target": "mas",
"identity": "Developer ID Application: Jeremie Chazelle (XXXXXXXXX)",
"contents": [
{
"x": 355,
"y": 125,
"type": "link",
"path": "/Applications"
},
{
"x": 155,
"y": 125,
"type": "file"
}
]
},
"mas": {
"identity": "Jeremie Chazelle"
}
}
}
I done this tutoriel https://github.com/nwjs/nw.js/wiki/MAS%3A-Requesting-certificates to make the certificates
I launch the build and sign with
sudo npm run-script dist
pc3:my-app jeremiechazelle$ sudo npm run-script dist
> @ dist /Users/jeremiechazelle/Sites/my-app
> npm run dist:osx
> @ dist:osx /Users/jeremiechazelle/Sites/my-app
> build --platform darwin
Rebuilding app dependencies for arch x64 to /Users/jeremiechazelle/Sites/my-app/app
Packaging app for platform mas x64 using electron v1.1.0
Signing app (identity: Developer ID Application: Jeremie Chazelle (XXXXXXXXXX))
pc3:my-app jeremiechazelle$
With Application Loader, I upload my app. The upload it’s done
But, after 30 secondes, I have an email from Apple
Dear developer,
We have discovered one or more issues with your recent delivery for "MyApp". To process your delivery, the following issues must be corrected:
Invalid Signature - ...
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
I don’t understand what I’m missing…
Issue Analytics
- State:
- Created 7 years ago
- Comments:77 (47 by maintainers)
Top Results From Across the Web
Invalid Code Signature Error on El… | Apple Developer Forums
I codesign via commandline using xcode 10.1 on Mac OS X 10.14.1. I've tried reducing the application down to the bare Electron startup,...
Read more >Submitting Electron App to Mac App Store: Error "Invalid ...
Invalid Signature - This error occurs when you have signed your app's installer incorrectly. There are two certs required for this process: the...
Read more >Code Signing | Electron
Generate, download, and install signing certificates. Electron's ecosystem favors configuration and freedom, so there are multiple ways to get your application ...
Read more >Submitting Electron App To Mac App Store: Error "Invalid - ADocLib
And here's message: Invalid Signature The nested app bundle Electron Framework at path MockingBot.app/Contents/Frameworks/Electron Framework.
Read more >Publish - electron-builder
snap target by default publishes to snap store (the app store for Linux). To force publishing to another providers, explicitly specify publish configuration ......
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
@jechazelle If wish to add options, you may use the following for signing and packing. Note the two dashes
--
before stating each param.Additionally,
export DEBUG=electron-osx-sign*
before signing should give extra debug logs.@sethlu @develar @mcfedr Thanks a lot for you help!! 👍
I would like to generate my build only to MAS (iTC)
'please don't specify identity in the package.json, it is recommended to use only env.'
I read your comments, So, I don’t declare identity in my package.json, only with env var
package.json
and I set env var
it’s correct ?