You have to make sure it actually does say “Timestamp” and not just “Time&Date” or similar. Sealed Resources version=2 rules=13 files=2 You should get back something similar to: (base) Martins-MBP:signing martin$ codesign -dvv MyPlugin.vst3Įxecutable=/Users/martin/Programming/Audio/signing/MyPlugin.vst3/Contents/MacOS/MyPluginĬodeDirectory v=20500 size=87871 flags=0x10000(runtime) hashes=2737+5 location=embeddedĪuthority=Developer ID Application: MY COMPANY LLC (G56E7125MX)Īuthority=Developer ID Certification Authority It is then going to show you the code signing. What happens when you enter the following into a terminal window ?: “severity”: “error”, “code”: null, “path”: “plug-package.pkg/VST3.pkg Contents/Payload/Library/Audio/Plug-Ins/VST3/plug.vst3/Contents/MacOS/plug”, “message”: “The binary is not signed.”, “docUrl”: null, “architecture”: “x86_64” I have signed the package once compiled and then I submit for notarization but I keep getting these errors. My understanding is that Xcode should sign the binaries. I set Code Signing Injection Entitlements to No and Code Signing Style is set to Manual in Xcode. “The signature does not include a secure timestamp.” - I tried the method above adding the -timestamp flag into the Other Code Signing Flags in Xcode but no dice. Code signing configuration is set to a valid and up-to-date developer certificate from Apple. “The binary is not signed.” - which doesn’t make any sense. I just upgraded to the latest version of Xcode and I am getting the following rejection notices when I submit a signed audio plugin package made using Packages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |