I have a provisioning profile, which allows for Push Notifications and I spent a long time working getting it right. I finally figured it all out and push notifications work! Now I am updating the same app for some reason I cannot choose the right profile. When I choose a profile to submit with, I cannot pick the right profile
But here it is when I click on accounts in Xcode!
It's INSchoolLawPushNotificationsProduction.
I have found the file and double clicked it, dragged it onto Xcode on the dock, everything. I have tried other Xcode Projects, nothing except the profiles in the first image are showing up! What do I do?
Please double check the followings
Check if your identifier are same in profile and in app.
Make sure you select the profile in settings also select the right certificate.
When you are going to upload you choose the same account which you used for the to create profiles and certificate.
Your production provisioning profile has expired (it did so on 9/15/2015). You cannot use an expired profile.
Log back into the the developer site and create a new distribution profile.
Also, you're developer profiles will expire in a couple of months - may as well create new versions of those as well.
Since the update to Xcode 6, I am having problems with validation of my app: see screenshot.
I have no idea, what this means, and what I can do...
Note: I do have valid profiles in Xcode and in the Dev Portal, and I can run the app from Xcode.
Please advice
It means that either you have no valid provisioning profiles installed or you haven't selected the correct ones in your target's build settings.
Go to your target's build settings and look at Code Signing and its Provisioning Profiles fields.
Select the correct provisioning profiles for your schemas and after you do that look at Code Signing Identities fields and make sure that the identities for each schema match the provisioning profiles.
Check out for the developer accounts in your Xcode preferences.
If you are a member of multiple teams then choose the correct team from there and if one of the account's developer info has been changed then remove that account from your Xcode preferences.
Try to remove the additional developer accounts of previous clients if there. I had this.
Also pressing the cancel button and doing it again by quitting Xcode or choosing Import Developer Profile from the above screenshot can help you.
In my case it worked for me.
Hope it helps you too.
I am seeing this issue too - everything was working fine pre xcode 6.
EDIT - In my case, under code signing, the selection was set to distribution. I clicked into this and saw I had two distribution options (one for a developer account and one for enterprise). Explicity setting the correct one here solved the issue. It seems xcode 6 introduces a change to the automatic selection behaviour. Hope that helps!
Hi, I recently upgraded to Xcode 5.1 now I can not find Provisioning Profile in Projects->Target->Code Signing section of settings. Before Xcode 5.1, I used to change Provisioning Profile to desired profile from Provisioning Profile option then it starts to appear in code signing identity debug or release section as shown in image below.
But now I am not given this options in Code Signing so I can't change the debug or release profile it only show automatic or identities in keychain.
How an I change to the desired provisioning profile?
Update:
I tried using the 000000B-0000-0000-0000-000000000000 UUID code at User Defined Provisioning Profile and it accepts and build and displays Provisioning profile at Code Signing. But it is not resolving Provisioning profile name at User Defined Profiles.
I was stuck with same issue and finally got it done here u can look for the following screen shots..
go to Code signing in the build setting and change the Provisional Profile NONE to the provisional profile you like to test
then change the Code signing identity to test your Application on device with the suitable bundle identifier look for the following screen shot
If you find this Answer is correct then Vote up lets other also can solve their problem.
Thanks
Make sure you have 'all' and not 'basic' display mode selected.
I filed a bug on this. You can manually do it but a pain in the rear. This to me is a huge bug. I hope they fix it soon.
Login in Apple Dev website and go to the profile list view, then download the profile and double click to install, then you can see it in Code Signing list.
Check your bundle Id and make sure that you have installed your required profile.
Then Click on Provisioning profile option and select a profile(see the option below code signing identity).
Now you need to select certificate under code signing identity.
To be sure:
Our team encountered an afternoon of frustration trying to open an app or update an app compiled with Xcode 5.1 on iOS 7.1 device with a tardy profile. Download and install a new profile (as necessary) then:
Make sure the BUNDLE IDENTIFIER in Xcodeʻs GENERAL view for your project matches what the profile reads on your Dev web portal, and then THAT profile is installed in Xcode verbatim. Select that profile in your BUILD setting, and you could be solved by now (the App installed on devices without issue), but we also noticed we could to go back to GENERAL view and the FIX button actually worked: it fixed the "not found" profile
Try by creating an archive. I attached an iphone and tried to create an archive which result in no provisioning profile error. But now the option in the target to select a provisioning profile was there from which I was able to choose the provisioning profile
Had this problem, just had to open Preferences and refreshed the screen under Accounts - View Details.
The provisioning profile had no options for me. I had registered for the Apple Developers program recently. I followed these steps and then clean and build. It worked.
Import User to XCODE
I have an error "No identities are available for signing" when try to validate my app in Xcode 5. I tried all: Recreate certificates and provisioning profiles, all methods which have been described on this site and another resources; I'm confused, because when I try to distribute my app as Ad-hoc, it successfully create and install on test device an IPA file. But when I try validate my app or submit to AppStore, all the time I have an error. Maybe someone can help me with this issue.
All you need to do is:
go to Certificates, Identifiers & Profiles in the Developer Center
create a new provisioning profile in "Provisioning Profiles" / "Distribution"
download the profile and open it
restart Xcode
Please make sure you are using distribution provisioning profiles, rather than Development.
And the code sign setting in Xcode is compatible with the distribution provisioning profiles.
The validation process does not work with Ad-hoc profiles. Need to create a Distribution provisioning profile. It is not specified in the instructions for beta testing. I agonized all day until realized.
Use the Application Loader (Xcode -> Open Developer Tool -> Application Loader).
Also - this answer/question may also be helpful for you:
https://stackoverflow.com/a/18914073/730172
Restarting Xcode solved the problem for me! Restart and/or clean solves 99% of all issues...
#CainaSouza 's comment above worked for me. I didn't even have to create any new provisioning profiles.
I just had to go to Xcode > Preferences > Accounts > (Apple ID) > View Details and hit the refresh button. After a minute or two it was done and had loaded my provisioning profiles. I didn't even have to select it in my project options, it had already selected my most recently generated one.
Clean your Product Build Folder (with Alt button)
Restart Xcode
It solved my same issue
I had a similar issue. Found out that the bundle identifier did not match the app id that was on itunes connect - it was capitalized differently. Fixed the issue by making the identifiers match.
Yes the appID and bundle identifier must match. Remember it is CASE-SENSITIVE. That was the problem for me.
I updated to Maverick and Xcode 5 and had the same issue even though I had everything ok in Profiles. I created a new Distribution profile (identical to the old one), added it by refreshing profiles and the issue was solved without rebuilding.
Apple Decided to "Magically Dissapear" my distribution provisioning profile from their site after upgrading to a newer Xcode, giving me this problem too.
Solution is obvious only once I had discovered this fact!
-Create new Distribution Provisioning Profile
-Download & install it / Refresh Xcode preferences under account details
I fixed this issue by delete the old development/distribute profiles and create new one with new names.
I had a mismatch between the Bundle Identifier within Xcode and the App ID on Developer.Apple.Com (Certificates, Identifiers & Profiles). This StackOverflow post was a great help to me. For a little extra info check out this blog post. The official documentation for the touch command can be found here. I had quit Xcode before doing the below. Upon completion of the details below and reopening Xcode my issue was resolved.
Use a text editor to update the bundle identifier to match the App ID, the Info.plist file is located:
ProjectName > ProjectName > ProjectName > ProjectName-Info.plist
Your looking for the following lines:
<key>CFBundleIdentifier</key>
<string>MyCompany.${PRODUCT_NAME:rfc1034identifier}</string>
Update the value to match you App ID, eg:
<string>com.MyCompany</string>
Use the terminal to issue the touch command, ensure your within the above listed directory:
touch ProjectName-Info.plist
If you are using Xcode 5.1 or above (which you would be now), this helped me: Code signing broken on Xcode 5.1 + iOS 7.1
The key is to delete the old provisioning profile on your mac and create a new one (with a different name?) from Apple web site and download it. Looks like Xcode 5.1 corrupts the existing provisioning profile and it does not help even if you re-download it again.
My solution was to go into the dev center, find the distribution provisioning profile, and it had expired. So i tapped edit on it, and renewed it, downloaded it, installed it, chose the profile in the build settings, and it worked.
HTH someone.
Of all the development issues I've faced over my 20+ years as a software developer, none have wasted so much time as the code-signing/provisioning profile rubbish in Xcode.
This week, I have wasted 8+ hours trying to build an Ad-hoc release of our iPhone app. In the past, it just worked, I could Archive, stick a download button on our in-house webpage, and users could just install our app from this page.
But, this week, I was facing the same "No identities are available" issue, described here.
EVENTUALLY, here's what solved the issue for me:
When I logged into the hopeless Apple Developers website, it showed that our company had 2 "iOS Distribution" certificates. They were valid, their expiry dates are months away, and in the Keychain Access application, the certificates were installed and valid... no problems here.
But what fixed my issue was to delete these two certificates, recreate a new one, then recreate my "In house" Provisioning Profile (as the original one was now showing as being invalid, as it used the old "iOS Distribution" certificate).
I also went into the "Keychain Access" application on my MacBook, and deleted all "iOS Distribution" keychains.
Then, I downloaded the new certificates & provisioning profiles, now, finally, Xcode would report that there was an identity which I could code-sign with.
To the Xcode development team:
Please. Get this fixed.
If a developer like myself, is up against a wall, unable to get a valid Provisioning Profile, which will result in a downloadable app, which will fail each time on "The app couldn't be downloaded at this time" message.. DON'T allow the Archive function to be used.
Instead, TELL the user what the problem is. HELP them resolve it, rather than going through the motions, and happily allowing them to create Archives which will never be useable.
And if an Ad-Hoc install is invalid, please put something in the Log to explain what's gone wrong, and make this accessible from Xcode. Currently your "The app can't be downloaded at this time" message is both useless and misleading.
One last thing (if this helps):
Our company accidentally let its Developer Enterprise Program license expire last month. We did then renew, everything was seemingly okay again, but perhaps, behind the scenes, this messed up our "iOS Distribution" certificate ? And perhaps, not. From the Apple website's point of view, everything was fine.
My issue was that I had none.myApp in my Bundle Identifier whereas in the AppID, I had com.myApp.
This drove me crazy for hours.
I ran into this issue today and it seems to be related to the face that the profile started with a number. I deleted the profile and recreated it exactly the same way (after a lot of other troubleshooting steps found on SO) EXCEPT this time I started with a word instead of a number. Coincidence? Not sure but worth trying.
Had this yesterday and could not figure it out, no matter what I did! To solve the problem, I went to both the Project and the Target in Xcode, and under code signing, chose
Code signing identity: Don't code sign
Provisioning profile: None
Build, and then Product > Archive, and now Organizer chose the correct code signing identities and profiles to allow it to get to the Validation step. Woohoo!
It happen to me after update Xcode.
I fixed doing the follow
change the sign in to "no sign"
restart Xcode
set it to the correct sign
re-archive the build
I hope it helps
Apple Documentation
"If Xcode doesn’t find signing identities, a dialog stating “No identities are available for signing” appears. Verify that you have a distribution certificate and an ad hoc provisioning profile before continuing.
If your ad hoc provisioning profile doesn’t appear in the Provisioning Profile pop-up menu when you create the iOS App Store Package, refresh the profiles in Xcode, as described in “Refreshing Provisioning Profiles in Xcode.”"
In my case, the adhoc provisioning that I wanted to set was not selectable in Code Signing in Build Settings. Though, I created and downloaded the adhoc provisioning from developer store. The answers mentioned here didn't work for me. Fix Issue button in General tab fixed the issue by downloading the required adhoc provisioning file by itself.
Creating a new certificate, Profile in Apple development center did not work for me! I tried editing a profile/certificates and download again and double click to install in KeyChain, but still did not work. I restarted XCode (Version 7 and Mac on El Capitan), restarted Mac but still did not work!
What worked for me is:
XCode -> Preferences -> Accounts - Then I deleted the Apple ID.
Shutdown my Mac, and restarted it.
Started my XCode, added the Apple ID, went to view details in Apple ID's and downloaded the Provisional Profile again and only then it started working!
Restarting solved my problem. I have a new mac and tried downloading the profiles, which should've transferred anyways. restarting solved it.
Have just noticed that Apple redesigned iOS Dev Center this weekend.
I need to add a couple of devices to an existing Ad-Hoc provisioning profile. But when I push Edit button, I can change only Name and App ID.
Is it any way to do it except of the obvious one: to delete the existing profile and create a new one with all required devices?
UPD.
Now I can edit the list of devices for development profiles, but not for distribution.
UPD. 2
Can edit devices for new distribution profiles, but can't do it for old.
It Works!
Apple fixed it. So it was a bug. Now you can edit your embedded device list, even if it's an Ad Hoc distribution profile.
I looked into this on the forum and found a reference to the new App Distribution Guide. You need to delete your old profile and create a new one. You'll be given the choice at that time to add devices to the new profile. The feeling is that Apple has changed the format of the profile and this is a way of forcing you to recreate a new profile in the new format.
It seems you can't edit it (generate button isn't enabled) if for example you have underscores in the profile name.