codesign

Jenkins vs. Xcode plugin - codesign troubles

六眼飞鱼酱① 提交于 2019-11-27 16:29:26
问题 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. 回答1: Everything is ok with Jenkins plugin. Just product settings is incorrect. Open the "Build Settings" tab of your project. Searched "Code Signing Resource Rules

iOS8 Dynamic Frameworks -> CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.3'

这一生的挚爱 提交于 2019-11-27 14:39:06
问题 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

Is there any way to get key hash from signed APK?

让人想犯罪 __ 提交于 2019-11-27 11:22:21
Is there any way to get key hash from signed APK? We have a signed Android apk file, and we want to find out key hash of this APK, for Facebook SDK. Can we do that by something like jarsigner? Any suggestions? amalBit For windows users getting the key from openssl, may be tricky some times.. I always use this to find the right signature.. Just paste this code in your onCreate() and run. // Add code to print out the key hash try { PackageInfo info = getPackageManager().getPackageInfo(getPackageName(), PackageManager.GET_SIGNATURES); for (Signature signature : info.signatures) { MessageDigest md

Xcode won't let to build for Device after denying Codesign to access Keychain

混江龙づ霸主 提交于 2019-11-27 11:14:33
I'm new to iOS development and today I tried to check my app on my iPhone and tried to build it for the device. So when I clicked on build, it asked to type my password to let codesign to access keychain. But after few attempts, I accidentally clicked on deny button. Then after again I tried to build my app for the device and now it says, Swift sodlib tool error, task failed with exit 1 signal 0 And when I check that error it says, unknown error -1=ffffffffffffffff error: Task failed with exit 1 signal 0 { /usr/bin/codesign '--force' '--sign' 'A6646CD79C82476C1C35598A10134D3171EE09CD' '-

Error when trying to obtain a certificate: The specified item could not be found in the keychain

耗尽温柔 提交于 2019-11-27 10:54:30
I was having a problem with codesigning my apps, so I deleted all the keys from the keychain. Then I went to Certificate Assistant => Request a certificate from a Certificate Authority (to create CSR for a new certificate). So enter my email address and here's what I get: The specified item could not be found in the keychain. What am I doing wrong? P.S. When I'm trying to Create a Certificate Authority , I get the same error. Francesco I solved it. Ensure you are in the "Certificates" section and you select "Apple Worldwide Developer Relations Certification Authority" before requesting a

iPhone CodeSign failed

天大地大妈咪最大 提交于 2019-11-27 08:44:30
问题 So - I am a registered iPhone developer (Having paid my $99/year). I have followed all the steps provided by Apple to get the provisioning and code-signing files. However, when I click 'build', it says: "Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)" I have re-downloaded all of the certificates and profiles repeatedly, and it still won't work. However, if I click 'build' (and it says codesign failed),

codesign “The operation was cancelled by the user”

核能气质少年 提交于 2019-11-27 03:47:21
问题 For some reason, whenever I try to codesign in xcode, I am getting this error (path to app): The operation was cancelled by the user. Command /usr/bin/codesign failed with exit code 1 回答1: I had this error after I changed my login keychain password, and my developer certificate was in this keychain. I restarted and unlocked the keychain again and all was well. 回答2: I spent hours trying to figure out why I was getting "The operation was cancelled by the user. Command /usr/bin/codesign failed

Building iOS applications using xcodebuild without codesign

此生再无相见时 提交于 2019-11-26 22:31:26
问题 We're building an app for another company. They hold the signing key and would rather not share it with us. It should be possible to separate build and sign, but how do I specify it on xcodebuild's command line? 回答1: In order to skip the code signing you can perform a manual build from the console like this: xcodebuild clean build CODE_SIGN_IDENTITY="" CODE_SIGNING_REQUIRED=NO Additionally, use the -configuration , -target and -sdk parameters in order to define your build settings. Refer to

Xcode won't let to build for Device after denying Codesign to access Keychain

狂风中的少年 提交于 2019-11-26 22:20:15
问题 I'm new to iOS development and today I tried to check my app on my iPhone and tried to build it for the device. So when I clicked on build, it asked to type my password to let codesign to access keychain. But after few attempts, I accidentally clicked on deny button. Then after again I tried to build my app for the device and now it says, Swift sodlib tool error, task failed with exit 1 signal 0 And when I check that error it says, unknown error -1=ffffffffffffffff error: Task failed with

Command /usr/bin/codesign failed with exit code 1

眉间皱痕 提交于 2019-11-26 21:57:51
I have the following error: Command /usr/bin/codesign failed with exit code 1 Here is what I already did for trying to fix this: set the bundle identifier to com.server.pgmname set the code signing to "Any Iphone OS Device" set the Code Signing Identity to my Distribution identity. The error only occurs when I try to build on my device, on the simulator everything works fine. Do you have any suggestions? I had the exact same error, and tried everything under the sun, including what was suggested elsewhere on this page. What the problem was for me was that in Keychain Access, the actual Apple