codesign

My company uses one build machine (a Mac Mini) as a CI node to build our iOS app. We currently build an Ad-Hoc and an App Store config on the mini. We've recently enrolled in the Enterprise Program and want to start building an Enterprise config as well. However, our build process now fails, because we now have two certificates called "iPhone Distribution: Widget Corporation". One is the distribution cert for AdHoc/AppStore, and one is for Enterprise (Apple calls it In-House). I've tried modifying the mini's keychains such that one cert is in the login keychain and one is in a new keychain

I'm trying to set up continuous builds/integration for a stable of iPhone apps. I have: A dedicated Mac Mini. A user account named "build" Hudson set up as a LaunchAgent for build, by dropping a plist in /Users/build/Library/LaunchAgents Tried as a system-wide LaunchDaemon running as hudson, but then had no access to the build user's login keychain. Long story, full of heartache. The system set to automatically login "build" on startup, so that Hudson starts running. The big problem is codesigning and the Keychain. We create code on behalf of our clients' developer identities, so we have

Instead of going to Extension Builder > Build Package… , I'd like to built a .safariextz package from the MyExtension.safariextension folder. I know I can unpack an extension with xar -xf . I suspect the way back involves packing it with xar , but then I'll need to do the code signing thing, which may or may not involve codesign(1) . Here are Omar Ismail's instructions, omitting the need for separate shell scripts. This will all occur in a directory safari/ , where we will be signing the directory safari/appname.safariextension/ to become the extension safari/appname.safariextz . The first

I am trying to run an automated xcodebuild on Jenkins, but I am running into the error User interaction is not allowed. Command /usr/bin/codesign failed with exit code 1 I have already referenced "User interaction is not allowed" trying to sign an OSX app using codesign and other similar threads, but none of the solutions seem to properly remedy the error. Here is what I've already tried: I have allowed all items to access the keychain, and I have specifically added codesign to the "always allow" list (as done here https://stackoverflow.com/a/22637896 ) I have set the keychain to not

I'm working with Xcode 4.1 build 4B110f trying to get my iOS app ready for upload. It passes the Product|Archive step with no errors, asking twice for permission to sign something. But when I try a validate of the archive from the Organizer, it fails: ### Codesigning '/Users/uqrchern/Library/MobileDevice/Provisioning Profiles/70D2381D-3733-4F5D-88B2-4729572C2864.mobileprovision' with 'iPhone Distribution: Ron Chernich' + /usr/bin/codesign --force --preserve-metadata --sign iPhone Distribution: Ron Chernich --resource-rules=/var/folders/ul/ula1AHKnGpqQ9ftDnUL-l++++TM/-Tmp-/rybczU3EBd/Payload

I have updated to OS X Yosemite and also Xcode 6.1 (downloaded from the developer site), from this time I have had the problem with the building as in the log file I see the note "Warning: --resource-rules has been deprecated in Mac OS X >= 10.10!". Does someone know how to use Xcode plugin without "resource-rules" flag? Thank you. Julius Lisauskas Everything is ok with Jenkins plugin. Just product settings is incorrect. Open the "Build Settings" tab of your project. Searched "Code Signing Resource Rules Path", it was empty for me. Change to: $(SDKROOT)/ResourceRules.plist credits goes to

I am using the iOS8 Dynamic Frameworks that I build myself and link within my iOS app. It was working fine in the simulator and on device, but when trying to archive a Release build for it, I keep getting this error: Code Sign error: No matching provisioning profiles found: None of the valid provisioning profiles allowed the specified entitlements: com.apple.developer.ubiquity-kvstore-identifier, keychain-access-groups, com.apple.developer.icloud-container-identifiers, com.apple.developer.icloud-services, com.apple.security.application-groups, com.apple.developer.ubiquity-container-identifiers