Code Signing error
-
HI!
Tried to sign a component file manually, though I get the error "bundle format unrecognized invalid or unsuitable"
Tried to find a search around for a solution though I can't seem to get any wiser.
Does anyone have any idea?ps. it has worked with other plugins though haven't tried since October 2022 ish.
(Mac Monterey 12.2 Xcode 13.2.1 Hise 2.1.0?)
-
@IsoWalle post the process that you're using for the signing process. That'll help figure out what's up.
-
@Dan-Korneff Just using codesign -s <dev-id> <path> in terminal
also tried --force and it did nothing
-
@IsoWalle Also add
--timestamp
-
@d-healey Still same...
-
@IsoWalle The command that is working for me is:
codesign --deep --force --options runtime --sign "Developer ID Application: Your Awesome Company (DEVELOPERID)" "/path/to/your/binary/or/package"
-
@Dan-Korneff Yep!
I realized i can't just use the dev-id code anymore, must use the whole name since i have a installer dev-id also with the same code...although now I'm getting "unknown file attribute: 5"
-
@Dan-Korneff Still not working.
I forgot the "" but it's still the same issue.
Someone said on another forum that it might have something to do with the resources folder and that it should not be created manually. -
@IsoWalle And I don't know for what reason (maybe a char code issue) it often works better if you type the whole line instead of copy/paste. Several people (like me) had the issue
-
@ustk said in Code Signing error:
@IsoWalle And I don't know for what reason (maybe a char code issue) it often works better if you type the whole line instead of copy/paste. Several people (like me) had the issue
yeah - this.
I have the same problem - so I always type out the entire notarize command . Seems to be fine for codesigning but notarize not so much.
-
Setup a bash script to automate it, then you never need to think about it again.
-
@d-healey That is what I need to learn as soon as I have 5min...
-
@ustk I posted a video and a bash script to Patreon (might have been 2 actually).
I modified my script the other day to pull down the latest HISE develop branch, build it, pull down the source for my project, and build that too. Then codesign, build and installer, and notarize. This way I don't have to transfer files between systems and manually rebuild HISE on my built machine. Just run the script and everything is taken care of.
I made a similar script for Windows and Linux. Windows was a bit of a pain because batch scripting lacks some of the nice string commands of bash, but I found solutions.
-
@Lindon said in Code Signing error:
I have the same problem - so I always type out the entire notarize command . Seems to be fine for codesigning but notarize not so much.
I copy and paste from a text document. No issues here.