codesign

I got a reply on my SO post that fixed this for me http://stackoverflow.com/questions/37801465/codesign-failed-on-10-12-sierra/38071473#38071473Launch Keychain Access, go to Preferences... and click Reset My Default Keychain

I'm hitting this error Every Time, and it only happens after I re-sign my app.Essentially I build my app Ad-Hoc with an Ad-Hoc profile to use for internal testing and such (and the inital build works perfectly), and then I re-sign the app for production (also adding the beta entitlements at that time). Once it's re-signed, the app will run perfectly on newer devices (64bit, iPhone 5S and up), but gives a startup crash on older devices (32bit, iPhone 5 and down).Jul 7 11:01:02 Company-iPhone-4S SpringBoard[48] : SecTrustEvaluate [leaf IssuerCommonName SubjectCommonName] Jul 7 11:01:02 Company-iPhone-4S SpringBoard[48] : SecTrustEvaluate [leaf IssuerCommonName SubjectCommonName] Jul 7 11:01:02 Company-iPhone-4S SpringBoard[48] : SecTrustEvaluate [leaf IssuerCommonName SubjectCommonName] Jul 7 11:01:02 Company-iPhone-4S securityd[86] : secTaskDiagnoseEntitlements MISSING keychain entitlements: no stored taskRef found Jul 7 11:01:02 Company-iPhone-4S securityd[86] : secTaskDiagnoseEntitlements MISSING keychain en

I have the same issue - I tried adding a different CFbundleIdentifier to the plist file but I am unable to change the Identifier of the jre/bin/javaI codesign the jave executeable using terminal, my signing key and a plist file similar to the steps at this post http://stackoverflow.com/questions/20856864/how-can-i-code-sign-a-bundled-executable-file-in-a-mac-app-using-xcode5. Everything works except this duplication of the Bundle Identifier.I am not the only one with this problem CFBundleIdentifier Collision - The Info.plist CFBundleIdentifier value 'net.java.openjdk.cmd' of 'java' is already in use by another application http://stackoverflow.com/questions/34613483/itms-90511-cfbundleidentifier-collisionPlease assist in how to change the CFBundleIdentifier or is it not something that can be changed?If I force the change using codesign -s (Vertificate) - i (A new budnle indetifier) then the java executeable becomes useless...@sselvia1 how did yo manage to fix this?

>and don’t have to rely on XCode 5.1.1.Point is, it's not your call. Xcode 6.x is the minimum allowed when doing store submittals now, so if that's your goal, you don't have a choice but to walk away from Xcode 5.x. >And, also how do I transfer the signing identities if they are revoked?Revoked/expired/invalids aren't transferrred, they are renewed.Many things have changed for codesigning since 5.1.1 was originally used, including the recommended preference of automatic provisioning. I suggest you get busy w/Xcode 7.3.1, and deal with details as they arise.

xcconfig might be a way for you to override the configuration.According to the WWDC 2016 talk on codesign changes, you are supposed to provide DEVELOPMENT_TEAM & PROVISIONING_PROFILE_SPECIFIER if you want to customize code signing. They said not to specify the identifier. You also don't want to specify the exact provisioning profile (uuid) since it can change. I do think the specifier is the way to go. So, based on your team id and the specifier, it's should figure out which provisioning profile to use automagically.I think it can be done by having something like this in your .xcconfig file//:configuration = Release DEVELOPMENT_TEAM = XXX111AAA PROVISIONING_PROFILE_SPECIFIER = My Release Provisioning Profile //:completeSettings = noneI got these lines of text by configuring to what I'd like in Xcode and Ctrl-C on those items in the build settings screen. I guess those comments do mean something in .xcconfig context.