Post

Replies

Boosts

Views

Activity

New issue with notarization - included 3rd party binary in package
Up until today our notarization process was working fine. Please note this is for an application developed using Xamarin for Mac, so I don't use Xcode-based notarization, rather a command-line process. Within our application we package 'wkhtmltopdf' to generate PDFs, and now it looks like this is causing an issue. Attempting to notarize now causes an issue, and the pertinent parts of the log file are like so: 		{ 			"severity": "error", 			"code": null, 			"path": "OURAPP.zip/OURAPP.app/Contents/Resources/Util/wkhtmltopdf", 			"message": "The binary is not signed.", 			"docUrl": null, 			"architecture": "x86_64" 		}, 		{ 			"severity": "error", 			"code": null, 			"path": "OURAPP.zip/OURAPP.app/Contents/Resources/Util/wkhtmltopdf", 			"message": "The signature does not include a secure timestamp.", 			"docUrl": null, 			"architecture": "x86_64" 		}, 		{ 			"severity": "error", 			"code": null, 			"path": "OURAPP.zip/OUR.app/Contents/Resources/Util/wkhtmltopdf", 			"message": "The executable does not have the hardened runtime enabled.", 			"docUrl": null, 			"architecture": "x86_64" 		} 	] Frankly, I'm not sure where to go from here. It looks to me as though I need to build and sign the wkhtmltopdf binary with our Developer ID - ? Any advice would be appreciate, thanks!
3
0
629
Jul ’20