Search results for

“codesign”

3,222 results found

Post

Replies

Boosts

Views

Activity

can't codesign the .app file using Visual Studio for Mac
I'm developing a C sharp application in Visual Studio for Mac. I have it set up to be signed with a developer ID signature to get it notarized by Apple. But it's not working. Here are the steps. (1). Sign the code using Visual Studio for Mac. (2). However, this .app file will crash. (3). When I create a dmg and request notarization with the xcrun altool command, I get the following error. { tlogFormatVersion: 1, tjobId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, tstatus: Invalid, tstatusSummary: Archive contains critical validation errors, tstatusCode: 4000, tarchiveFilename: MyApp.dmg, tuploadDate: 2020-08-18T08:29:55Z, tsha256: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, tticketContents: null, tissues: [ tt{ tttseverity: error, tttcode: null, tttpath: MyApp.dmg/MyApp.app/Contents/MonoBundle/SQLite.Interop.dll, tttmessage: The signature of the binary is invalid., tttdocUrl: null, tttarchitecture: x86_64 tt} t] } Even if this succeeds, it won't matter because it will crash... Thi
Topic: App & System Services SubTopic: Core OS Tags:
8
0
2.0k
Sep ’20
Codesign causes the app to not run properly
I signed my application in MacOS 13.4, and the signed objects include all the binary files I compiled myself, and notarizing also works. It can also run normally on my version 13.4 Mac. However, when I copied this application to a computer with Mac OS version 11.3, it couldn't run properly. Dlopen will generate an error message, indicating that some of the dynamic libraries called by the program do not match the signature of the program itself. These dynamic libraries are from JRE, so I re-signed them and notarizing also works. In MacOS 13.4, it still runs normally, but in MacOS 11.3, it will report another error: Error occurred during initialization of VM Could not reserve enough space for code cache What is the reason for this and how should I handle it? Thank you in advance for any comments on this issue.
Topic: Code Signing SubTopic: Notarization Tags:
1
0
754
Oct ’23
"No identity found" error when codesigning app
I keep getting this error despite having installed new certificates. I have 3rd Party Mac Developer Application, AddTrust External CA Root, Apple Application Inegration Certification Authority, Developer ID Application, Apple Worldwide Developer Relations Certification Authority, Developer ID Application, Developer ID Certification Authority, Developer ID Installer and some others. Why does it give me this error?
Topic: Code Signing SubTopic: General Tags:
9
0
27k
Aug ’17
Reply to Code signature validation failed fatally
It’s likely that your code signature is simply borked. Try this: % codesign --verify -vvv --strict --deep /path/to/your.app Note that using --deep in a --verify operation is just fine (-: The most common cause of this problem for frameworks is folks copying the framework using cp -r, which doesn’t preserve symlinks. And below is my codesign order Hmmm… codesign -s Developer ID Application --options=runtime,library --timestamp -f ***.app/Contents/Resources/*** ***.driver This is a worry. Presumably this .driver bundle contains code, which means it shouldn’t be in the Resources directory. See Placing Content in a Bundle. codesign -s Developer ID Application --options=runtime,library --timestamp -f ***.app/Contents/Resources/***/***.app/Contents/MacOS/*** I’m presuming that’s this is some sort of helper tool rather than the main executable for the containing .app. codesign -s Developer ID Application --options=runtime,library --timestamp -f ***.app/Contents/Resources/
Topic: App & System Services SubTopic: Core OS Tags:
May ’23
Reply to application-identifier error when submitting re-signed app
If anyone faces the same issue just as I did in 2023. This was the solution that finally resolved it. Framework has to be signed along with the app if you are going to use different signer codesign -f -s Distribution Certificate Name MyApp.app/Frameworks/* then sign the app again codesign -f -s Distribution Certificate Name MyApp.app https://gist.github.com/chaitanyagupta/9a2a13f0a3e6755192f7?permalink_comment_id=1812865#gistcomment-1812865
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Oct ’23
Reply to "Application damaged and can't be opened' error prompt on 15.6.1 Sequoia
[quote='873484022, oddeyed, /thread/799110?answerId=873484022#873484022, /profile/oddeyed'] My application currently requires elevated privileges or “sudo” to verify the codesign … [/quote] Lemme see if I understand this correctly: You take a Mac that’s never seen your app before. You install your app in the standard way that a user would install it. This command fails: % codesign --verify --deep --strict /path/to/your.app Instead you have to do this: % sudo codesign --verify --deep --strict /path/to/your.app Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General Tags:
Jan ’26
Reply to App is damaged and can't be opened, despite being codesigned
I am indeed running it through the Terminal, not Finder. Wouldn't Gatekeeper block the application regardless of where it's being launched from? Well, it should, but it doesn’t, which is why we consider it a bug (r. 58097824)-: code has no resources but signature indicates they must be present Consider this sequence: % cp /usr/bin/true MyTrue % codesign -s - -f MyTrue MyTrue: replacing existing signature % codesign -d -v MyTrue … Format=Mach-O universal (x86_64 arm64e) … I make a copy of the true command and re-sign it. When I dump the signature, codesign shows the Format property as a plain Mach-O. Now let’s put this in an app wrapper and re-sign: % mkdir -p MyTrue.app/Contents/MacOS % mv MyTrue MyTrue.app/Contents/MacOS/ % codesign -s - -f MyTrue.app MyTrue.app: replacing existing signature % codesign -d -v MyTrue.app … Format=bundle with Mach-O universal (x86_64 arm64e) … Here codesign has detected the app wrapper and signed the code as a bundle. Note h
Topic: Code Signing SubTopic: General Tags:
Nov ’23
Reply to How to app distribution for Mac
Feel free to ignore the comments I left above. The case is an error with the extension app, and it is considered normal, not an error with the actual app. I also encountered the following problem: I've read all the documentation to fix the issue, but I can't confirm any idea why this is happening? Case 1 I had an existing Apple Development signed app for distribution. Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/embedded.provisionprofile Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension/Contents/embedded.provisionprofile However, in order to distribute the a
Topic: App & System Services SubTopic: Core OS Tags:
Feb ’22
Reply to Notarization started failing this week
Thanks to everyone for your feedback. After reading your posts and following your links, I was able to figure it out. It turns out the fault was mine. (1) I did not have the necessary certificate, and (2) I had to do a manual codesign with the new certificateBefore when I did a codesign -dvvvv I could see that the binary was signed, but the Apple Development signing certificate (line 3 below) was not sufficient.$ codesign -dvvv --entitlements :- /tmp/helloworld.dst/usr/local/bin/helloworld ... Authority=Apple Development: XXXXXX (XXXXXXXXXX)After requesting and getting a Developer ID Application certificate, and then manually signing the binary with that, notarization started working for me again.$ codesign -s Developer ID Application: XXXXXXXX (XXXXXXXXXX) --options=runtime --force /tmp/helloworld.dst/usr/local/bin/helloworldcodesign -dvvv --entitlements :- /tmp/helloworld.dst/usr/local/bin/helloworld ... Authority=Developer ID Application: XXXXXXX (XXXXXXXXXX)So if the Au
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Feb ’20
Reply to Error: Failed with Exit Code 1
Fixed it. I did Option - Command - Shift - K, which led to another Error: Command CodeSign failed with a nonzero exit code. I Googled that which led a StackOverflow page:https://stackoverflow.com/questions/52421999/xcode-10-command-codesign-failed-with-a-nonzero-exit-codeIt had instructions on resetting my Keychain Access. Thanks for the help.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Aug ’19
Reply to App crashes in AppStore-Mode
In the meantime, I found out that the problem is caused by codesign. but still no idea, why ..
Topic: Code Signing SubTopic: General
Replies
Boosts
Views
Activity
Aug ’24
can't codesign the .app file using Visual Studio for Mac
I'm developing a C sharp application in Visual Studio for Mac. I have it set up to be signed with a developer ID signature to get it notarized by Apple. But it's not working. Here are the steps. (1). Sign the code using Visual Studio for Mac. (2). However, this .app file will crash. (3). When I create a dmg and request notarization with the xcrun altool command, I get the following error. { tlogFormatVersion: 1, tjobId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, tstatus: Invalid, tstatusSummary: Archive contains critical validation errors, tstatusCode: 4000, tarchiveFilename: MyApp.dmg, tuploadDate: 2020-08-18T08:29:55Z, tsha256: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, tticketContents: null, tissues: [ tt{ tttseverity: error, tttcode: null, tttpath: MyApp.dmg/MyApp.app/Contents/MonoBundle/SQLite.Interop.dll, tttmessage: The signature of the binary is invalid., tttdocUrl: null, tttarchitecture: x86_64 tt} t] } Even if this succeeds, it won't matter because it will crash... Thi
Topic: App & System Services SubTopic: Core OS Tags:
Replies
8
Boosts
0
Views
2.0k
Activity
Sep ’20
Codesign causes the app to not run properly
I signed my application in MacOS 13.4, and the signed objects include all the binary files I compiled myself, and notarizing also works. It can also run normally on my version 13.4 Mac. However, when I copied this application to a computer with Mac OS version 11.3, it couldn't run properly. Dlopen will generate an error message, indicating that some of the dynamic libraries called by the program do not match the signature of the program itself. These dynamic libraries are from JRE, so I re-signed them and notarizing also works. In MacOS 13.4, it still runs normally, but in MacOS 11.3, it will report another error: Error occurred during initialization of VM Could not reserve enough space for code cache What is the reason for this and how should I handle it? Thank you in advance for any comments on this issue.
Topic: Code Signing SubTopic: Notarization Tags:
Replies
1
Boosts
0
Views
754
Activity
Oct ’23
"No identity found" error when codesigning app
I keep getting this error despite having installed new certificates. I have 3rd Party Mac Developer Application, AddTrust External CA Root, Apple Application Inegration Certification Authority, Developer ID Application, Apple Worldwide Developer Relations Certification Authority, Developer ID Application, Developer ID Certification Authority, Developer ID Installer and some others. Why does it give me this error?
Topic: Code Signing SubTopic: General Tags:
Replies
9
Boosts
0
Views
27k
Activity
Aug ’17
Reply to Code signature validation failed fatally
It’s likely that your code signature is simply borked. Try this: % codesign --verify -vvv --strict --deep /path/to/your.app Note that using --deep in a --verify operation is just fine (-: The most common cause of this problem for frameworks is folks copying the framework using cp -r, which doesn’t preserve symlinks. And below is my codesign order Hmmm… codesign -s Developer ID Application --options=runtime,library --timestamp -f ***.app/Contents/Resources/*** ***.driver This is a worry. Presumably this .driver bundle contains code, which means it shouldn’t be in the Resources directory. See Placing Content in a Bundle. codesign -s Developer ID Application --options=runtime,library --timestamp -f ***.app/Contents/Resources/***/***.app/Contents/MacOS/*** I’m presuming that’s this is some sort of helper tool rather than the main executable for the containing .app. codesign -s Developer ID Application --options=runtime,library --timestamp -f ***.app/Contents/Resources/
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
May ’23
Reply to Swift stdlib tool Error: Task failed with exit 0 signal 4
With XCode 10 beta this error shows Command CodeSign failed with a nonzero exit code
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Jul ’18
Reply to application-identifier error when submitting re-signed app
If anyone faces the same issue just as I did in 2023. This was the solution that finally resolved it. Framework has to be signed along with the app if you are going to use different signer codesign -f -s Distribution Certificate Name MyApp.app/Frameworks/* then sign the app again codesign -f -s Distribution Certificate Name MyApp.app https://gist.github.com/chaitanyagupta/9a2a13f0a3e6755192f7?permalink_comment_id=1812865#gistcomment-1812865
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
Oct ’23
Reply to "Application damaged and can't be opened' error prompt on 15.6.1 Sequoia
[quote='873484022, oddeyed, /thread/799110?answerId=873484022#873484022, /profile/oddeyed'] My application currently requires elevated privileges or “sudo” to verify the codesign … [/quote] Lemme see if I understand this correctly: You take a Mac that’s never seen your app before. You install your app in the standard way that a user would install it. This command fails: % codesign --verify --deep --strict /path/to/your.app Instead you have to do this: % sudo codesign --verify --deep --strict /path/to/your.app Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jan ’26
Reply to Developer Error
Showing All Errors OnlyCommand CodeSign failed with a nonzero exit code
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
May ’20
Reply to revoked my signing account
If you haven't figured this out yet, you need the paid account for codesigning and provisioning.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
May ’17
Reply to App is damaged and can't be opened, despite being codesigned
I am indeed running it through the Terminal, not Finder. Wouldn't Gatekeeper block the application regardless of where it's being launched from? Well, it should, but it doesn’t, which is why we consider it a bug (r. 58097824)-: code has no resources but signature indicates they must be present Consider this sequence: % cp /usr/bin/true MyTrue % codesign -s - -f MyTrue MyTrue: replacing existing signature % codesign -d -v MyTrue … Format=Mach-O universal (x86_64 arm64e) … I make a copy of the true command and re-sign it. When I dump the signature, codesign shows the Format property as a plain Mach-O. Now let’s put this in an app wrapper and re-sign: % mkdir -p MyTrue.app/Contents/MacOS % mv MyTrue MyTrue.app/Contents/MacOS/ % codesign -s - -f MyTrue.app MyTrue.app: replacing existing signature % codesign -d -v MyTrue.app … Format=bundle with Mach-O universal (x86_64 arm64e) … Here codesign has detected the app wrapper and signed the code as a bundle. Note h
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Nov ’23
Reply to How to app distribution for Mac
Feel free to ignore the comments I left above. The case is an error with the extension app, and it is considered normal, not an error with the actual app. I also encountered the following problem: I've read all the documentation to fix the issue, but I can't confirm any idea why this is happening? Case 1 I had an existing Apple Development signed app for distribution. Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/embedded.provisionprofile Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension/Contents/embedded.provisionprofile However, in order to distribute the a
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Feb ’22
Reply to Notarization started failing this week
Thanks to everyone for your feedback. After reading your posts and following your links, I was able to figure it out. It turns out the fault was mine. (1) I did not have the necessary certificate, and (2) I had to do a manual codesign with the new certificateBefore when I did a codesign -dvvvv I could see that the binary was signed, but the Apple Development signing certificate (line 3 below) was not sufficient.$ codesign -dvvv --entitlements :- /tmp/helloworld.dst/usr/local/bin/helloworld ... Authority=Apple Development: XXXXXX (XXXXXXXXXX)After requesting and getting a Developer ID Application certificate, and then manually signing the binary with that, notarization started working for me again.$ codesign -s Developer ID Application: XXXXXXXX (XXXXXXXXXX) --options=runtime --force /tmp/helloworld.dst/usr/local/bin/helloworldcodesign -dvvv --entitlements :- /tmp/helloworld.dst/usr/local/bin/helloworld ... Authority=Developer ID Application: XXXXXXX (XXXXXXXXXX)So if the Au
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
Feb ’20
Reply to Error: Failed with Exit Code 1
Fixed it. I did Option - Command - Shift - K, which led to another Error: Command CodeSign failed with a nonzero exit code. I Googled that which led a StackOverflow page:https://stackoverflow.com/questions/52421999/xcode-10-command-codesign-failed-with-a-nonzero-exit-codeIt had instructions on resetting my Keychain Access. Thanks for the help.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Aug ’19
Reply to VisionOS Codesigning
THanks for the reply @eskimo . Do you have any documentation that you can refer to me regarding codesigning and VisionOS? I would appreciate it. Thanks.
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Feb ’24