Search results for

“codesign”

3,222 results found

Post

Replies

Boosts

Views

Activity

Reply to macOS Autonomous Single App Mode
eskimo, Thanks for your response. I will try to apply a provisioning profile firstly. My app is built and signed using command line. After app is built, I use codesign to sign the whole app, like: codesign --force --verify --verbose --entitlements XXX.entitlements --options runtime --sign Developer ID Application: XXX XXX.app How to sign it with the provisioning profile? I did not find any related parameter in codesign.
Topic: Code Signing SubTopic: Entitlements Tags:
Sep ’20
Codesign -- force not signing 3rd Pty binaries
This math-educational 3D-graphics courseware utilizes Java3D, which sits on top of hardware-dependent JOGAMP binaries (which instruct at the GPU-level). This code signing command applied to the installer .dmg: codesign -s myName --force --options runtime ~/DFG2D_MacOS_Manufacturing/MacOSInstallers/DFG2D_Mac_J1602_x86/DataflowGeometry2D-1.0.300.dmg is supposed to force signing of all the embedded binaries, BUT the notary tool finds about 25 jogamp-fat dynamic libraries (/ *.dylib) UNSIGNED. Processing complete id: 23d81a99-4087-48d2-a567-8072dd2820fe status: Invalid pierrebierre@Pierres-iMac ~ % xcrun notarytool log 17d2fe94-f38a-47d4-9568-cf4dc65f24c9 --apple-id xxxxxxxxxxx --team-id XXXXXXXXX --password pwpwpwpwpw { logFormatVersion: 1, jobId: 17d2fe94-f38a-47d4-9568-cf4dc65f24c9, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: DataflowGeometry2D-1.0.300.dmg, uploadDate: 2025-07-13T21:28:21.147Z, sha256: 57320c4ad4a07f144336084152bf7e33
Topic: Code Signing SubTopic: General
9
0
465
Jul ’25
How to download a codesign certificate for my MAC App
Hi All,I have an enterprise apple developer program login with Admin role.We have a developer build machine which is no more now, hence we are re-creating it again from the scratch.I have to install a code / product signing certificate for one of our MAC OS X App.From my developer login I could see the certificate which is - Developer ID installer and it has validity as well.But I could not able to download / use it. I tried from the Team Agent role as well but it is able to download only the certificate but I could not able to get the key.Since there is no key I could not able to use the certificate for signing my apps.How to download the certificate along with key from this portal.Any help is really appreciatedThanks,Saravana
1
0
646
Sep ’16
Codesign failed - .ipa does not exist
For days I'm looking for solution to this problem. I have tried many different answers from Stack Overflow and other sites, but still problem is the same.When I try to validate my app, I have tried with other apps also, the problem is the same, it gives me this error:An error occurred during validation:Codesign failed.Archive validation failed duo to issues listed below.! Unable to validate your application.The archive is invalid. /var/folders/26/rk825_6d2178gmwjt_6rtgw0000gn/T/XcodeDistPipeline.G1G/Packages/myApp.ipa does not exist.I have tried answers like:Logged out from my developer account in Xcode preferences. Turn off bitCode from build settings. Removed unwanted libraries from build phases -> Link binary with librariesTried to export the app and upload it through application loader, and got this error:An error occurred during validation:Codesign failed.I also added this piece of code to my plist:<dict> <key>method</key> <string>app-store</string></dict>I have als
4
0
2.8k
Jan ’17
Reply to Codesigned app just hangs
Also the console app shows no errors, and I sign like this for every executable in the app: codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/libffmpeg.dylib codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/nwjs Framework.framework/libnode.dylib codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/nwjs Framework.framework/Resources/app_mode_loader.app/Contents/MacOS/app_mode_loader codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/nwjs Framework.framework/Versions/Current/Libraries/WidevineCdm/_platform_specific/mac_x64/widevinecdmadapter.plugin codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime W
Topic: Code Signing SubTopic: General Tags:
Jul ’21
Error: Command CodeSign failed with a nonzero exit code Xcode in 13.2.1
I got this Codesign error when attempting to run one of my applications on my iPhone, I tried a couple more of my apps and i still get the same error. Also, I only get this error when I’m running the app on my iPhone that’s plugged into my computer but I get no errors when running on a simulator. Thus, this error seems to be due to my iPhone. From what I read online I tried the following: Restart both my Mac and iPhone no success. I tried multiple times and still got the same error. Check my provisioning profile and certificates everything looks fine but I'm a newbie so I could be wrong. What I noticed that may be causing the error: I stopped using Xcode for about 3 months and during that time I updated my iPhone version to 15.6.1, but the iOS Deployment Target only goes up to 15.2. So with all this said, is it possible to run an older version say 15.2 when your iPhones version is higher (like mine which is 15.6.1)? ^ If this is possible, where else could this error be coming from? Thank you!
0
0
570
Sep ’22
Reply to errSecInternalComponent building locally with Xcode
Thanks for the info! I'll try the export/import in a minute, but tried the log export first and thought I'd post it here now in case you see something that points in a particular direction. I believe this is the section of logs resulting from running the MyTrue test: default 2023-10-02 13:14:49.496818 -0700 securityd 0x7fa4ea41e400(0x7fa4ec4095b0) is unlocked; decoding for makeUnlocked() default 2023-10-02 13:14:49.496954 -0700 securityd CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.496983 -0700 securityd CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497085 -0700 codesign CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497112 -0700 codesign CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497131 -0700 codesign caught CssmError: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497132 -0700 codesign MAC verification failed
Topic: Code Signing SubTopic: General Tags:
Oct ’23
Reply to Connection Interrupted Error sudo -u _securityagent pluginkit -a /Applications/SmartCardApp.app/Contents/PlugIns/CssToken.appex
I tried that sudo -u _securityagent /Applications/HostApp.app/Contents/MacOS/HostApp for my app. But I am receiving the following error: Illegal instruction: 4 I want to be able to use identities on a Cryptographic Token from codesign when codesign is running in the context of a script started by a daemon. Do you know how I can do that? Right now if I tried to codesign under daemon context using Popen I received the following error: 'error: The specified item could not be found in the keychain.n'.
Topic: Privacy & Security SubTopic: General Tags:
Dec ’21
Reply to Getting past the unidentified developer problem
You don't need a Xcode - Project, but within Xcode codesigning and notarization are much easier than in a separate Workflow. The decisive terminal commands are 'codesign' for signing and 'altool' for notarization. There are man-pages for the commands and a good documentation for manual codesigning: https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html With codesigning you will get rid of the 'unidentified developer' message, but without notarization Gatekeeper still won't let you through, because your app isn't checked for malware. That is what notarization does. Please keep in mind that 'altool' will stop working in fall 2023. There will be a replacement for it, but I haven't tried that yet (and forgot the name). Good luck Brigitte
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’22
Reply to macOS Autonomous Single App Mode
eskimo, Thanks for your response. I will try to apply a provisioning profile firstly. My app is built and signed using command line. After app is built, I use codesign to sign the whole app, like: codesign --force --verify --verbose --entitlements XXX.entitlements --options runtime --sign Developer ID Application: XXX XXX.app How to sign it with the provisioning profile? I did not find any related parameter in codesign.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Sep ’20
Codesign -- force not signing 3rd Pty binaries
This math-educational 3D-graphics courseware utilizes Java3D, which sits on top of hardware-dependent JOGAMP binaries (which instruct at the GPU-level). This code signing command applied to the installer .dmg: codesign -s myName --force --options runtime ~/DFG2D_MacOS_Manufacturing/MacOSInstallers/DFG2D_Mac_J1602_x86/DataflowGeometry2D-1.0.300.dmg is supposed to force signing of all the embedded binaries, BUT the notary tool finds about 25 jogamp-fat dynamic libraries (/ *.dylib) UNSIGNED. Processing complete id: 23d81a99-4087-48d2-a567-8072dd2820fe status: Invalid pierrebierre@Pierres-iMac ~ % xcrun notarytool log 17d2fe94-f38a-47d4-9568-cf4dc65f24c9 --apple-id xxxxxxxxxxx --team-id XXXXXXXXX --password pwpwpwpwpw { logFormatVersion: 1, jobId: 17d2fe94-f38a-47d4-9568-cf4dc65f24c9, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: DataflowGeometry2D-1.0.300.dmg, uploadDate: 2025-07-13T21:28:21.147Z, sha256: 57320c4ad4a07f144336084152bf7e33
Topic: Code Signing SubTopic: General
Replies
9
Boosts
0
Views
465
Activity
Jul ’25
How to download a codesign certificate for my MAC App
Hi All,I have an enterprise apple developer program login with Admin role.We have a developer build machine which is no more now, hence we are re-creating it again from the scratch.I have to install a code / product signing certificate for one of our MAC OS X App.From my developer login I could see the certificate which is - Developer ID installer and it has validity as well.But I could not able to download / use it. I tried from the Team Agent role as well but it is able to download only the certificate but I could not able to get the key.Since there is no key I could not able to use the certificate for signing my apps.How to download the certificate along with key from this portal.Any help is really appreciatedThanks,Saravana
Replies
1
Boosts
0
Views
646
Activity
Sep ’16
Codesign failed - .ipa does not exist
For days I'm looking for solution to this problem. I have tried many different answers from Stack Overflow and other sites, but still problem is the same.When I try to validate my app, I have tried with other apps also, the problem is the same, it gives me this error:An error occurred during validation:Codesign failed.Archive validation failed duo to issues listed below.! Unable to validate your application.The archive is invalid. /var/folders/26/rk825_6d2178gmwjt_6rtgw0000gn/T/XcodeDistPipeline.G1G/Packages/myApp.ipa does not exist.I have tried answers like:Logged out from my developer account in Xcode preferences. Turn off bitCode from build settings. Removed unwanted libraries from build phases -> Link binary with librariesTried to export the app and upload it through application loader, and got this error:An error occurred during validation:Codesign failed.I also added this piece of code to my plist:<dict> <key>method</key> <string>app-store</string></dict>I have als
Replies
4
Boosts
0
Views
2.8k
Activity
Jan ’17
Reply to App not launch on an M1 mac
` codesign --force --deep -s - APP1.app APP1.app: replacing existing signature ` This is not a solution because the app is a sandbox app and after the new codesign it's no longer a sandbox app.
Replies
Boosts
Views
Activity
Nov ’21
Reply to IBDesignables, no suitable image, required code signature missing
Perhaps you're right...I don't understand what you mean by Does the framework have the general appearance of being codesigned? I've never made any changes to codesigning for Pods, and as I mentioned this error points to more than just one Pod framework. It's multiple errors.
Replies
Boosts
Views
Activity
Apr ’18
Reply to trying to get permission for my app to access the wacom tablet
Still running up against this. Essentially the wacom tablet functionality works until I codesign the app (using hardened runtime), then it doesnt work anymore. Anyone able to advise why this might be? Why would codesigning break my wacom functionality?
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Aug ’20
Reply to Codesigned app just hangs
Also the console app shows no errors, and I sign like this for every executable in the app: codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/libffmpeg.dylib codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/nwjs Framework.framework/libnode.dylib codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/nwjs Framework.framework/Resources/app_mode_loader.app/Contents/MacOS/app_mode_loader codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime WhoStoleMyBeard.app/Contents/Versions/65.0.3325.146/nwjs Framework.framework/Versions/Current/Libraries/WidevineCdm/_platform_specific/mac_x64/widevinecdmadapter.plugin codesign -s Developer ID Application: Neil Collier --timestamp -f --options runtime W
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jul ’21
Reply to CFBundleIdentifier Collision for using FMOD
Thanks Quinn, much appreciated! I actually was just reading the man page for codesign and found --remove-signature, gave it a go and just as you suggested, it helped Xcode re-codesign it correctly. I have now uploaded to App Store Connect without any errors.
Replies
Boosts
Views
Activity
May ’21
Error: Command CodeSign failed with a nonzero exit code Xcode in 13.2.1
I got this Codesign error when attempting to run one of my applications on my iPhone, I tried a couple more of my apps and i still get the same error. Also, I only get this error when I’m running the app on my iPhone that’s plugged into my computer but I get no errors when running on a simulator. Thus, this error seems to be due to my iPhone. From what I read online I tried the following: Restart both my Mac and iPhone no success. I tried multiple times and still got the same error. Check my provisioning profile and certificates everything looks fine but I'm a newbie so I could be wrong. What I noticed that may be causing the error: I stopped using Xcode for about 3 months and during that time I updated my iPhone version to 15.6.1, but the iOS Deployment Target only goes up to 15.2. So with all this said, is it possible to run an older version say 15.2 when your iPhones version is higher (like mine which is 15.6.1)? ^ If this is possible, where else could this error be coming from? Thank you!
Replies
0
Boosts
0
Views
570
Activity
Sep ’22
Reply to errSecInternalComponent building locally with Xcode
Thanks for the info! I'll try the export/import in a minute, but tried the log export first and thought I'd post it here now in case you see something that points in a particular direction. I believe this is the section of logs resulting from running the MyTrue test: default 2023-10-02 13:14:49.496818 -0700 securityd 0x7fa4ea41e400(0x7fa4ec4095b0) is unlocked; decoding for makeUnlocked() default 2023-10-02 13:14:49.496954 -0700 securityd CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.496983 -0700 securityd CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497085 -0700 codesign CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497112 -0700 codesign CSSM Exception: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497131 -0700 codesign caught CssmError: -2147415734 CSSMERR_CSP_VERIFY_FAILED default 2023-10-02 13:14:49.497132 -0700 codesign MAC verification failed
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’23
Reply to Connection Interrupted Error sudo -u _securityagent pluginkit -a /Applications/SmartCardApp.app/Contents/PlugIns/CssToken.appex
I tried that sudo -u _securityagent /Applications/HostApp.app/Contents/MacOS/HostApp for my app. But I am receiving the following error: Illegal instruction: 4 I want to be able to use identities on a Cryptographic Token from codesign when codesign is running in the context of a script started by a daemon. Do you know how I can do that? Right now if I tried to codesign under daemon context using Popen I received the following error: 'error: The specified item could not be found in the keychain.n'.
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Dec ’21
Reply to The staple and validate action failed! Error 73.
Did you codesign your flat pkg before you notarize it ?
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’19
Reply to Can I Exporting a Developer ID PacketTunnelProvider Plugin?
This is my extension's entitlements which dump by codesign
Replies
Boosts
Views
Activity
Sep ’25
Reply to Getting past the unidentified developer problem
You don't need a Xcode - Project, but within Xcode codesigning and notarization are much easier than in a separate Workflow. The decisive terminal commands are 'codesign' for signing and 'altool' for notarization. There are man-pages for the commands and a good documentation for manual codesigning: https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html With codesigning you will get rid of the 'unidentified developer' message, but without notarization Gatekeeper still won't let you through, because your app isn't checked for malware. That is what notarization does. Please keep in mind that 'altool' will stop working in fall 2023. There will be a replacement for it, but I haven't tried that yet (and forgot the name). Good luck Brigitte
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’22