I am currently having some problems regarding provisioning profiles on the dev centre. In the past, I have been able to successfully create and deploy apps on internal app stores and on multiple devices. I have never run into trouble when trying to sign my apps. However, since the last update on the dev-portal, I have not been able to create new provisioning profiles - which is becoming a big problem.
I have successfully created an app id, com.xx.USApp and created a certificate for it: com.xx.USApp just as I did for all my other apps in the past. However, when I go to "Provisioning Profiles", I am unable to create a profile for any App ID (not even for the previous apps). When I try, I am able to select an App ID, then on the next screen, this message pops up: http://i.imgur.com/grEcut5.png
It is telling me to create a certificate, which I have already done - as can been seen here: http://i.imgur.com/ouW7LKo.png
I have even tried to make additional ones through the links they have provided me, however whenever I go back to the Provisioning tab, the same message occurs. In the past, I was taken to this dialog: http://i.imgur.com/QnP5X3s.png which then gave me a list of all my certificate files. I am wondering if this is a bug in their update and how I would go about resolving this issue.
Thanks!
Apple has decided to move the place where you setup provisioning profiles to the member center. That could be the problem. Not sure why they moved it. Try adding it from the new member center.
There was a problem with their servers when trying to create provisioning profiles. They have since fixed this issue.
Related
Over the past couple of days I've worked my way through all the prior posts on here that I could find that seemed to be related (many of them appear to be horrifically out of date and less than useful now), as well as the Apple Troubleshooting and Maintaining Your Signing Identities and Certificate guides (not to mention the usual Internet searches).
The app in question was deploying fine until the latest XCode update, but now fails to upload (build is successful obviously, and there have been code changes as well):
ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle *content removed* is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
It's not the first time I've mysteriously had a failure like this, but in prior cases simply revoking the certs, removing the profile, then rebuilding would take care of it. Not so in this case.
The provisioning profile is confirmed to be the correct type, and the code signing certificate sure looks like it's in there... Certificate gets a nice green checkmark too. Any new suggestions not covered in the usual places?
It turns out that there's nothing wrong with the certificate itself, but it's the upload process which needs to be done different.
In the past I had been deploying the distribution outputs from Cordova CLI via the Application Loader. The App store no longer accepts my builds when done that way.
With the current version of XCode, I need to use the GUI now and set the build target to "Generic iOS Device" and then do an "Archive" operation. The archive will upload the app through a different loader, which the App store will accept.
I get this error when trying to validate, now theres tons of these questions, the problem is, none of their solutions have worked.
The top highlighted one is my distribution provisioning file thats associated with the project in question.
you can even see it's online.
so I have the profile, I have the app ready for uploading (how do you change the date for when it can be available on the app store AFTER you have said "yes these details are right, now lets get ready to upload?").
But I can't validate. every time I log in to "validate" I get that error. I have all the profiles required I have tripple checked every thing, but being VERY NEW to IOS dev, I am sure I missed some crucial step.
Please help.
1) Have you created a Distribution Certificate and downloaded it?
2) Have you created App Store provisioning profile?
3) Are the code signing identities have been properly setup in your project?
If yes to the above then try manually downloading the provisioning profile from the developer portal and restarting XCode.
I'm trying to get my XCode to run apps on my iPhone.
A while ago I tried to do that just from within XCode (knowing nothing), and it complained about how my Apple ID wasn't set up with a developer account. Fair enough.
Now I do have a developer account (I'm a member of an organization). As soon as I got the enrollment email I followed their instructions about setting up the certificates and adding it to my keychain and whatnot.
Then I followed these instructions to try to get XCode set up. When I got to the part about using my device for development, that button wasn't there. But as the instructions say:
If the device was used for development in the past, the “Use for Development” button may not appear. If this happens, click “Add to Portal” at the bottom of the screen instead.
So I clicked "Add to Portal", a provisioning profile appeared in the list, and everything seemed good. I then proceeded to the "Code Sign Your App" section. This is what I see:
I expected there to be a section for iOS Team Provisioning Profile: * or something. And, of course, this means that when I try to run my app it fails with a code signing error.
I've poked around with deleting and re-adding stuff, but this is where I always get stuck. I can provide more information, I just...don't know what you want. How do I proceed?
Thanks.
You can try CMD Shift 2, going to the Devices tab, and refresh the provisioning profiles and/or the team. It should ask you to log in - and hopefully will update your profile for you.
If it doesn't, it's the same every time. Your device needs to be added to the devices on the portal by a team admin. You said you have a certificate. If not using the team provisioning profile, you have to add your certificate to the profile you are using. Then make sure to quit xcode and reopen it after the changes.
Download the certificate and mobile provisioning profile from the developer site. Then double click them to add to your keychain / organizer.
To make a long story short: I have developed an application for a company and I was about to update when I discovered that in the member center area on the Apple website the Development Certificate was gone, as well as the devices and other stuff, so I made a new one and uploaded the device ID again.
So everything okay...I thought. I opened iTunes and downloaded the new provisioning profile and dragged it over to the organizer window. But it did not work. I got several different warning and errors saying the the keys, certificates etc did not match, so I Googled. I saw some posts that said: try making a new distrubution certificate...so I did, then xcode told me that I had to many certificates for that app so I exported the certificates by right clicking the selected certificates in the keychain and tapped export. I ended up with a Certificates.cer file. Then I deleted those certificates to make room for the new ones i downloaded from the member center portal.
SO now I do not know what I have done...I am afraid that I screwed something really up.
My question is: I really hope it is still possible to update the application already in appstore even though I have to recreate the certficates, provisioning profiles etc.
Best regards
You can alway start from scratch, deleting all the provisioning profiles through your developer member page, recreating the profiles you need, importing them in Xcode and rebuilding the app with them. You cannot screw things that much, not being able to publish the app once again.
Clear all the contents of Xcode, and of your provisioning profiles page, and start over. Things will work. I've done this tens of times.
So we all need to deploy our applications to real iPhones for testing purposes. I'm sure you much like me have found a group of sucke^H^H^H^H^H testers to help you out with this process. Whenever you want to send a build out to a new person this requires adding the new device id to your ad hoc provision. This part is fairly painless. The trouble starts when trying to get Xcode to use the new provision file.
Whats the best way to get Xcode to pickup and use the new provision first time? Ideally I would like to do this without changing the .xcodeproj file.
I've done this as follows, with good success:
Send out call for beta testers.
Respond to each with "in order to beta test, I need your UDID. You can send it to my by following these instructions..."
Folks incapable of sending UDID are told "thank you for your time, but beta is no longer taking applications."
If too many people can't figure it out, review your instructions.
After several days, make a batch provision file with all the people in beta.
I name the devices after the person's email address, i.e., mikeATexampleDOTcom.
I name the provision after the beta program, i.e., Neko-beta-1.
Build the app, provision & deliver (with non-technical installation instructions!)
For stragglers, you can either build another provision, or add them to the existing one, or tell them "beta's full."
Then...
After a few days, send email asking how its going, if they have any difficulties, etc.
~3 days before end of Beta, email saying "beta is coming to a close, please be sure to return your questionaires."
After close of beta, be sure to thank everyone, even those who did not reply.
How to automatically build an IPA file from XCode: http://www.idotcom.us/2009/05/how-to-build-a-ipa-file-from-xcode/
Step-by-step explanation of how to build an IPA file to send out via ad-hoc. You do have to change your XCode project but this way you create a separate target so it doesn't affect your main project.
What I do now is create a new provisioning profile if the devices change. Even if you modify an existing one, it is essentially a new profile with a different ID, but a new name. Then testers' iPhone fill up with provisioning profiles with the same name :)
Yes, it means changing your Xcode project file each time, but in my experience it's more reliable.
If you do keep the same name, beware of Xcode's cache of provisioning profiles, which can create a mess with builds. Your best bet is to remove of all the provisioning profiles from the Organizer window, as well as deleting the files in ~/Library/MobileDevice/Provisioning Profiles. Then restart Xcode and reimport the provision profile.
I haven't been able to do this without changing the .xcodeproj file, but that's probably because I've had terrible luck getting things to work without going through the whole "build clean, deselect the provisioning profile, reselect the provisioning profile" process.