No identities were available - administrator request

Question

I had problems while "archiving" my app. I think there are invalid profiles because of iPhone Update to 5.1 and XCode update to 4.2.2.

I've taken now more than 4 hours to get rid of certification issues while using this thread step by step 3 times (which costs a lot of time):

Getting "A valid signing identity matching this profile could not be found in your keychain" warning

I still have the following fault: XCode certification error

No identities were available An administrator must request identities before they can be downloaded.

The "Download identities" button went back to this window after processing some seconds.

Do you know how to get out of this wood of certification documentations and solve that fault?

I've checked for case sensitivity and could not find any problems. I've recreated all today with ID of "master" which should work. — Nasenbaer, Apr 19 '12 at 07:33
http://stackoverflow.com/questions/9643057/app-store-submission-no-identities did not help in my case — Nasenbaer, Apr 19 '12 at 08:03
Could someone update this for XCode 5. Every single solution on here does NOT work in any way shape or form anymore. Apple blew everything out of the water. — user1318747, Jan 20 '14 at 00:51

score 154 · Accepted Answer · edited Sep 17 '15 at 08:11

Visit Member Center
Go to "iOS Provisioning Portal" -> "Certificates" (Left sidebar) >> "Distribution" tab
Check field "Provisioning Profiles". If empty, next (4)
Go to "Provisioning" (Left sidebar) -> "Distribution" tab. Press "New Profile" and complete it. Go back to (3) check the field again.
Download and "run" (double click) the new provisioning profile.
In your project's build settings select the NEW provisioning profile (it might have the same name as the old one)
In your project's build settings update your code signing identities (all of them) to the new one if there is one. (The old one was probably expired which is one of the biggest causes for the error message you saw)
Verify that your bundle ID is correct (CaSe SeNsEtIvE)
Back to XCode Organizer - Devices. Click TEAM (Left sidebar) and click "Refresh" (right-bottom). You will find XCode fetch the new profile. If new content loaded, repeat steps 6 and 7 (they will have been changed!)

*If you can't find team because you are running a newer version of xCode, go to Xcode preferences (clicking "Xcode" on the mac toolbar on the top left corner of your screen) and go to account, select your team and click refresh. If new content loaded, repeat steps 6 and 7 (they will have been changed!)

If you are in Preferences -> Accounts and you still can't refresh, then:
- Click on the Accounts tab
- Select an Apple ID in the list
- Click "View Details" on the bottom right
- Click on the refresh arrow on the bottom left
- Xcode will now refresh the updated credentials, and you can proceed to validate or distribute your app.
Validate or distribute your app again. It should work.
If this didn't work then go to "TEAM" under project settings > targets and select "none"... Now that you have selected None you will need to repeat step 7 and change the code signing identities (all of them) and try archiving again.
Lastly, if none of the above worked. Simply create a new production certificate AND create a new provisioning profile with the same bundle ID. (Yes, this will work if you are updating an app that is already live). Download the cert and prov. profile and run both (double click). Now repeat step 6 and archive. This should work.

additional in XCODE the selection is needed to do in project where the provisioning item needs to be selected. thanks for your help. — Nasenbaer, Jun 28 '12 at 22:13
I was still getting this error even though everything looked fine UNTIL I pressed Refresh in step 5. Then it was sorted.... — Greg, Apr 12 '13 at 20:07
@Takol and what if there is no "TEAM" (left sidebar) or "Refresh" (bottom-right) button??? — stephen, Dec 08 '13 at 07:51
**Important:** You can't validate with only an ad-hoc distribution. You'll (also) need one for the App Store. — Brian White, Apr 20 '14 at 02:26
Brian White is right. But this response is quite right in normal error cases. — CesareoAguirre, May 07 '14 at 09:57
I can't make any sense of this answer. Could you go a bit more in depth in every step? I followed every step and I am still getting the exact same error as the question provided above. — Timothy Swan, Aug 11 '14 at 19:14

score 17 · Answer 2 · answered Dec 19 '13 at 22:29

17

@Takoi's answer is correct. However, with my latest version of Xcode, there is no TEAM option in the Devices section of the Organizer. I had to do the following instead to refresh the credentials:

Go to Xcode->Preferences
Click on the Accounts tab
Select an Apple ID in the list
Click "View Details" on the bottom right
Click on the refresh arrow on the bottom left

Xcode will now refresh the updated credentials, and you can proceed to validate or distribute your app.

Hope this helps!

answered Dec 19 '13 at 22:29

BooTooMany

1,192
12
19

1

ugh, went through about 100 SO posts and this solved my issue. WHY DOESN'T APPLE AUTO REFRESH! – John Riselvato Feb 17 '14 at 05:32
Oh, gosh! That was a solution what I was waiting about hour. Thanks. – Vyacheslav Apr 16 '14 at 19:21
I still get the same exact error as the question states. – Timothy Swan Aug 11 '14 at 19:16

score 4 · Answer 3 · edited Nov 15 '13 at 16:06

4

Make sure the bundle id in your .plist file in XCode is the same as the bundle id in itunesconnect, if it's off, it won't be able to match the archive to the profile on itunesconnect when validating/distributing.

edited Nov 15 '13 at 16:06

Danny Yaroslavski

492
4
13

answered Jan 10 '13 at 14:17

Wasi Shah

41
1

score 3 · Answer 4 · answered Jan 01 '14 at 21:03

3

This is a little easier now.

You go to the app itunesconnect and login
click "certificates"
Provisioning Profiles / Distribution
generate a profile,
download the profile
double click it

answered Jan 01 '14 at 21:03

bobobobo

64,917
62
258
363

2

This solved my problem in XCode 5. Although I think it should be [linkg](https://developer.apple.com/membercenter/), 2. is "Provisioning Profiles" and you have to create a profile for **App Store** Distribution. I only created one for **Ad Hoc** (Testflight) and the error kept showing up until I created another for the App Store. – Steffen Wenzel Jan 20 '14 at 09:10
1

There are no certificates in itunesconnect – Dvole Jun 20 '14 at 22:09
1

There is no 'certificates' link in itunesConnect. :( – ed_is_my_name Aug 13 '14 at 15:57

deko · Answer 5 · 2014-07-19T13:56:34.677

3

I am a member of 2 teams and had the same problem while uploading one of the projects.
Changing General -> Identity -> Team to None in project settings (XCode 5) allowed me to upload the application to iTunesConnect.

Screenshot is here

edited Jul 19 '14 at 13:56

answered May 21 '14 at 15:02

deko

2,534
3
34
48

There is no Identity in General settings in Xcode! What to do? – Dvole Jun 20 '14 at 22:11
@Dvole, It's not XCode General settings, but Project settings. See the screenshot in my updated answer. – deko Jul 19 '14 at 13:53

score 2 · Answer 6 · answered Jan 16 '14 at 14:38

My certificate had expired which resulted in my provisioning profile being expired.
Once I -

Updated my certificate on the iOS web portal
Clicked Edited on the provision profile
Selected the new certificate and clicked generate
In Xcode I refreshed my provisioning profiles

Error went away

score 2 · Answer 7 · answered Sep 13 '14 at 17:33

2

I guess it is written somewhere in the stream, I did not read all in detail. I just want to emphasise on this point:

Due to an annoying xCode behavior, once you've set up everything, you HAVE TO clean the project and Quit xCode.

Then relaunch and build. Now you know if it works or not.

answered Sep 13 '14 at 17:33

Moose

2,607
24
23

Still observing this issue with xCode 6.1, one year later. In some cases, when you reload your developer certificates, you also may have to restart your mac. Perhaps due to Keychain cache. Just to say if you think everything is correctly set, but nothing works, Reset all! – Moose Dec 12 '14 at 17:22

score 1 · Answer 8 · answered May 23 '12 at 03:23

It looks like you're going to have to request another developer cert. Go to the iOS dev center website and go to the provisioning portal. Click the certificates tab and follow the directions. https://developer.apple.com/ios/manage/certificates/team/howto.action

To be clear, you're problem doesnt seem to be provisioning related, it's specifically the developer cert. if you do get another cert, you'll have to create all new profiles to sign your apps with.

what is this, there are ways of fixing it! – user1432813 Jul 11 '12 at 10:59 — user1432813, Jul 11 '12 at 10:59

score 1 · Answer 9 · answered Jan 16 '14 at 13:38

1

My bundle identifier was named differently. I had to change it from Nyquist.GasBro to com.Nyquist.GasBro which is what I had in the provisioning profile.

answered Jan 16 '14 at 13:38

seantomburke

10,514
3
18
23

score 1 · Answer 10 · answered Sep 13 '14 at 08:17

None of previous answers helped me, so I post my issue.

Dev Center: Certificates, Identifiers & Profiles > Provisioning Profile > Distribution

Make sure that there is a distribution provisioning profile, and App ID in it is exactly the same as Bundle ID of your app in Xcode (Project Settings > General > Identity > Bundle Identifier).

Xcode: Project Settings > Build Settings > Code Signing:
- Provisioning profile - choose that Distribution provisioning profile name (not Development!)
- Code Signing Identity - I choosed Automatic since I have only one.

P.S. Before doing this, I deleted all unused and expired provisioning profiles and signing identities from Dev Center and from Xcode. Then, refreshed as mentioned in other answers: Xcode: Preferences > Accounts > (my Apple ID) > View Details > Refresh.

score 0 · Answer 11 · answered Jun 08 '13 at 00:26

The answer that you are looking for is that when you generate the certificate request for COMMON NAME you need to put your HUMAN NAME as in John Smith, not your app name. Apple uses this term Common Name in 2 different ways and doesn't tell you that the certificate is supposed to have your name on it whereas in another area they ask for common name and want the APP name.

score 0 · Answer 12 · answered Feb 06 '14 at 10:37

0

I had the same problem. Nothing mentioned on this page did not work for me until i was deleted everything from archive. After that problem disappear.

answered Feb 06 '14 at 10:37

slobodans

859
1
17
23

score 0 · Answer 13 · answered May 07 '14 at 09:55

For those who says that the Ad Hoc Distribution profile wont work this year 2014, I have to agree.

In Build Settings locate the Code Signing setting: for Release choose your Store Distribution and then select Menu>Product>Archive.

Later, in the Organizer Window, select your archive and clic in Validate. It will let you select the Ad Hoc profile and validate... then select Distribute, it will let you save as .ipa file.

No identities were available - administrator request

13 Answers13

Linked

Related