macOS notarization fails
See original GitHub issuei’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:12 (12 by maintainers)
Top Results From Across the Web
Notarization Issues | Apple Developer Forums
I'm having problems getting my app notarized with Apple from the new 'Release' version of XCode 10.0 (10A255) that came out today. 1....
Read more >MacOS app notarization failed - The signature of the binary ...
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 >Notarization fails on MacOS 10.15.3 · Issue #4656
We are trying to notarize our electron app, but the notarization is not working . It fails with the following issue :- "issues": ......
Read more >[Action required] Notarization fails because Cloud Build is ...
I've been having the same issue with notarized cloud builds for Mac even using Xcode 13.2.1. But eventually managed to solve it. As...
Read more >[Bug] macOS notarization fails #5193 - microsoft/playwright
MOVED FROM: microsoft/playwright-dotnet#1093 i'm using Playwright-Sharp in a macOS project which gets distributed to our customers.
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 Free
Top 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
sorry for the delay, i have build a repro project with a test that currently just checks for the existence of
Contents/MonoBundle/package/lib/cli/cli.js
within the macOS .app file. Currently i assume that everything that should live in the package directory is in the first level directly inContents/MonoBundle
.Here is the project which consists of a Xamarin.Forms project a Xamarin.Mac project and an mstest project. https://github.com/nor0x/playwright-xmac-test
this is a very similar project structure to the main application that i’m building which is closed source for now
@nor0x nothing to test here. But I’ll get here before 0.190.0.