[Bug] macOS notarization fails
See original GitHub issueMOVED FROM: https://github.com/microsoft/playwright-sharp/issues/1093
i’m using Playwright-Sharp in a macOS project which gets distributed to our customers. We use the apple notarization service to allow proper execution with gatekeeper enabled. Since i have added Playwright-Sharp to the project the notarization fails, because the added binaries are not properly signed and don’t have the hardened runtime
flag enabled. Here is a log of the apple notarization service:
{
"logFormatVersion": 1,
"jobId": "1234567890",
"status": "Invalid",
"statusSummary": "Archive contains critical validation errors",
"statusCode": 4000,
"archiveFilename": "MyApp.app.zip",
"uploadDate": "2021-01-09T14:54:20Z",
"sha256": "1234567890",
"ticketContents": null,
"issues": [
{
"severity": "error",
"code": null,
"path": "MyApp.app.zip/MyApp.app/Contents/MonoBundle/playwright-cli",
"message": "The binary is not signed.",
"docUrl": null,
"architecture": "x86_64"
},
{
"severity": "error",
"code": null,
"path": "MyApp.app.zip/MyApp.app/Contents/MonoBundle/playwright-cli",
"message": "The signature does not include a secure timestamp.",
"docUrl": null,
"architecture": "x86_64"
},
{
"severity": "error",
"code": null,
"path": "MyApp.app.zip/MyApp.app/Contents/MonoBundle/playwright-cli",
"message": "The executable does not have the hardened runtime enabled.",
"docUrl": null,
"architecture": "x86_64"
},
{
"severity": "error",
"code": null,
"path": "MyApp.app.zip/MyApp.app/Contents/MonoBundle/ffmpeg-mac",
"message": "The binary is not signed.",
"docUrl": null,
"architecture": "x86_64"
},
{
"severity": "error",
"code": null,
"path": "MyApp.app.zip/MyApp.app/Contents/MonoBundle/ffmpeg-mac",
"message": "The signature does not include a secure timestamp.",
"docUrl": null,
"architecture": "x86_64"
},
{
"severity": "error",
"code": null,
"path": "MyApp.app.zip/MyApp.app/Contents/MonoBundle/ffmpeg-mac",
"message": "The executable does not have the hardened runtime enabled.",
"docUrl": null,
"architecture": "x86_64"
}
]
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Resolving common notarization issues - Apple Developer
If you don't enable the hardened runtime, notarization fails and reports an issue with the following message: The executable does not have the...
Read more >Notarizing your macOS application - Unity - Manual
Notarization is a process where Apple verifies your application to make sure it has a Developer ID code signature and doesn't contain malicious...
Read more >Bug - macOS notarization: using new profile type "G2 Sub-CA ...
However, UCB notarization will fail with messages like: "Could not notarize package with message 'Package Invalid'"
Read more >macOS Notarization - RAD Studio - Embarcadero DocWiki
Warning: Notarization fails when an application is targeted for Developer ID compilation to a system with multiple providers. It also may fail when...
Read more >MacOS app notarization failed - The signature of the binary is ...
The solution is to create a new .entitlements file on the Mac by vim comand rathen than the above and it codesigns and...
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
@nor0x I’m working on that on the Sharp side. We should get something by the end of this week or early next week.
We are changing the way cli is packaged and trying to move away from pkg, so it may help with this issue too.