Apple certificates CER file to CSR - ios

I am a little lost in apple certificates and what I need. I created development certificate, some profiles and so (for my use). Now I am adding some features to existing app which creates someone else but it's my job now and for next I was asked for giving UDID and creating CSR file. UDID is clear but how can I create CSR file? I should give it and then I get provisioning profile from other person. I hope it's clear. So how can I get CSR for my development profile?

From what I understood you already have provisioning profile. Provisioning profile is something that connects certificate (developer) with UDID's (allowed devices) and bundle identifier (app identifier).
If you have valid provisioning profile (contains your device, correct app identifier etc.) you only need to set it to be used in xcode under build configuration.
If you really need CSR (certificate signing request), something that is used to generate new certificate - you use keychain for that (Keychain access -> Certificate assistant ...). You can find detailed information on CSR generation in memeber center of iOS developer program (Certificates, Identifiers & Profiles -> Certificates -> + ). From some time handling of provisioning profiles is almost automatically handled by Xcode when you try to build app for your device.

Related

iPhone has denied the launch request - On provision profile

A company that I am developing a project for, gave me a .mobileprovision file and a .p12 certificate to add APNS to their project. As long as I've added their provision profile to my project in XCode, XCode keeps saying "iPhone has denied the launch request." when I try to build project on my physical device.
I've tried deleting certificate Apple Worldwide Developer Relations Certification Authority, and adding another user account to mac but non of them worked. Only when I disabled Debug executable, the app launched successfully, but it's not a solution because I need to debug the app.
Should I tell them to add my device UDID to their account's devices on developer.apple.com?
You've been given an Adhoc distribution provisioning profile, which don't allow the debugger to attach (they're missing the get-task-allow entitlement), as they're for use when you distribute your app for testing, not local development.
If you need to debug, they'll have to supply you with a development p12 certificate and a matching provisioning profile.
You are trying with Development Profile vs Distribution Profile?
Distribution Profile:
With AdHoc Distribution profile, you can't debug any app it should be used for distribution only.
Development Profile:
If you didn't add your device UDID to the provisioning profile, you can try to do that and re-generate the provisioning profile and download it.
In Keychain Access, you will get to know which profile you received from the team,
gave me a ".mobileprovision" file and a ".p12" certificate
That seems like a red herring. I would suggest ignoring both of those. If they want you to work on their app, they simply make you a team member. Done! Your own dev center membership is then sufficient to debug on device.

Do the distribution profiles come from distribution certificate?

The client has given me the distribution profiles, how can i add the profiles in xcode 5?
As far as i know distribution certificates are responsible for distribution profiles. Importing distribution certificate enables and add all the distribution profiles in xcode. Without certificate distribution profiles can't be used.
Please correct me if i am wrong and suggest the work around for importing profiles in xcode 5.
Deployment phase is new for me.
Thanks
Importing the profiles is just double clicking on them. You can't use the profile without the private key for the certificate that was used to generate the profiles. This need to be exported from the keychain (usually as a p12 file) and imported onto your development machine.
It is possible that the client exported a package containing all of this info using Xcode, then double clicking should install everything required.
Importing distribution certificate enables and add all the distribution profiles in xcode
No, importing one doesn't automatically import the other.
There are no workarounds, you need to be supplied with both the certificate (private key) and the profiles.
A distribution profile is basically a way to make a trust relationship between a particular distribution certificate (which identifies your organisation as a registered Apple development organisation), a particular app or group of apps (identified by an AppID like com.foo.bar.myawesomegame), a set of valid devices where the app can be installed (in the case of ad-hoc distribution; in the case of App Store distribution this is not required), and a set of enabled services, like In-App Purchases.
In your particular situation, if the client wants to test your app, and you are provided with a valid distribution provisioning profile (a file with .mobileprovisioning extension), you also need to install a valid distribution certificate on your computer. The client can download this certificate from http://developer.apple.com (Member Center) and send it to you so you can import it on your machine with a double click on the .cer file.
To enable external users test an app, there's a simpler process, providing that your organisation is a registered Apple development organisation: First, you generate a distribution certificate from http://developer.apple.com. Then, you create a distribution (ad-hoc) provisioning profile and add the distribution certificate and the UUIDs of the iPhones the client wants to use for testing. The client can get the UUIDs from the iTunes app, for example. Then, you can download both the certificate and the distribution profile to your computer, double click to import them into Xcode, and finally sign the app (.ipa file) so that the client can test it on their own devices. You can do that by choosing Product, Archive in Xcode and selecting your distribution certificate and provisioning profile.

Trying to Upload iOS App, Can't Archive

I made an app and am trying to upload it to iTunes Connect. I have a certificate installed, development certificate and distribution certificate...see picture..
...But, somehow, when I am trying to archive the app in Xcode to binary, it reports an error:
All my certificates are valid, but it's still complaining about distribution certificates,
What am I missing?
You don't appear to have a distribution profile (only a developer profile -- in organizer). You appear to have a distribution certificate, but no profile. You must create a distribution profile for your app. You can do this in the portal.
Did you generate the certificate on your own Mac? The certificate must match a private key in the keychain. If not, revoke the existing certificate and create a new one. You will have to perform the signing from Apple again.

iOS ad hoc distribution with .p12 from customer

I have an app developed and working with our company's profile and distribution cert. I just recieved the .p12 from the company that we are going to be distributing to, and am trying to rebuild the app with their certificate. However, when I select 'Archive' I receive
"No unexpired provisioning profiles found that contain any of the keychains signing certificates"
I believe I'm missing something here, but google and I can't figure it out. Do I need a new profile with that certificate in it? If so how do I go about uploading the .p12?
Thankyou very much.
With the p12 you are enabling your computer to make releases for the outside company but what you need right now is the provisioning profile associated with that app (it will be specific if you have in app purchases or push notification otherwise it will be the default developer profile) and that .p12
Check out your keychain, distribution certificate has key. If not then install right certificate.

Problems validating iOS App build

I'm working with a developer to create an iOS App for a client. I created my certificates, provisioning profiles, etc, and then sent it to the developer to build the App. They have then sent me back the build as an .xarchive file, which I have loaded up into Xcode.
On the Archives tab, I then go to validate it, but the developer certificate I created in iTunes connect is invalid.
I created both my developer and distribution signature inside the same iTunes Connect account, and they're both loaded up in Keychain along with my WWDR certificate.
Make sure you downloaded and dragged your provisioning files to XCode as well.
When producing a build using a Distribution Certificate you need to make sure that you have a properly generated Distribution Certificate in the iOS Provisioning Portal. Select the Certificates -> Distribution tab and make sure you have a distribution certificate listed. If there is one and you do not have the original private key on your machine, you will need to obtain the private/public key pair from the original machine, or revoke and recreate the certificate.
Also, make sure you have created a Distribution provisioning profile and that it is being used in conjunction with this Distribution Certificate.
Also, check to be sure you have a distribution provisioning profile for your app for app store.
Other problems include the App ID differing from the Bundle Identifier and it has trouble associating it with the provisioning profile. Most commonly when the Bundle Identifier is derived from the ProductName and the case of the characters doesn't match the case of the characters in the App ID on the provisioning portal.
You can get around this by typing in the bundle identifier into the AppName-info.plist file.
I finally worked it out! I had the right certificates, but had only created a development provisioning profile. I created this in iTunes Connect and then it worked perfectly. Hope this helps someone else who has a similar problem.
Easiest way to ensure you have everything I needed is to remember that you need separate certificates and provisioning profiles for development and distribution. They can all be created in iTunes Connect, and you just need to download them and run the file to ensure Xcode finds them.

Resources