codesign

Hello,after updating to Xcode 7.3 (From 7.1 i think) i got the following error when i try to run my app on the simulator:Installation FailedInvalid argumentand when i try to run it on my iphone i get:Command /usr/bin/codesign failed with exit code 1does somone know a fix for that problem ?

I'm running Xcode 7.3 with Server 5.1 on El Capitan 10.11.4. My bots no longer product ipa's. Archives are being created successfuly. The build service error is as follows:Assertion: Running task was terminated because it produced no activity for more than 600 seconds (use sudo xcrun xcscontrol --configure-integration-timeout to increase this timeout)I've done a lot of research on this issue and it all seems to point to the certificate needing permission before it can be used to codesign the application. Basically it stalls waiting for input from something before it will proceed. A solution to this in the past was to set the private key for the certificate to Allow all applications to access this item. However, if I understand it correct, the Server now uses the Portal keychain to sign these builds and I cannot get access to that to make this modification to a private key.So how does Apple intend users to create .ipa's from Bots? Has anyone else had this issue?

Hi,We're using cURL to communicate with a server with mutual authentication (server and client-side certificates). The application runs on OS X 10.7 and newer. We're using CLion, not XCode for development.Before we signed our binary the following dialog popped up every time we did client side authentication via (CURLOPT_SSLCERT)http://i.stack.imgur.com/IAjtV.pngOnce signed, the dialog is not shown on 10.8 or newer. However, when on OS X 10.7 the dialog is shown despite the binary being signed, but now with only the text Do you want to allow access to this item?We sign the binary as follows (the .pfx used for codesigning is previously imported into the keychain):> codesign -s Our Identifier path/to/binaryfileWhen running (both on 10.7 and 10.11)> codesign --verify -v path/to/binaryThe result is> binaryname: valid on disk> binaryname: satisfies its Designated RequirementSo it seems the code signing is valid also on 10.7 - is this just different behavior on OS X's part? Can

I am working on a Mac app which works with iCloud KVS & CloudKit container of my iOS app which is already in production. All works fine when I run the app from Xcode directly. However, I need to Archive > Export and move it to the /Applications folder because it seems (?) that's the only way how the system picks up Safari Extension Companion. Otherwise, when running straight from Xcode or exporting just as a Mac app (without codesigning), safari.extension.companion always returns null in my extension code.Now, on one hand, when exporting the app, I need to choose Developer ID codesigning as noted in Safari Extension programming guide.On another hand, Developer ID doesn't support iCloud capability which is reserved for Development-codesigning and so I am supposed to export it as a Development build as noted in CloudKit programming guide.But how do I export a build of my app including both of these capabilities?When I export using Development codesigning, I can't launc

When I open my app's signing with codesign -d --ent :- <app path> I see the iCloud entitlement:codesign -d --ent :- /Users/jwanner/Library/Mobi/Provisioning Profiles/dc54d0d9-2d09-4767-bb0a-df4b886b0e94.mobileprovision/Users/jwanner/Library/MobileDevice/Provisioning Profiles/dc54d0d9-2d09-4767-bb0a-df4b886b0e94.mobileprovision: code object is not signed at allCampwood-Mac:~ jwanner$ security cms -D -i /Users/jwanner/Library/MobileDevice/Provisioning Profiles/dc54d0d9-2d09-4767-bb0a-df4b886b0e94.mobileprovision<?xml version=1.0 encoding=UTF-8?><!DOCTYPE plist PUBLIC -/<plist version=1.0><dict> <key>AppIDName</key> <string>Xcode iOS App ID com quipzl Quipzl</string> <key>ApplicationIdentifierPrefix</key> <array> <string>PTXZTRRTHH</string> </array> <key>CreationDate</key> <date>2016-03-30T20:57:45Z</date> <key>Platform</key> <array> <string>iOS</string> </array

Hey guys,I stumbled on a weird problem in my CI machine and I'm not sure how to debug it - when I try to `codesign` my iOS app the command crashes (but returns status code 0), later when trying to view the code signature using `codesign -d -vv <path_to_.app>` the command crashes as well.The problem exists in our CI machine which uses fastlane to build and export App Store IPA file, the command that crashes during the build process is -/usr/bin/codesign --force --sign <signatureid> --entitlements /Users/billguard/Library/Developer/Xcode/DerivedData/BillGuard-dmgbviswkecvtmaanmmdqmvnjqlc/Build/Intermediates/ArchiveIntermediates/Prosper Production/IntermediateBuildFilesPath/BillGuard.build/Release-iphoneos/Prosper Daily.build/Prosper Daily.app.xcent --timestamp=none /Users/billguard/Library/Developer/Xcode/DerivedData/BillGuard-dmgbviswkecvtmaanmmdqmvnjqlc/Build/Intermediates/ArchiveIntermediates/Prosper Production/InstallationBuildProductsLocation/Applications/Prosper Dail

We have an application users can download from the web. This was working fine until 10.11.4. Now users are getting warnings that it is from an unknown developer. We did not have a V2 signature, so today I went through and made the modification to make it a V2 signature and we are still unable to pass GateKeeper checks.When I execute: codesign -d --verbose=7 <myapp>I get:Sealed Resources version=2 rules=12 files=83Internal requirements count=2 size=232However when I execute:spctl -a -t exec -vv <my app>I get:Double Click to Install.app: rejectedsource=obsolete resource envelopeorigin=Developer ID Application: AutodeskI have tried reducing the app and signing again. No luck. The application passes Gatekeeper checks on all other OS version. Any ideas?

I am running XCode Server on El Capitan with new XCode 7, I have three Repositories and three in House Apps. I want XCode Server to automatically sign these apps with the enterprise certificate.This had worked for one day and suddenly all bots are stucking at Signing Product... A short research results in codesign does not have permission on your certificate but IT HAS PERMISSIONS AND IT IS IN THE SYSTEM KEYCHAIN.What else can I do to allow xcode bots to sign my product?

The short story: tested with a default Xcode command line tool that says Hello World.1) Build a command line tool on 10.11.3 and sign it with my Developer ID. Everything is fine.2) Test it on 10.11.4 and spctl gives me an obsolete resource envelope error.The deeper problem that this causes:My app is built on 10.11.3. It is a prefPane with one command line tool and three app bundles (four helper tools) in it's bundle. I am getting GateKeeper warnings on 10.11.4 systems, but not on anything else. It is manually codesigned with my Developer ID... first the helper tool frameworks, then the helper tools themselves and then the prefPane. So everything is signed from the inside-out.In terminal (on two different machines running 10.11.3) I get:spctl -a -t exec -vv My.prefPane /Volumes/Path/To/ source=Developer ID origin=Developer ID Application: My Company, Inc.codesign --verbose=4 --deep --strict My.prefPane /Volumes/Path/To/ /Volumes/Path/To/ In terminal (on two different machines running 10.11.4) I get:sp

Hello,On OS X 10.11.4, I compile and codesign my application. I am using QT 5.5 and macdeploy, in addition to codesign.Then, I verify using both:codesign --verify --verbose myApp.appspctl --assess --type execute myAppbefore I create the myApp.dmg disk image.Everything is ok on OS X 10.11.4, when I open the disk image and copy myApp.app on the mac.However, on a mac running 10.10.5, when I try to open myApp.app, I get the following error:myApp.app is damaged and can't be opened. You should move it to the Trash.I checked with the RB App Checker Lite and I don't see any error.I had a previous version done in November 2015 which works perfectly on both OS X 10.10 and 10.11.Am I missing something basic?Thanks for any help