codesign

Hello,im developing iOS app and im having problem with codesigning distribution version. First of all, im working through macincloud.com which is a virtual mac so im not able to plug in an actual iOS device to test it neither with development signing nor ad-hoc signing.Anyway, I created my distribution signing certificate aswell as provisioning profile but Xcode somehow cant see my distribution certificate.When i try to archive the app it says:No provisioning profiles containing one of the following signing identities was found:iPhone Developer: XXXXX YYYY (ZZZZZZZ) (SHA1: XXXX...).which is my DEVELOPER signing certificate, so it says it sees only this certificate but since im using my DISTRIBUTION provisioning profile it doest match. if I go to keychain and delete this cerificate then Xcode says:No valid signing identities (i.e. certificate and private key pair) matching the team ID “XXXXXXXXXX” were found.after hitting fix issue it only tells me that is cant create new provisioning profile beacuse

When I try to submit my app with the new seed Xcode 7.1 beta (7B60) I receive a weird error by which it complaints that there is No account with iTunes connect access, while of course the account is there and kicking as you may see in the linked screenshot. I already had to delete all my profiles and restore them again in order to be successfully codesigned, now this. Please tell me how I may fix it.http://www.inarrivo.net/iTunesError.pngI also tried entering a new techical role following a hint on StackOverflow, apparently now needed. But that is all but ignored when I try to submit the app.You may check the thred with the images at:http://stackoverflow.com/questions/32592291/on-xcode-7-i-keep-receiving-error-no-account-with-itunes-connect-access/32592581

Hello!I am using the EV (Extended Validation) code signing certificate issued by DigiCert (https://www.digicert.com/code-signing/ev-code-signing.htm) to sign code. The certificate and corresponding private key are stored on the eToken.I am signing successfully Mac OS X applications with following command:$ codesign -s Open Joint-Stock Company BIFIT -v -f nmBIFITAppnmBIFITApp: replacing existing signaturenmBIFITApp: signed Mach-O thin (x86_64) [nmBIFITApp]And verify:$ codesign -vvd nmBIFITAppExecutable=/Users/borodavkin/2sign/macosx/nmBIFITAppIdentifier=nmBIFITAppFormat=Mach-O thin (x86_64)CodeDirectory v=20100 size=4662 flags=0x0(none) hashes=228+2 location=embeddedSignature size=4775Authority=Open Joint-Stock Company BIFITAuthority=DigiCert EV Code Signing CA (SHA2)Authority=DigiCert High Assurance EV Root CASigned Time=17 сент. 2015 г., 19:02:16Info.plist=not boundTeamIdentifier=not setSealed Resources=noneInternal requirements count=2 size=264However, I can't sign the installation package

Sep 20 13:35:35 Davids-AppleWatch installd[35] <Error>: 0x1f084000 -[MIInstallableBundle performVerificationWithError:]: 1044: Upgrade's application-identifier entitlement string (ZNVB52L2P6.nz.co.DavidGWilson.TrafficCamNZ.watchkitapp) does not match installed application's application-identifier string (Q9T4XA67S6.nz.co.DavidGWilson.TrafficCamNZ.watchkitapp); rejecting upgrade. Sep 20 13:35:35 Davids-AppleWatch installd[35] <Error>: 0x1f084000 -[MIInstaller performInstallationWithError:]: Verification stage failedmy id is: ZNVB52L2P6I have no idea what this is: Q9T4XA67S6This Application is in the AppStore. It's there now with iOS support and Apple Watch support (Watch OS 1).I’ve converted the Xcode project from Watch OS 1 to Watch OS 2. Changed some code (a minor amount) for the OS update and depreciated functions.It’s working in the simulator…And… falls in a heap for the device installation.- iOS application installs just fine- Watch OS application installs and is then uninstalledAnyone been he

I'm working on a feature for a design mac app that allows designers to export a standalone viewer app that has their design embeded in it. The exported viewer app could then be sent to clients for review. Currently, the feature works by copying a viewer app embeded in the main app's bundle to the user's desktop, and then copying the design file into the viewer (~/Desktop/Viewer.app/Contents/Resources/designFile)This works great, unless the client doesn't have the allow apps from anywhere security setting turned on. If I enable codesigning for the viewer app, codsigning is broken by copying the design file into the app's resources folder. Pre-mavricks you could specify files that codesign should ignore, but this is no longer possible. So my quesiton is this: is there some other way to make this viewer app so that it's codesigned?

HiyasSince upgrading to XCode 7 I don't seem to be able to submit a testflight binary to the Appstore anymore. I get this:Invalid Signature - The binary with bundle identifier 'ch.abacus.RMFoundation6' at path [RMFoundation6.framework] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target.for one of my dynamic (iOS8) frameworks. I had to change Bitcode flag on all frameworks and the binary since at least one of my third party frameworks is not enabled for Bitcode, but that's all I had to change when upgrading. I didn't get this message when submitting from XCode 6.4 last week though.When I verify the app using codesign