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

Answer 1

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.

Answer 2

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.

Answer 3

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.

Answer 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.

Answer 5

This is a little easier now.

1. You go to the app itunesconnect and login
2. click "certificates"
3. Provisioning Profiles / Distribution
4. generate a profile,
5. download the profile
6. double click it

Answer 6

1. Visit Member Center

2. Go to "iOS Provisioning Portal" -> "Certificates" (Left sidebar) >> "Distribution" tab

3. Check field "Provisioning Profiles". If empty, next (4)

4. Go to "Provisioning" (Left sidebar) -> "Distribution" tab. Press "New Profile" and complete it. Go back to (3) check the field again.

5. Download and "run" (double click) the new provisioning profile.

6. In your project's build settings select the NEW provisioning profile (it might have the same name as the old one)

7. 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)

8. Verify that your bundle ID is correct (CaSe SeNsEtIvE)

9. 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.
     
     

10. Validate or distribute your app again. It should work.

11. 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.

12. 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.