Search results for

“codesign”

3,221 results found

Post

Replies

Boosts

Views

Activity

Reply to Keychain access prompt on app upgrade
Thanks for the reply, Quinn. If I run codesign -dvvv -r- on my app, I can see that a designated requirement is being created for it. It looks like this:designated => identifier <my apps bundle id> and certificate leaf = H<leaf certificate hash>So, there is a designated requirement. I'm not sure why this wouldn't be sufficient. None of these value should change on upgrade.
Topic: Privacy & Security SubTopic: General Tags:
Mar ’18
Reply to NetworkExtension Flow source of traffic
You can do this using codesign: $ codesign -d --requirements - /Applications/TextEdit.app Executable=/Applications/TextEdit.app/Contents/MacOS/TextEdit designated => identifier com.apple.TextEdit and anchor apple $ $ codesign -d -v /Applications/TextEdit.app Executable=/Applications/TextEdit.app/Contents/MacOS/TextEdit Identifier=com.apple.TextEdit …Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Mar ’18
Swift stdlib tool error
Dear Community,I was writing my first App on XCode 9.2 and Swift and wanted to build and run it on my iPhone X but it crashed on BuildTime with the error:error: Task failed with exit 1 signal 0 { /usr/bin/codesign '--force' '--sign' '8ADFAD19462E04A6E966AF7F71D5402C4AF525CA' '--verbose' '/Users/Simon/Library/Developer/Xcode/DerivedData/Object_Recognizer-berxtxtaqlvwfcbrqkdxwlnelwhs/Build/Products/Debug-iphoneos/Object Recognizer.app/Frameworks/libswiftAVFoundation.dylib'}On first XCode asked me to enter my KeyChain password but I messed it up, because the password I remembered didn't match. Neither restarting, rebooting, reinstalling, resetting the developer account nor resetting the Login KeyChain fixed the problem.Compiling for the iOS Simulator works fine, but I need to access the camera so this isn't an option for me.Thanks for any help and suggestions!Yours,Simon
2
0
1.3k
Mar ’18
Reply to Certificate-private key combo failure
I pulled code into a test application with some unit tests. The binary is signed. The tests create a keychain file on the desktop, password protected. The tests: create Certificate Signing Request - succeeds import identity - succeeds, identity is the one returned from a successful registration using the above CSR sign - fails: CSSMERR_CSP_OPERATION_AUTH_DENIED verify - not tested because it depends on signature above encrypt - succeeds, returns cipherText decrypt - falis: CSSMERR_CSP_OPERATION_AUTH_DENIEDI am at my wits end (easy for me to reach, apparently). The only googled-info I can find claims the CSSMERR_CSP_OPERATION_AUTH_DENIED error is due to an improperly signed binary. Mine is signed, verified by codesign. The keychain is unlocked (probably not necessary) when the private key is used. What am I missing?Thanks for any insights.PS FWIW foover == pch-ivanti Two dev account memeberships, two logins.
Topic: Privacy & Security SubTopic: General Tags:
Apr ’18
xcodebuild OTHER_CODE_SIGN_FLAGS --keychain search order
Hi,I am posting this in the hopes that it may save someone with a similar problem some time.A build was failing with the following error:Code Signing Error: Provisioning profile FooBar doesn't include signing certificate iPhone Developer: foo bar (xxxxxxxxxxx).The build was done on the command line with:xcodebuild OTHER_CODE_SIGN_FLAGS='--keychain /Users/me/Library/Keychains/Buildsystem' (and other parameters)Before each build we create the Buildsystem keychain and import the certificates needed fo the build into it. The keychain is then removed after the build.I could do the build locally and it would work, it was only on our build machine under jenkins that it failed.After spending a lot of time on this I found the cause was that there was another certificate in the builds machine's login keychain that was being used for the code signing even though we had provided a keychain with the correct certificate and told the codsigning to use it. After deleting the bad certificate from teh login keychain everything
2
0
6.7k
Apr ’18
Reply to Certificate-private key combo failure
Yes, it is a macOS (10.12+) command line tool that runs in the system context.The binary is signed, signature verified by codesign. The signing cert is a valid Apple-generated cert.The keychain file is created by the tool and not stored in /Library/Keychains - don't know if that makes any difference.A generated (SecKeyGeneratePair) RSA key pair works - data can be signed and verified.The issue seems to be related to using an identity... When the private key is obtained from an identity, signing fails. The indentity is created when a certificate is imported into the keychain and the keychain matches it with the existing private key.Any suggestions for how to debug what is going on?Thanks.
Topic: Privacy & Security SubTopic: General Tags:
Apr ’18
I am creating a sticker pack and receiving this error: Command /usr/bin/codesign failed with exit code 1 ...I cannot figure out how to resolve this issue. Any ideas/suggestions?
Hi All,I am creating a sticker pack in X code and I keep receiving this error message:Command /usr/bin/codesign failed with exit code 1How do I resolve this issue? I've been troubleshooting but cannot find the error. I had it built earlier with out the error and then rerunning got it again.
0
0
707
Apr ’18
Reply to Published Watch App install fails with empty error
After struggling two weeks against this issue, I finally foud an explanation and workaround.Here is the comment I just posted on the bug report 39488346 :OK, I now have nailed down the issue to an unicode encoding/normalization. By managing to suppress any accented character from any file (coming from the product name) in the Watch application and extension, the Apple signed binary now install correctly on the Watch.This is a MAJOR recent regression. It appears that WatchOS has recently switched between UTF-8/UTF16 and or between NFC/NFD normalization and that the signature check has NOT been updated accordingly. This explains why codesign on MacOS does not see any signature issue, while the WatchOS reject it.
Topic: App & System Services SubTopic: General Tags:
Apr ’18
SOLVED: Issue with spctl / gatekeeper after successfully codesigning application
Hello,I am facing a rather strange issue with the codesigning of my application. Even though the codesigning and its verification are successful the app failsthe spctl -a -t exec -vv command, having the result simply <app> rejected. This of course also makes the gatekeeper check fail and the app can not be opened automatically. If the search I have done so far is correct, the issue seems to have to do with the apple codesigning authority of the certificate I use (which is generated as per the instructions in the certificates section of my apple developer account) to sign the application. I am pasting the output of the codesign --display --verbose=4 below, where the authority is stated as Authority=Apple Worldwide Developer Relations Certification Authority and not Authority=Developer ID Certification Authority . Is that the error, or not, and if so, how can it be addressed?Executable=<path to executable>Identifier=<identifier>Format=app bundle with Mach-O
1
0
3.4k
Apr ’18
Keychain access password prompt on app upgrade
We have an app which creates a custom keychain to store some data. We were using “3rd Party Mac Developer Application” certificate to sign our app.The cert got expired in March, 2015. We generated a new cert from the same account and signed the updated version on the app. But, now the system prompts for keychain password whenever the updated app tries to read the keychain content created by the older version of the app, even though both the app versions are signed using the certs from the same account.We are using the following command to sign the app from command line :codesign --sign 3rd Party Mac Developer Application: ******” --force --keychain <keychain-name> --verbose <appname>The designated requirement for the app is identifier <app bundle id> and anchor apple generic and certificate leaf[subject.CN] = 3rd Party Mac Developer Application: ****** (*********) and certificate 1[field.<some numbers>] / exists */Please suggest some solution to avoid the UI-prompt asking the
4
0
1.5k
Apr ’18
Testing App on my iPhone
Hi,What does it mean when building an app for testing on iPhone fails and Xcode signals: ! Task failed with exit 1 signal 0 {/usr/bin/codesign '--force' '--sign' '273EC7AA17CA1209AA7AA8B4DF31A5EC1947CEFE' '--verbose' '/Users/halimnataprawira/Library/Developer/Xcode/DerivedData/AvatarApp-enfhidvegjcpkldkeigzhtrokqwq/Build/Products/Debug-iphoneos/AvatarApp.app/Frameworks/libswiftCore.dylib'}Any Xcode wizards out there that might know how to troubleshoot this?Thank you in advancezWolf
3
0
741
Apr ’18
Reply to Keychain access prompt on app upgrade
Thanks for the reply, Quinn. If I run codesign -dvvv -r- on my app, I can see that a designated requirement is being created for it. It looks like this:designated => identifier <my apps bundle id> and certificate leaf = H<leaf certificate hash>So, there is a designated requirement. I'm not sure why this wouldn't be sufficient. None of these value should change on upgrade.
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’18
Reply to NetworkExtension Flow source of traffic
You can do this using codesign: $ codesign -d --requirements - /Applications/TextEdit.app Executable=/Applications/TextEdit.app/Contents/MacOS/TextEdit designated => identifier com.apple.TextEdit and anchor apple $ $ codesign -d -v /Applications/TextEdit.app Executable=/Applications/TextEdit.app/Contents/MacOS/TextEdit Identifier=com.apple.TextEdit …Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Replies
Boosts
Views
Activity
Mar ’18
Swift stdlib tool error
Dear Community,I was writing my first App on XCode 9.2 and Swift and wanted to build and run it on my iPhone X but it crashed on BuildTime with the error:error: Task failed with exit 1 signal 0 { /usr/bin/codesign '--force' '--sign' '8ADFAD19462E04A6E966AF7F71D5402C4AF525CA' '--verbose' '/Users/Simon/Library/Developer/Xcode/DerivedData/Object_Recognizer-berxtxtaqlvwfcbrqkdxwlnelwhs/Build/Products/Debug-iphoneos/Object Recognizer.app/Frameworks/libswiftAVFoundation.dylib'}On first XCode asked me to enter my KeyChain password but I messed it up, because the password I remembered didn't match. Neither restarting, rebooting, reinstalling, resetting the developer account nor resetting the Login KeyChain fixed the problem.Compiling for the iOS Simulator works fine, but I need to access the camera so this isn't an option for me.Thanks for any help and suggestions!Yours,Simon
Replies
2
Boosts
0
Views
1.3k
Activity
Mar ’18
Reply to IBDesignables, no suitable image, required code signature missing
I think you're at the point where you need to submit a bug report.Does the framework have the general appearance of being codesigned? If so, can you verify the codesigning using the 'codesign' command line tool. (I think that's its name.)
Replies
Boosts
Views
Activity
Apr ’18
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 Certificate-private key combo failure
I pulled code into a test application with some unit tests. The binary is signed. The tests create a keychain file on the desktop, password protected. The tests: create Certificate Signing Request - succeeds import identity - succeeds, identity is the one returned from a successful registration using the above CSR sign - fails: CSSMERR_CSP_OPERATION_AUTH_DENIED verify - not tested because it depends on signature above encrypt - succeeds, returns cipherText decrypt - falis: CSSMERR_CSP_OPERATION_AUTH_DENIEDI am at my wits end (easy for me to reach, apparently). The only googled-info I can find claims the CSSMERR_CSP_OPERATION_AUTH_DENIED error is due to an improperly signed binary. Mine is signed, verified by codesign. The keychain is unlocked (probably not necessary) when the private key is used. What am I missing?Thanks for any insights.PS FWIW foover == pch-ivanti Two dev account memeberships, two logins.
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’18
xcodebuild OTHER_CODE_SIGN_FLAGS --keychain search order
Hi,I am posting this in the hopes that it may save someone with a similar problem some time.A build was failing with the following error:Code Signing Error: Provisioning profile FooBar doesn't include signing certificate iPhone Developer: foo bar (xxxxxxxxxxx).The build was done on the command line with:xcodebuild OTHER_CODE_SIGN_FLAGS='--keychain /Users/me/Library/Keychains/Buildsystem' (and other parameters)Before each build we create the Buildsystem keychain and import the certificates needed fo the build into it. The keychain is then removed after the build.I could do the build locally and it would work, it was only on our build machine under jenkins that it failed.After spending a lot of time on this I found the cause was that there was another certificate in the builds machine's login keychain that was being used for the code signing even though we had provided a keychain with the correct certificate and told the codsigning to use it. After deleting the bad certificate from teh login keychain everything
Replies
2
Boosts
0
Views
6.7k
Activity
Apr ’18
Reply to Certificate-private key combo failure
Yes, it is a macOS (10.12+) command line tool that runs in the system context.The binary is signed, signature verified by codesign. The signing cert is a valid Apple-generated cert.The keychain file is created by the tool and not stored in /Library/Keychains - don't know if that makes any difference.A generated (SecKeyGeneratePair) RSA key pair works - data can be signed and verified.The issue seems to be related to using an identity... When the private key is obtained from an identity, signing fails. The indentity is created when a certificate is imported into the keychain and the keychain matches it with the existing private key.Any suggestions for how to debug what is going on?Thanks.
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’18
I am creating a sticker pack and receiving this error: Command /usr/bin/codesign failed with exit code 1 ...I cannot figure out how to resolve this issue. Any ideas/suggestions?
Hi All,I am creating a sticker pack in X code and I keep receiving this error message:Command /usr/bin/codesign failed with exit code 1How do I resolve this issue? I've been troubleshooting but cannot find the error. I had it built earlier with out the error and then rerunning got it again.
Replies
0
Boosts
0
Views
707
Activity
Apr ’18
Reply to Xcode 9.3 archive missing archived-expanded-entitlements.xcent file
Have the same issue.Apple, does it mean, this file is not needed in ipa anymore and you are puting entitlements using codesign only?
Replies
Boosts
Views
Activity
Apr ’18
Reply to Published Watch App install fails with empty error
After struggling two weeks against this issue, I finally foud an explanation and workaround.Here is the comment I just posted on the bug report 39488346 :OK, I now have nailed down the issue to an unicode encoding/normalization. By managing to suppress any accented character from any file (coming from the product name) in the Watch application and extension, the Apple signed binary now install correctly on the Watch.This is a MAJOR recent regression. It appears that WatchOS has recently switched between UTF-8/UTF16 and or between NFC/NFD normalization and that the signature check has NOT been updated accordingly. This explains why codesign on MacOS does not see any signature issue, while the WatchOS reject it.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’18
SOLVED: Issue with spctl / gatekeeper after successfully codesigning application
Hello,I am facing a rather strange issue with the codesigning of my application. Even though the codesigning and its verification are successful the app failsthe spctl -a -t exec -vv command, having the result simply <app> rejected. This of course also makes the gatekeeper check fail and the app can not be opened automatically. If the search I have done so far is correct, the issue seems to have to do with the apple codesigning authority of the certificate I use (which is generated as per the instructions in the certificates section of my apple developer account) to sign the application. I am pasting the output of the codesign --display --verbose=4 below, where the authority is stated as Authority=Apple Worldwide Developer Relations Certification Authority and not Authority=Developer ID Certification Authority . Is that the error, or not, and if so, how can it be addressed?Executable=<path to executable>Identifier=<identifier>Format=app bundle with Mach-O
Replies
1
Boosts
0
Views
3.4k
Activity
Apr ’18
Keychain access password prompt on app upgrade
We have an app which creates a custom keychain to store some data. We were using “3rd Party Mac Developer Application” certificate to sign our app.The cert got expired in March, 2015. We generated a new cert from the same account and signed the updated version on the app. But, now the system prompts for keychain password whenever the updated app tries to read the keychain content created by the older version of the app, even though both the app versions are signed using the certs from the same account.We are using the following command to sign the app from command line :codesign --sign 3rd Party Mac Developer Application: ******” --force --keychain <keychain-name> --verbose <appname>The designated requirement for the app is identifier <app bundle id> and anchor apple generic and certificate leaf[subject.CN] = 3rd Party Mac Developer Application: ****** (*********) and certificate 1[field.<some numbers>] / exists */Please suggest some solution to avoid the UI-prompt asking the
Replies
4
Boosts
0
Views
1.5k
Activity
Apr ’18
Testing App on my iPhone
Hi,What does it mean when building an app for testing on iPhone fails and Xcode signals: ! Task failed with exit 1 signal 0 {/usr/bin/codesign '--force' '--sign' '273EC7AA17CA1209AA7AA8B4DF31A5EC1947CEFE' '--verbose' '/Users/halimnataprawira/Library/Developer/Xcode/DerivedData/AvatarApp-enfhidvegjcpkldkeigzhtrokqwq/Build/Products/Debug-iphoneos/AvatarApp.app/Frameworks/libswiftCore.dylib'}Any Xcode wizards out there that might know how to troubleshoot this?Thank you in advancezWolf
Replies
3
Boosts
0
Views
741
Activity
Apr ’18
Reply to How to read data from NEAppProxyTCPFlow?
Thank you,eskimoYes,I'm sure that the completion handler has been called,and error is nil.I called '-(void)readDataWithCompletionHandler:' in the open completion handler.Is it because of this reason that I use the development provisioning profile to codesign, not the enterprise provisioning profile?Thanks,SKtt
Replies
Boosts
Views
Activity
Apr ’18