Search results for

“codesign”

3,223 results found

Post

Replies

Boosts

Views

Activity

Device Build fail to Xcode 8
I work with Xcode 8 (Mac OSX sierra) and i cannot run any app on my iPhone.The build fails with error: error: Task failed with exit 0 signal 5I can run the apps on the simulators, just not on a device.The full error message:error: Task failed with exit 0 signal 5 { /usr/bin/codesign '--force' '--sign' '3CC7FF89D95E08EC1873A71D274A88E9B2EE4B99' '--verbose' '/Users/pbresson/Library/Developer/Xcode/DerivedData/pickerEggs-ensuvwahvrjbjgebdslmiofpmlch/Build/Products/Debug-iphoneos/pickerEggs.app/Frameworks/libswiftCore.dylib'}Please help.
3
0
4.4k
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1”
After I executed xattr -rc . in DerivedData, I got this error😕Task failed with exit 0 signal 5 { /usr/bin/codesign '--force' '--sign' '64AD1BBB92372E15F0D3841CCDB0E547351F4BC7' '--verbose' '/Users/Myname/Library/Developer/Xcode/DerivedData/Myapp-bensyburovqkqkcvacgdedoulizo/Build/Products/Debug-iphoneos/Myapp.app/Frameworks/libswiftCore.dylib'}I reinstalled Xcode, but it doesn't work.Anyone know how to fix it?
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1”
Hi.I'm running into this problem for the first time today with my project after updating an advertising SDK and have been unable to solve it.Error:/Users/Mikzor/Library/Developer/Xcode/DerivedData/Unity-iPhone-cudlmprhgwshgfhbqnmbpcuekeqn/Build/Products/Release-iphoneos/sling.app: resource fork, Finder information, or similar detritus not allowedCommand /usr/bin/codesign failed with exit code 1I tried doing xattr -c * as well as xattr -rc . in both the Project folder root and the Derived Data folder root and then perform a clean / rebuild on the project but I always get the same error.I am using macOS Sierra Version 10.12 and XCode 8.1 (8B62)Any help appreciated.
Oct ’16
How do I test a Mac App Store app that uses MapKit?
My app uses MapKit, so Xcode 8 insists I have a provisioning profile. This seems to make it impossible to test the Mac App Store version of my app the way I used to with Xcode 7.With Xcode 7 I could build the MAS version, launch it, and my app would detect there wasn't a valid MAS receipt, exiting with -173. This would cause the OS to put up a login dialog and I could enter a test account and password registered with iTuneConnect. A MAS receipt would then be added to my app and I could launch it after that and test it.With Xcode 8, my app won't even launch. This error is printed to the system log:Oct 30 13:30:56 com.apple.xpc.launchd[1] (com.mycompany.myapp[54628]): Binary is improperly signed.When I type codesign -vv into Terminal, my app is valid on disk and satisfies its Designated Requirement.I think the problem is the binary is signed with my 3rd Party Developer Application certificate, and the provisioning profile that allows MapKit access wants the binary to be signed by Apple. So it's impossi
3
0
610
Oct ’16
gdb 7.12 sierra unknown signal.
GDB 7.12 worked fine (codesigned) on macOS 10.11.On macOS 10.12, it fails miserably with During startup program terminated with signal ?, unknown signal.Checked certificate and codesigning status, nothing changed.Rebuilt from SourceForge, reinstalled/resigned, nothing changed.Disabled SIP, nothing changed.Looks like a macOS bug to me. Any ideas?I fortunately did not upgrade my MAC, just tested it in a Fusion partition. I will be rejecting Sierra until it's fixed.
1
0
5.2k
Nov ’16
codesign ask me 34 times to access
Hi guy,why Xcode ask me for many times to access the keychain and other times only ones or twice?and if I click on 'consenti' (in English 'allow') pop up other codesign prompt. I've counted there are 34 requestscome out.how can I solve this problem?these are two screenshot about problem
2
0
4.9k
Nov ’16
Reply to Confusion about access groups and iOS extensions.
I presume you’re working on iOS (or watchOS or tvOS) here; if you’re developing for the Mac, things are more complex.You can think of the keychain as a database table, where rows in the table are keychain items and columns are various keychain attributes. One of those attributes is kSecAttrAccessGroup, the access group of the item. Here’s how things break down by API: For the query APIs (like SecItemCopyMatching), if you don’t supply kSecAttrAccessGroup in the query then it does a wildcard search, returning all items you have access to, that is, whose access group is contained in your app’s effective keychain access group list.OTOH, when your query contains a value for kSecAttrAccessGroup then: that value must be listed in your app’s effective keychain access group listitems are returned if their access group matches that valueWhen you create an item (SecItemAdd), if you don’t supply a value for kSecAttrAccessGroup then its access group is set to the default keychain access group.OTOH, if you do supply a valu
Topic: Privacy & Security SubTopic: General Tags:
Nov ’16
Reply to Xcode 8 on 10.12 codesign segmentation fault
I'm also having this issue ever since upgrading from 10.11.5 to 10.12 yesterday. I'll get one of two errors, which one seems to be random.I'll either get that Segmentation fault: 11... Or I'll get an error complaining about ambiguous code sign certificates, and the two certificates it lists are actually the same certificate! If I delete the certificate, it complains about not being able to find it. But then when I add it to my login keychain, it complains about ambiguous certificates again.This happens when codesigning in the terminal or from Xcode, in both Xcode 8.1 and Xcode 7.3.
Nov ’16
Command /usr/bin/codesign failed with exit code 1
Hi there! I'm a visual artist, and I am trying my darnedest to create a sticker pack for iMessage. I have a brand new, up to date iMac with the newest Xcode installed. I created my sticker pack, but when I tried to test it on my iphone, I got the error message Command /usr/bin/codesign failed with exit code 1Every subsequent time I tried to run it, whether on my phone or in the simulator, the build failed and I get the same message. Does anyone have any idea what this means or what I can do to fix it?Thank you!!
1
0
437
Nov ’16
Reply to Linking embedded framework with other dynamic framework fails when build & run on device
Based on the log message, it appears that Other.framework is not codesigned. How was it created? It needs to be signed. You can probably workaround this by signing it manually yourself for now, but you should provide more detail about how it's getting built because it should be signed automatically.codesign --force --deep --preserve-metadata=identifier,entitlements,resource-rules,requirements,flags,team-identifier --sign - /path/to/Other.framework
Nov ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1”
Hi ,Im Also having the same problem . Tried both as above but still have the issue.Os :10.12.1Xcode :8.1after 8.1 Update only im having this issueError:Signing Identity: - /usr/bin/codesign --force --sign - --timestamp=none /Users/keerthi/Library/Developer/Xcode/DerivedData/Voxer-garanexqxxqsaxfshffbufgifwcd/Build/Products/Debug-iphonesimulator/DBChooser.bundle/Users/keerthi/Library/Developer/Xcode/DerivedData/Voxer-garanexqxxqsaxfshffbufgifwcd/Build/Products/Debug-iphonesimulator/DBChooser.bundle: bundle format unrecognized, invalid, or unsuitableCommand /usr/bin/codesign failed with exit code 1If Anyone found solution please share .
Nov ’16
Want to sign .dmg file on osx with my apple developer certificate
codesign --force --sign iPhone Distribution: me (...) AA.dmg=> this works, dmg file is signed, but when I open it AA can't be opened because it is from an unidentified developerwhereas the certificate was applied correctly and is in my keychain; the root CA is Apple CAWhen I verify the dmg:spctl -a -t open --context context:primary-signature --verbose=4 -v AA.dmgAA.dmg: rejectedorigin=iPhone Distribution: me (...)So how can I sign my dmg file so my customers will have no warning ?
1
0
2.8k
Nov ’16
SAT Driver couldn't be loaded from Sierra
Hello guys,I'm leading Portable SSD(T1/T3) Project in Samsung Electronics. Recently I've asked to look into issue that our security software is not working after upgarding to Sierra. The root-cause of this issue I've found is Opensource SAT driver which we provided couldn't be loaded due to codesigning version - According to your developer guide for codesigning, version1 driver loading is not allowed from the Sierra. However, there was no version2 sigining when we signed that driver. This makes our customers inconvenient.Therefore, I'd like to ask something to address current situation.1. Is there any reason to block Driver loading which is signed with Version 1 based from the Sierra? I guess this was due to security improvement. But would like to know exactly2. I tested some different MAC PCs, it does not have problem with iMAC PC with Sierra version, but MacBook Air shows failure to load this driver. This is a little bit different scenario from my expectation. Might be Gatekeeper setting i
0
0
302
Nov ’16
Reply to Codesign really slow since updating to sierra 10.12.1
I also had this same problem. In my KeyChain I had 1700+ in the 'My Certificates' section, I delete all but the current Apple certs that I needed and it took my codesigning time down from 4mins to 3secs!
Replies
Boosts
Views
Activity
Oct ’16
Device Build fail to Xcode 8
I work with Xcode 8 (Mac OSX sierra) and i cannot run any app on my iPhone.The build fails with error: error: Task failed with exit 0 signal 5I can run the apps on the simulators, just not on a device.The full error message:error: Task failed with exit 0 signal 5 { /usr/bin/codesign '--force' '--sign' '3CC7FF89D95E08EC1873A71D274A88E9B2EE4B99' '--verbose' '/Users/pbresson/Library/Developer/Xcode/DerivedData/pickerEggs-ensuvwahvrjbjgebdslmiofpmlch/Build/Products/Debug-iphoneos/pickerEggs.app/Frameworks/libswiftCore.dylib'}Please help.
Replies
3
Boosts
0
Views
4.4k
Activity
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1”
After I executed xattr -rc . in DerivedData, I got this error😕Task failed with exit 0 signal 5 { /usr/bin/codesign '--force' '--sign' '64AD1BBB92372E15F0D3841CCDB0E547351F4BC7' '--verbose' '/Users/Myname/Library/Developer/Xcode/DerivedData/Myapp-bensyburovqkqkcvacgdedoulizo/Build/Products/Debug-iphoneos/Myapp.app/Frameworks/libswiftCore.dylib'}I reinstalled Xcode, but it doesn't work.Anyone know how to fix it?
Replies
Boosts
Views
Activity
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1”
Hi.I'm running into this problem for the first time today with my project after updating an advertising SDK and have been unable to solve it.Error:/Users/Mikzor/Library/Developer/Xcode/DerivedData/Unity-iPhone-cudlmprhgwshgfhbqnmbpcuekeqn/Build/Products/Release-iphoneos/sling.app: resource fork, Finder information, or similar detritus not allowedCommand /usr/bin/codesign failed with exit code 1I tried doing xattr -c * as well as xattr -rc . in both the Project folder root and the Derived Data folder root and then perform a clean / rebuild on the project but I always get the same error.I am using macOS Sierra Version 10.12 and XCode 8.1 (8B62)Any help appreciated.
Replies
Boosts
Views
Activity
Oct ’16
How do I test a Mac App Store app that uses MapKit?
My app uses MapKit, so Xcode 8 insists I have a provisioning profile. This seems to make it impossible to test the Mac App Store version of my app the way I used to with Xcode 7.With Xcode 7 I could build the MAS version, launch it, and my app would detect there wasn't a valid MAS receipt, exiting with -173. This would cause the OS to put up a login dialog and I could enter a test account and password registered with iTuneConnect. A MAS receipt would then be added to my app and I could launch it after that and test it.With Xcode 8, my app won't even launch. This error is printed to the system log:Oct 30 13:30:56 com.apple.xpc.launchd[1] (com.mycompany.myapp[54628]): Binary is improperly signed.When I type codesign -vv into Terminal, my app is valid on disk and satisfies its Designated Requirement.I think the problem is the binary is signed with my 3rd Party Developer Application certificate, and the provisioning profile that allows MapKit access wants the binary to be signed by Apple. So it's impossi
Replies
3
Boosts
0
Views
610
Activity
Oct ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1” part 2
Thank you...I'd spent a couple of hours working this problem before I stumbled upon your post. As I read it, it occured to me that just before the Command /usr/bin/codesign failed with exit code 1 error, I'd added a file to my project's scnassets.Thank you again.
Replies
Boosts
Views
Activity
Nov ’16
gdb 7.12 sierra unknown signal.
GDB 7.12 worked fine (codesigned) on macOS 10.11.On macOS 10.12, it fails miserably with During startup program terminated with signal ?, unknown signal.Checked certificate and codesigning status, nothing changed.Rebuilt from SourceForge, reinstalled/resigned, nothing changed.Disabled SIP, nothing changed.Looks like a macOS bug to me. Any ideas?I fortunately did not upgrade my MAC, just tested it in a Fusion partition. I will be rejecting Sierra until it's fixed.
Replies
1
Boosts
0
Views
5.2k
Activity
Nov ’16
codesign ask me 34 times to access
Hi guy,why Xcode ask me for many times to access the keychain and other times only ones or twice?and if I click on 'consenti' (in English 'allow') pop up other codesign prompt. I've counted there are 34 requestscome out.how can I solve this problem?these are two screenshot about problem
Replies
2
Boosts
0
Views
4.9k
Activity
Nov ’16
Reply to Confusion about access groups and iOS extensions.
I presume you’re working on iOS (or watchOS or tvOS) here; if you’re developing for the Mac, things are more complex.You can think of the keychain as a database table, where rows in the table are keychain items and columns are various keychain attributes. One of those attributes is kSecAttrAccessGroup, the access group of the item. Here’s how things break down by API: For the query APIs (like SecItemCopyMatching), if you don’t supply kSecAttrAccessGroup in the query then it does a wildcard search, returning all items you have access to, that is, whose access group is contained in your app’s effective keychain access group list.OTOH, when your query contains a value for kSecAttrAccessGroup then: that value must be listed in your app’s effective keychain access group listitems are returned if their access group matches that valueWhen you create an item (SecItemAdd), if you don’t supply a value for kSecAttrAccessGroup then its access group is set to the default keychain access group.OTOH, if you do supply a valu
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Nov ’16
Reply to Xcode 8 on 10.12 codesign segmentation fault
I'm also having this issue ever since upgrading from 10.11.5 to 10.12 yesterday. I'll get one of two errors, which one seems to be random.I'll either get that Segmentation fault: 11... Or I'll get an error complaining about ambiguous code sign certificates, and the two certificates it lists are actually the same certificate! If I delete the certificate, it complains about not being able to find it. But then when I add it to my login keychain, it complains about ambiguous certificates again.This happens when codesigning in the terminal or from Xcode, in both Xcode 8.1 and Xcode 7.3.
Replies
Boosts
Views
Activity
Nov ’16
Command /usr/bin/codesign failed with exit code 1
Hi there! I'm a visual artist, and I am trying my darnedest to create a sticker pack for iMessage. I have a brand new, up to date iMac with the newest Xcode installed. I created my sticker pack, but when I tried to test it on my iphone, I got the error message Command /usr/bin/codesign failed with exit code 1Every subsequent time I tried to run it, whether on my phone or in the simulator, the build failed and I get the same message. Does anyone have any idea what this means or what I can do to fix it?Thank you!!
Replies
1
Boosts
0
Views
437
Activity
Nov ’16
Reply to Linking embedded framework with other dynamic framework fails when build & run on device
Based on the log message, it appears that Other.framework is not codesigned. How was it created? It needs to be signed. You can probably workaround this by signing it manually yourself for now, but you should provide more detail about how it's getting built because it should be signed automatically.codesign --force --deep --preserve-metadata=identifier,entitlements,resource-rules,requirements,flags,team-identifier --sign - /path/to/Other.framework
Replies
Boosts
Views
Activity
Nov ’16
Reply to Xcode 8 can't archive “Command /usr/bin/codesign failed with exit code 1”
Hi ,Im Also having the same problem . Tried both as above but still have the issue.Os :10.12.1Xcode :8.1after 8.1 Update only im having this issueError:Signing Identity: - /usr/bin/codesign --force --sign - --timestamp=none /Users/keerthi/Library/Developer/Xcode/DerivedData/Voxer-garanexqxxqsaxfshffbufgifwcd/Build/Products/Debug-iphonesimulator/DBChooser.bundle/Users/keerthi/Library/Developer/Xcode/DerivedData/Voxer-garanexqxxqsaxfshffbufgifwcd/Build/Products/Debug-iphonesimulator/DBChooser.bundle: bundle format unrecognized, invalid, or unsuitableCommand /usr/bin/codesign failed with exit code 1If Anyone found solution please share .
Replies
Boosts
Views
Activity
Nov ’16
Want to sign .dmg file on osx with my apple developer certificate
codesign --force --sign iPhone Distribution: me (...) AA.dmg=> this works, dmg file is signed, but when I open it AA can't be opened because it is from an unidentified developerwhereas the certificate was applied correctly and is in my keychain; the root CA is Apple CAWhen I verify the dmg:spctl -a -t open --context context:primary-signature --verbose=4 -v AA.dmgAA.dmg: rejectedorigin=iPhone Distribution: me (...)So how can I sign my dmg file so my customers will have no warning ?
Replies
1
Boosts
0
Views
2.8k
Activity
Nov ’16
SAT Driver couldn't be loaded from Sierra
Hello guys,I'm leading Portable SSD(T1/T3) Project in Samsung Electronics. Recently I've asked to look into issue that our security software is not working after upgarding to Sierra. The root-cause of this issue I've found is Opensource SAT driver which we provided couldn't be loaded due to codesigning version - According to your developer guide for codesigning, version1 driver loading is not allowed from the Sierra. However, there was no version2 sigining when we signed that driver. This makes our customers inconvenient.Therefore, I'd like to ask something to address current situation.1. Is there any reason to block Driver loading which is signed with Version 1 based from the Sierra? I guess this was due to security improvement. But would like to know exactly2. I tested some different MAC PCs, it does not have problem with iMAC PC with Sierra version, but MacBook Air shows failure to load this driver. This is a little bit different scenario from my expectation. Might be Gatekeeper setting i
Replies
0
Boosts
0
Views
302
Activity
Nov ’16