Xcode - Non matching & non expired provisioning profiles found - free dev account - ios

Non matching & non expired provisioning profiles found
I've been working over this issue and came across SO threads and I have not succeeded till now.
First off all, I'm using a free developer account so I am not able to login to the developer account portal and manage certificates and profiles.
I did not face any problem till now, after that I upgraded to Xcode 7.3.1
I am able to run the app on simulator but not on a real device
i am able to create a new project and run it on a real device, this only affects projects that I had created prior to upgrade
After that:
- Checked that certificates were valid under keychain access
deleted account from Xcode > preferences > accounts > appleIds
navigated to appleIds > view details : ensured that provisioning profiles were downloaded and non expired
deleted existing provisioning profiles from provisioned profiles directory and then created them again
cleared all profiles, deleted the account, recreated the account, triggered product > profile
verified that my iOS development cert is valid and did not create in Xcode
restarted Xcode at every stage of this process, as per multiple threads

For all of the posts I've seen, I'm sure this will help someone out there.
Go to project build settings > code signing > code signing identity
check that the provisioning profile you've made is set.
after I did this, I was still receiving an error. this time for entitlements. I browsed to project > capabilities > health kit (where the issue was) and found a 'fix issue' button. This solved the second half of the problem. good luck out there

Related

Provisioning profile becomes invalid everyday

I have recently renewed my developer certificate and I’m using Xcode 7. I’m using the same developer account in four different Macs. But ever since I renewed my certificate, the next day morning my all my apps pointing that certificate is crashing and when I log into my developer account I’m finding all my profiles invalid. This happens everyday. Things I’ve tried are
Deleted the App ID and recreated it (did not work)
Removed all old profiles from the Mac and Developer account (did not work)
Deleted my iOS Development Certificate and created again (did not work)
What I’m doing these past days is Edit the profile and choose my Certificate everyday.
Any help?
I delete the same AppID Development Profiles but keep one that managed by Xcode.Then I open the Xcode and enter the "Setting" > "Accounts" > Choose the developer account that I used > "View Detail" > Signing Identities:iOS development "Reset" > "DownLoadAll". then it is OK.
Remember:if you let Xcode manage your certificates,just make sure that "one AppID, one development Profiles".

Provisioning profiles status invalid (managed by XCode)

Suddenly all my provisioning profiles are in status Invalid (managed by XCode). Why?
Also I remember in XCode 4 that you always had to create your provisioning profile. Now XCode autocreates your provisioning profile for development. Is this a new feature on XCode 6?
I had the same problem today.
In the Apple Developer website, all of my company's Provisioning Profiles were marked as "Invalid (managed in Xcode)". None were out of them were date, none were using iOS Certificates which had expired, and the website gave zero suggestion that anything was actually wrong.
The solution, ridiculously, was to delete my perfectly valid iOS Certificates, and recreate them.
We write in-house apps aswell as apps for the App Store, and Apple (quietly) refuses to let you have more than 2 of these at once. So I was unable to create a third iOS Certificate which would allow me to use the "In house and Ad-hoc" option, hence the need to delete an iOS Certificate first.
Once I had pointlessly recreated the "iOS Certificate", the Provisioning Profiles came to life.
Part 2 of this farce is to go into Xcode, and delete your Provision Profiles (XCode \ Preferences \ select your iOS Certificate \ View Details, then select all of your provisioning profiles, right click and select "Move to trash".
At this point, absolutely nothing will change, and you'll think you've done something wrong.
But then, if you then quit Xcode, and go back in, then you'll see the Provisioning Profiles will have disappeared.
Now you can re-download the Provisioning Profiles from the Apple Developers website, and redownload the latest versions.
Until Xcode 7.2 comes along, and breaks something else.
(Seriously, I spend more time fighting with Xcode bugs than writing code..)
Apple introduced Xcode Managed profiles in Xcode 5 as a way to try and make the provisioning process less cumbersome and get Developers sending code to their devices without having to go through the manual upload/setup/download/install/build process. In effect, Xcode was completely automating the entire provisioning process whenever there was a code sign error detected. For developers that had already wrestled with understanding Provisioning, this new behavior was frustrating as the processes those teams put in place were unintentionally being wrecked by Xcode's best attempts to be helpful. That said, it is better today but not as transparent as it should be when it comes to affecting your Certificates, Identities, and Profiles data. If you are't familiar with what all is included in a provisioning profile or signing identity, there's some related reading you might want to skim: What are code signing identities?
Suddenly all my provisioning profiles are in status Invalid (managed by XCode). Why?
The most common reason for a profile to move to the "Invalid" state is because at least one of the profile's registered test devices has been deactivated / removed from the developer's account. By doing so, all profiles that included that device UDID are marked as invalid and require regeneration. This can be accomplished in Xcode > Preferences > Accounts, clicking 'View Details' on your Apple ID account, and then clicking the refresh button in the lower right corner of that account details screen.
Also I remember in XCode 4 that you always had to create your provisioning profile. Now XCode autocreates your provisioning profile for development. Is this a new feature on XCode 6?
As stated in the start of this answer, no. Autogenerated provisioning profiles were introduced in Xcode 5 and the workflow has been refined several times since Xcode 5.0 and modern Xcode. If you allow Xcode to assist you with Code Signing error messages, its default position is to check the validity of your development or distribution certificate (depending on what kind of code sign operation you were trying to do), check the validity of the AppId and Provisioning Profile, and revoke then reissue whichever part of the signing identity is in error.
Really it messing up on me. it destroyed my 4 hours fighting with Xcode. At last created another new provisioning file with selecting appleID as iOS Wildcard App ID (xxx.*)

iOS provisioning profile

Usually I can always find what I'm looking for on Stack Overflow. But this time I'm really stumped.
I've read other Stack Overflow responses for people who have had a similar problem to this; but to no avail. (I think some of that is that I'm using Mavericks and I recently updated Xcode to 6.0.1.)
My woes began with getting this warning from Xcode: “Target Integrity Provisioning profile is expiring...” which was true. I had recently renewed my developer's license and I did need to update the provisioning profile.
So before I updated Xcode, I went to the iOS dev center and created a new provisioning profile and downloaded it. I selected it in Window->Organizer / Devices and I removed the old one. But the warning did not go away.
I read a post on Stack Overflow, from someone who could not delete their provisioning profile. They suggested using the iPhone Configuration Utility. I went to that web link for that program; and read there that for Mavericks, I should now use the Apple Configurator.
I downloaded the Apple Configurator but when I began using the program, I couldn't readily see anything about provisioning profiles.
I began to think, maybe I did need the older program called iPhone Configuration Utility after all. So I downloaded that, and it installed. But I cannot find it anywhere. I'm so confused by that. Is the iPhone Configuration Utility part of Xcode or part of Apple Configurator now?
To make matters so much worse, after I updated to Xcode 6.0.1, the screen in Windows->Organizer / Devices where I was able to see my provisioning profiles and add and remove them is gone! (I'm not sure where it got moved or how to get to it.)
I'm worried if I don't take care of this warning soon the app may stop working because it's referencing the expired provisioning profile.
Has anyone had some success updating a provisioning profile with Mavericks and Xcode 6.0.1?
Well all you need is access to your developer portal and Xcode.
If your provisioning profile is expiring soon, all you need to do is to go to your developer portal > provisioning profiles > click on the one expiring > renew or regenerate.
After you do that, go to Xcode > Preferences > Accounts > Your Account > View Details > Refresh and you should be good to go.
It won't hurt to clean up your project after this procedure.
Edit:
Also check if your selected provisioning profiles for your project's schemas are valid and the ones you actually need.
As for your expiring provisioning profile, that's the one managed by Xcode. You can delete it from your developer portal without any worries and go to Xcode > Preferences > Accounts > Your Account > View Details > Refresh for Xcode to create a new general development provisioning profile for you automatically.
This error happened to me when I refreshed my xcode account's provisioning profiles, the provisioning profiles just got replaced with some ID that looks like thisas2d-12asdsd-13asd-ad3as-8sds, solution is to just choose the correct provisioning profile again, if the provisioning profiles are updated, the updated profile should be there.
THIS IS IMPORTANT, MAKE SURE THAT BOTH THE PROJECT AND THE TARGET PROVISIONING PROFILES WERE CHANGED

xcode 6 unable to process application. The bundle '*' is not signed using an apple submission certificate

I'm running into the following error when using XCode 6 to validate or submit an ios app to the app store.
I know there are posts out there with this same error, but I've followed all the steps and still can't figure this out.
What I've tried.
Change "Valid Architectures" in Build Settings to
"$(ARCHS_STANDARD)".
Re-creating all certificates and
provisioning profiles. Deleting and re-downloading to local
computer. Syncing these via xcode account preferences page.
Installed the apple root certificates
Note. this builds and runs fine in debug mode, I can even export the archived app. It's only when validating.
Go to your Project's Target > Build Settings > Code Signing and check that your build schemas have the correct Provisioning Profile(s) selected.
Do this after you're sure that:
Your certificates are valid.
Your provisioning profile(s) are valid and that are using the correct App ID which should also exactly match the one in iTunes Connect. Also be sure the Provisioning Profile is an App Store Distribution one (be sure to name it accordingly so you can find it easily).
You've refreshed your account in Xcode > Preferences > Accounts > Your Account > View Details > Refresh.
After you've done all this steps and you're positive regarding your code signing selections, clean your project, select your device as the build device (even if it's not connected), Archive > Validate > Submit.
On XCODE 6.0.1 the issue was for me (OS X 10.10) to recreate new apple ID (although my apple ID was already there) so go to Preferences - Delete your current Apple ID account and + add again your apple ID. That did the trick.
So I ended up...
Creating a new user on my mac.
Copied the project over the one of the new users directory.
Deleted the ios distribution cert and re-created it along with new provisioning profiles.
Synced the new certs and profiles to my new user's directory and this fixed it.
So there had to be some mis-configuration with my existing user. When in doubt, start fresh and it may "just work"

No identities were available - administrator request not solved by previous answers

I get the "No identities were available - administrator request" issue
I have a valid certificate, a match boundle ID, a valid provisioning profile (distribution) I have two apps, both I published 3 weeks ago to the app store with the configuration I currently have.
the only thing that changed is that I upgrade my mac to 10.9 and my xcode to 5, but left my device at IOS6
now both my apps failed to validate with the above error.
I tried the steps in many other articles like No identities were available - administrator request
or Xcode 4.3.2: "No identities were available" - Where to request a Dev Identity?
or https://discussions.apple.com/message/21603155#21603155
and others
nothing works
any idea ?
I spent two days reading forums and searching the web and finally figured out the problem. Under your IOS provisioning profiles, you have to have a profile that is listed as ditribution under type. It also needs to be listed under your account in xcode (xcode>preferences>account>view details) if it is not listed there, click the refresh button to have it check itunes connect for your certificate. I tried deleting every certificate and everything from Certificates, Identifiers & Profiles and let xcode create new certificates, but xcode says it will add distribution stuff and doesn't. Make sure to use your provisioning profile that is a distribution type for your provisioning profile under your code signing in both of the app target build setting and the app project build settings.
I had to go into Applications -> Utilities -> Keychains on my Mac and remove expired certificates. After removing those, I had to generate new certificates through the IOS Developer Site and import those into the Keychains application. After doing so, return to Xcode and in Build Settings, verify you are using the new Code Signing Identity and Provisioning Profile. (You will need both recreated, as revoking the Identity will invalidate the Provisioning Profile.)

Resources