Search results for

“codesign”

3,222 results found

Post

Replies

Boosts

Views

Activity

Reply to Notarizing a package
No, the package contains codesigned app. I'm trying to notarize only final package file. I tried to notarize application bundle only for testing purpose. So, to clarify:Case 1:- I tried to notarize application bundle. Notary service is ok with it. I used ditto command to compress it.Case 2:- I created a package which contains non-notarized (but codesigned) application bundle using pkgbuild/productbuild commands. Notary service rejects it.- If I try to install application using this package, it works ok. Both spctl and codesign returns ok for installed app.
Topic: Code Signing SubTopic: General Tags:
Feb ’19
Reply to Codesign -- force not signing 3rd Pty binaries
I have a valid Developer ID certificate and key. When I codesign, I'm prompted to enter my system pw. codesign gives absolutely ZERO feedback that it isn't using the Developer ID I reference in the codesign command line. It just says it's signed in response to --verify. You haven't told me anything specifically actionable, like how would I verify during code signing that it's using my Developer ID vs. adhoc. Is there a way to tell, short of the long, exasperating feedback loop leading to Notarization testing?
Topic: Code Signing SubTopic: General
Aug ’25
Reply to OS X Server Continious Intergration Error CodeSign
Finally I figured it out. Since the codesign and provisional file work properly on your local XCode, the cert. & provisional files should work. So you need to commit and check in your local copy to remote repo. My codesign error was from, I guess I need to make sure the codesign & provisional setting with XCode needs to be corretly set in Project & target.Secondly, follow this instruction, https://github.com/heleny/xcode-continuous-integration. Read the FAQ part. bascially, copy your local provisional files to the folder of your XCode Server
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jul ’15
Reply to How do you codesign with a SmartCard
does this my the previous DeveloperID cert I generated on-device is gone forever, wasted my last DeveloperID slot? I don’t understand this question. This works Cool. However: signing this way results in this Well, that’s weird. That again suggests a chain of trust issue. When you signed the program, did you get any warnings from codesign? What does the full output from codesign -d look like? If you do a codesign -d with the --extract-certificates, what do you get back? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General Tags:
Apr ’23
App Not starting: Termination Reason: Namespace CODESIGNING, Code 0x1
Hi, I am writing a Network Extension (NEPacketTunnelProvider) app for macos. I am using Developer ID signing for my Macos app. But it crashes after I start it on my mac. I have already gone through the notarization. Thanks Time Awake Since Boot: 13000 seconds Time Since Wake: 11000 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXCCRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXCCORPSENOTIFY Termination Reason: Namespace CODESIGNING, Code 0x1 kernel messages: VM Regions Near 0 (cr2):-> TEXT 0000000104aaa000-0000000104b32000 [ 544K] r-x/r-x SM=COW Thread 0 Crashed: 0 @ Z 0x000000010ddb9000 dyld_start + 0 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffeeb155b70 r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r
Topic: Code Signing SubTopic: General Tags:
3
0
8.2k
Oct ’20
Codesigning outside of Xcode EXC_CRASH (Code Signature Invalid)
I have been trying to code sign my Omnis Studio application, so I am signing outside of Xcode. Everything signs ok, I tested it as wellWhen I run a check:Clients & Profits x64beta.app: valid on diskClients & Profits x64beta.app: satisfies its Designated RequirementProcess: CPCloud [3250]Path: /C&P InstallersRuntimes/*/Clients & Profits x64beta.app/Contents/MacOS/CPCloudIdentifier: com.clientsandprofits.CPCloudVersion: ???Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: CPCloud [3250]User ID: 501Date/Time: 2019-11-15 14:36:29.064 -0800OS Version: Mac OS X 10.14.6 (18G103)Report Version: 12Bridge OS Version:3.6 (16P6571)Anonymous UUID: 8EF04917-BF79-DCF9-6C0C-ECCB2995EDA6Time Awake Since Boot: 15000 secondsSystem Integrity Protection: enabledCrashed Thread: 0Exception Type: EXC_CRASH (Code Signature Invalid)Exception Codes:0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTermination Reason:Namespace CODESIGNING, Code 0x1kernel messages:VM Regions Near
Topic: Code Signing SubTopic: General Tags:
1
0
1.8k
Nov ’19
QtWebView, QtBluetooth, etc., are not being codesigned correctly
I've only started to learn about the notarization process within the past eight months. About every three weeks or so, after I've added features to a piece of software I'm writing, I check to make sure I can still get it notarized. Everything worked fine until today. My workflow is the following (I'm running Mac 11.6.1) My program is written in python using tkinter and converted to an .app using pyinstaller. It runs fine on my own machine. I'm not using XCode. Build the package: productbuild --component Desktop/dist/my_app.app Desktop/my_app.pkg Product sign the package: productsign --force --deep --sign 'Developer ID Installer: MyName (XXXXXX7RBW)' /Users/Desktop/my_app.pkg /UsersDesktop/my_app_signed.pkg Check that code is signed. pkgutil --check-signature Desktop/my_app_signed.pkg Obtain an app specific password by visiting https://appleid.apple.com/account/manage Submit for notarization: xcrun altool --notarize-app -f Desktop/my_app_signed.pkg --primary-bundle-id XXXXXX7RBW -u my_email_address -p' @keycha
Topic: Code Signing SubTopic: Notarization Tags:
1
0
638
Apr ’22
CodeSign failed with a non-zero exit code OS Monterey in Xcode 13
I have recently installed Xcode to setup an old react-native app. After adding all the certificates, provisioning profiles when we try to generate a build, codesign asks us to enter the password to access keychain but since it was asking continuously more than 5 times so by mistake I denied once and restarted my system. After that I'm not able to generate the build and there is no popup also coming from Xcode side to allow the permissions. FYI: I completely uninstalled Xcode and deleted all cache files. Still the same issue exists. In this image you can see the error message. Can somebody tell us what's going wrong here and how resolve this issue. FYI: Tried locking/unlocking login keychain access. Removing of duplicate certificates. Requesting developer certificate form apple developers portal. Granting access for xcode in certificate, here I'm not getting the option to add the apps.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
392
Apr ’22
Reply to Xcode notarization and hardened runtime issue
Wow, Apple reports error in our application by message Segmentation fault?Till January 2020 I had workaround by using parameter --timestamp=none. Using that the codesign does not fail. Are you saying that your executable crashes with a segmentation fault? Or that codesign crashes with a segmentation fault? Because JacobMcD started this thread with the former. Consider this quote from their initial post: I have even attempted to force enable hardened runtime on the executable … however, this appears to break the executable, making zsh throw a Segmentation Fault when it is run. This is not codesign crashing, but their executable. OTOH, if you’re seeing codesign crash, that’s definitely weird. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Mar ’20
Unable to Generate .ipa for .NET MAUI iOS App – Codesign Fails With “unable to build chain to self-signed root”
Hi everyone, I am trying to generate an .ipa file for my .NET MAUI (net9.0-ios) application, but every attempt fails with the same codesigning error. I have tried multiple approaches, including building from Windows paired to macOS, and directly building through the macOS terminal, but nothing is working. Below are the exact steps I followed: Steps I Performed 1.>Generated the Apple Development certificate using Keychain Access on macOS. 2.>Added that certificate into my developer account and created the corresponding provisioning profile. 3.>Created an App ID, attached the App ID to the provisioning profile, and downloaded it. 4.>Added the provisioning profile into Xcode. Verified that the certificate is correctly visible in Keychain Access (private key available). Attempted to build/publish the MAUI app to generate the .ipa file. Issue Whenever I run the publish command or build via Windows/macOS, codesigning fails with the following error: /usr/bin/codesign exited wit
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles
1
0
248
Nov ’25
Reply to Notarizing a package
No, the package contains codesigned app. I'm trying to notarize only final package file. I tried to notarize application bundle only for testing purpose. So, to clarify:Case 1:- I tried to notarize application bundle. Notary service is ok with it. I used ditto command to compress it.Case 2:- I created a package which contains non-notarized (but codesigned) application bundle using pkgbuild/productbuild commands. Notary service rejects it.- If I try to install application using this package, it works ok. Both spctl and codesign returns ok for installed app.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Feb ’19
Reply to Codesign -- force not signing 3rd Pty binaries
I have a valid Developer ID certificate and key. When I codesign, I'm prompted to enter my system pw. codesign gives absolutely ZERO feedback that it isn't using the Developer ID I reference in the codesign command line. It just says it's signed in response to --verify. You haven't told me anything specifically actionable, like how would I verify during code signing that it's using my Developer ID vs. adhoc. Is there a way to tell, short of the long, exasperating feedback loop leading to Notarization testing?
Topic: Code Signing SubTopic: General
Replies
Boosts
Views
Activity
Aug ’25
Reply to Big Sur Problem?: "You do not have permission to open the application"
Tried everything here includes codesign but nothing works
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’21
Reply to Kext Invalid ownership
Sorry, I've fixed everything. Problem was in incorrect codesign 🙂
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Aug ’21
Reply to Notarized app but quarantine
Ive Codesigned and notarised the application but still the app is quarantined.
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Aug ’19
Reply to OS X Server Continious Intergration Error CodeSign
Finally I figured it out. Since the codesign and provisional file work properly on your local XCode, the cert. & provisional files should work. So you need to commit and check in your local copy to remote repo. My codesign error was from, I guess I need to make sure the codesign & provisional setting with XCode needs to be corretly set in Project & target.Secondly, follow this instruction, https://github.com/heleny/xcode-continuous-integration. Read the FAQ part. bascially, copy your local provisional files to the folder of your XCode Server
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jul ’15
Reply to How do you codesign with a SmartCard
does this my the previous DeveloperID cert I generated on-device is gone forever, wasted my last DeveloperID slot? I don’t understand this question. This works Cool. However: signing this way results in this Well, that’s weird. That again suggests a chain of trust issue. When you signed the program, did you get any warnings from codesign? What does the full output from codesign -d look like? If you do a codesign -d with the --extract-certificates, what do you get back? 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
Apr ’23
App Not starting: Termination Reason: Namespace CODESIGNING, Code 0x1
Hi, I am writing a Network Extension (NEPacketTunnelProvider) app for macos. I am using Developer ID signing for my Macos app. But it crashes after I start it on my mac. I have already gone through the notarization. Thanks Time Awake Since Boot: 13000 seconds Time Since Wake: 11000 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXCCRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXCCORPSENOTIFY Termination Reason: Namespace CODESIGNING, Code 0x1 kernel messages: VM Regions Near 0 (cr2):-> TEXT 0000000104aaa000-0000000104b32000 [ 544K] r-x/r-x SM=COW Thread 0 Crashed: 0 @ Z 0x000000010ddb9000 dyld_start + 0 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffeeb155b70 r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r
Topic: Code Signing SubTopic: General Tags:
Replies
3
Boosts
0
Views
8.2k
Activity
Oct ’20
Codesigning outside of Xcode EXC_CRASH (Code Signature Invalid)
I have been trying to code sign my Omnis Studio application, so I am signing outside of Xcode. Everything signs ok, I tested it as wellWhen I run a check:Clients & Profits x64beta.app: valid on diskClients & Profits x64beta.app: satisfies its Designated RequirementProcess: CPCloud [3250]Path: /C&P InstallersRuntimes/*/Clients & Profits x64beta.app/Contents/MacOS/CPCloudIdentifier: com.clientsandprofits.CPCloudVersion: ???Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: CPCloud [3250]User ID: 501Date/Time: 2019-11-15 14:36:29.064 -0800OS Version: Mac OS X 10.14.6 (18G103)Report Version: 12Bridge OS Version:3.6 (16P6571)Anonymous UUID: 8EF04917-BF79-DCF9-6C0C-ECCB2995EDA6Time Awake Since Boot: 15000 secondsSystem Integrity Protection: enabledCrashed Thread: 0Exception Type: EXC_CRASH (Code Signature Invalid)Exception Codes:0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTermination Reason:Namespace CODESIGNING, Code 0x1kernel messages:VM Regions Near
Topic: Code Signing SubTopic: General Tags:
Replies
1
Boosts
0
Views
1.8k
Activity
Nov ’19
Reply to Mac12.0.1 loadNib NSValidateNibPathInMainBundle issue
CodeSign exception is fixed, but SecStaticCodeValidateResourceWithErrors still costs 90%+ time in loadNib.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Nov ’21
Codesign really slow since updating to sierra 10.12.1
Anyone else has this issue? What can be done to fix that?
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
19
Boosts
0
Views
13k
Activity
Oct ’16
QtWebView, QtBluetooth, etc., are not being codesigned correctly
I've only started to learn about the notarization process within the past eight months. About every three weeks or so, after I've added features to a piece of software I'm writing, I check to make sure I can still get it notarized. Everything worked fine until today. My workflow is the following (I'm running Mac 11.6.1) My program is written in python using tkinter and converted to an .app using pyinstaller. It runs fine on my own machine. I'm not using XCode. Build the package: productbuild --component Desktop/dist/my_app.app Desktop/my_app.pkg Product sign the package: productsign --force --deep --sign 'Developer ID Installer: MyName (XXXXXX7RBW)' /Users/Desktop/my_app.pkg /UsersDesktop/my_app_signed.pkg Check that code is signed. pkgutil --check-signature Desktop/my_app_signed.pkg Obtain an app specific password by visiting https://appleid.apple.com/account/manage Submit for notarization: xcrun altool --notarize-app -f Desktop/my_app_signed.pkg --primary-bundle-id XXXXXX7RBW -u my_email_address -p' @keycha
Topic: Code Signing SubTopic: Notarization Tags:
Replies
1
Boosts
0
Views
638
Activity
Apr ’22
CodeSign failed with a non-zero exit code OS Monterey in Xcode 13
I have recently installed Xcode to setup an old react-native app. After adding all the certificates, provisioning profiles when we try to generate a build, codesign asks us to enter the password to access keychain but since it was asking continuously more than 5 times so by mistake I denied once and restarted my system. After that I'm not able to generate the build and there is no popup also coming from Xcode side to allow the permissions. FYI: I completely uninstalled Xcode and deleted all cache files. Still the same issue exists. In this image you can see the error message. Can somebody tell us what's going wrong here and how resolve this issue. FYI: Tried locking/unlocking login keychain access. Removing of duplicate certificates. Requesting developer certificate form apple developers portal. Granting access for xcode in certificate, here I'm not getting the option to add the apps.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
0
Boosts
0
Views
392
Activity
Apr ’22
Reply to Xcode notarization and hardened runtime issue
Wow, Apple reports error in our application by message Segmentation fault?Till January 2020 I had workaround by using parameter --timestamp=none. Using that the codesign does not fail. Are you saying that your executable crashes with a segmentation fault? Or that codesign crashes with a segmentation fault? Because JacobMcD started this thread with the former. Consider this quote from their initial post: I have even attempted to force enable hardened runtime on the executable … however, this appears to break the executable, making zsh throw a Segmentation Fault when it is run. This is not codesign crashing, but their executable. OTOH, if you’re seeing codesign crash, that’s definitely weird. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’20
Unable to Generate .ipa for .NET MAUI iOS App – Codesign Fails With “unable to build chain to self-signed root”
Hi everyone, I am trying to generate an .ipa file for my .NET MAUI (net9.0-ios) application, but every attempt fails with the same codesigning error. I have tried multiple approaches, including building from Windows paired to macOS, and directly building through the macOS terminal, but nothing is working. Below are the exact steps I followed: Steps I Performed 1.>Generated the Apple Development certificate using Keychain Access on macOS. 2.>Added that certificate into my developer account and created the corresponding provisioning profile. 3.>Created an App ID, attached the App ID to the provisioning profile, and downloaded it. 4.>Added the provisioning profile into Xcode. Verified that the certificate is correctly visible in Keychain Access (private key available). Attempted to build/publish the MAUI app to generate the .ipa file. Issue Whenever I run the publish command or build via Windows/macOS, codesigning fails with the following error: /usr/bin/codesign exited wit
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles
Replies
1
Boosts
0
Views
248
Activity
Nov ’25