13

I am trying to create a distribution profile. From scratch I deleted every certificate at KeyChain. I removed all provision profile using terminal method. I closed my Xcode. Then I followed this link to create the distribution certificate and profiles. I followed the step correctly and I got the following results. I keep getting "No signing certificate"IOS development found" Please help.

Edited

I then created the Development certificate following this link and now I get different certificates name for Development and Distribution. My error is Distribution Provision Profile doesn't include signing certificate iPhone Developer xxxx xxxx

Please help, thanks.

pic2

Pic 1

pic 5

pic 3

pic4

pic 6

After creating the development profile

After creating the development profile

Why is my certificate different name for development and distribution, I followed the steps to create certificate. Why is it different name?

pic 8

pic 9

Community
  • 1
  • 1
Hanz Cheah
  • 761
  • 5
  • 15
  • 44
  • You cannot use the same certificate for development and distribution. That is why they are different. Also, your "Signing (Debug)" profile should be your iOS Development provisioning profile, "SFITNESS Develop". – wottle Apr 24 '18 at 20:31
  • Also, is there a reason you are not using Automatic code signing? – wottle Apr 24 '18 at 20:32
  • Xcode still believes the "SFITNESS Distri" profile is an iOS Development profile. I would delete all your provisioning profiles from the Xcode location (https://stackoverflow.com/a/45642752/3708242) quit Xcode, redownload the iOS Distribution provisioning profile and open it (it will launch Xcode). Something is out of sync with your profiles and certs. – wottle Apr 24 '18 at 20:40

3 Answers3

46

FOR DISTRIBUTION CERTIFICATES

On BuildSettings make sure you pick "IOS Distribution" instead of "IOS DEVELOPER" in the "Code Signing Identity" dropdown:

enter image description here

Fidel
  • 1,173
  • 11
  • 21
1

You have the certificate and provisioning profile for iOS Distribution. You are trying to do a build for development (building to a test device), which will require you to generate a certificate and profile for iOS Development. Follow the steps you did, but when you need to specificy what the certificate is for, choose iOS Development. Also, when you create the provisioning profile, select iOS Development. It is actually the next article on the site you were using: http://lessons.livecode.com/m/4069/l/308242-how-do-i-create-a-development-profile-for-ios

The iOS Distribution certificate / profile will be used when you want to submit to Apple for testing through TestFlight, or for distribution in the App Store, so don't worry about deleting those.

wottle
  • 13,095
  • 4
  • 27
  • 68
  • I am trying to put it to the App Store already finish development, do I still need to create a development provisioning profile? – Hanz Cheah Apr 23 '18 at 13:54
  • If you are trying to go to the app store, it is pretty risky to do so without testing it on a physical device. You need a development profile to do that. Technically, however, to build for the app store, you only need the distribution profile. What are your code signing settings for your project under Signing (Release)? What are you doing to create your app store build? – wottle Apr 23 '18 at 14:15
  • I actually did create a development provisioning profile and tested it on physical device. I deleted it temperorary because I want to focus on the distribution provision profile and send it to the App Store for test flight. However I keep getting the error. Anyway sorry I only can update you about your question in another 10hours later coz the pc is not with me. – Hanz Cheah Apr 23 '18 at 14:43
  • OK, but the main problem is whatever you are doing to build the app think it should be doing a development build instead of a distribution build. You need to make some changes either to you code signing settings, or your scheme to ensure you are trying to do a release build. – wottle Apr 23 '18 at 14:50
-3

I had the same problem and I solved it just checking the configuration of certificates and provisioning.

Check if they are using correct provisioning profiles

And check if they are using the correct reference in code signing

That's what worked for me...

Julio Effgen
  • 9
  • 3