So I recently created some provisioning profiles and am handling them manually in order to insure the correct use for push notifications. However, my Development profile appears under a heading of Ineligible, but seems to be accepted with no warnings or anything. Am I misunderstanding the meaning of eligible/ineligible in this situation? In the screenshot, you can see which profile is for distribution and which is for development. The fully crossed out one is just the wildcard
Maybe this profile are made under another distribution cert which is not use in your project ?
Related
The distribution provisioning profile that I use for my iOS app "BodBot Personal Trainer" has been working without issue for the past several months. Without any change from my part, it became invalid. It appears that the accompanying Certificate had expired a few days before I found that the profile became invalid, so I assumed I just needed to "Generate" the profile again. This did not work. I then verified that the related App ID was fully functionality, which it was. I then created a new Certificate as well as a new Provisioning Profile associated with that Certificate. None of these actions seem to successfully result in a working Distribution Provisioning Profile associated with my App ID.
Odd note: Each time I Generate the Provisioning Profile, it shows up as "Active" for around 10 minutes, at which point it shows up as "Invalid"
Question: There's little/no detail as to what is going on here. Any help, even if it's just a place to look for additional data for a diagnosis, would be very much appreciated. When it comes to provisioning profiles, I'm pretty lost.
This sounds like symptoms of automatic provisioning resolving done via XCode. Even though it works sometimes, it's good practice to avoid using this feature, as usually it is invalidating current profiles for some reason.
Consider trying out brand new tool by F.Krause, which will allow to centralise provisioning profiles and avoid their constant invalidation/re-generation.
Xcode as of 6.3 is no longer allowing me to automatically perform device provisioning for a client. Has anyone else experienced this issue? I found no results when searching for this on Google...
This client has their own bundle ID and it's possible they also have their own provisioning profile for this device. So maybe Apple is matching up the bundle ID irrespective of the developer account being used for provisioning.
I was able to address the issue by modifying the app's bundle ID and manually going through the provisioning process, but I'm guessing this issue is extremely rare, so I'm not sure if this post will be of use to anyone.
When I am create new certificate from my Xcode 9.2 the error was appear
"You already have a current iOS Distribution certificate or a pending certificate request".
Just 2 step for fix this error.
Remove old certificate from developer.apple.com
Create new certificate from Xcode or developer.apple.com
My problem has been solved (I am using Xcode 9.2).
I just found that if I remove my account from Xcode, and then sign in again, it solved the issue. I did revoke my existing certificates and request new ones though as part of that process. I didn't import an existing profile.
My team has maxed out on release certificates, because apparently there is a quota.
We had to delete one of the existing release certificates.
This issue is actually more common than you think.
Some Solutions:
I usually find that opening Xcode's settings and signing out of my account and the signing in again resolves most of those issues.
You may have an older mac that already used up that one allotted development certificate. In that case you'll want to export the developer profile from that machine. If you no longer have access to that machine, it may be time to invalidate that certificate and simply request a new one.
Another option may be to double check your build settings in your project and ensure that it's looking for the right certificate. It's fairly common in my experience for these settings to make decisions on their own, and confirming that they're what you expect may help.
Background:
When dealing with provisioning, it's really easy to get caught up with the frustration of all of the steps you need to go through. The first thing to note is if the error you see is talking about a "Certificate" or a "Profile." In your case, it's a certificate. Good.
Certificates differ from provisioning profiles in a few ways. Certificates are usually only generated twice: once for development, and once for distribution. (Exceptions to this rule are if you decide to add support for some of the special features like push notification or for generating passbook passes on a server.)
The process for generating certificates is also a little more bureaucratic than profiles. You request a certificate from Apple's Member Center. You generate a provisioning profile.
The reason for the word request vs generate is because both Apple and your iOS team's admin need to approve certificate requests. This is because certificates identify you as part of your iOS developer team, and offer all the powers associated with that.
For the sake of completeness, I'll add that provisioning profiles are generated based on that certificate, and really only tell iOS what environment your app is meant to run in. (On any device via the store, specific devices, etc.)
Now, the important part for you is the request business. Most people don't pay much attention to this terminology, since indie developers and small teams (where the developers are admins) don't require developers to ask for permission.
Your error is talking about a previously generated certificate or request. You can only have one development certificate per developer. You either have one, or you've requested one and someone has to approve.
That's what's happening here.
This process is made simple with Xcode 8.3 and 9. Just delete one of your old certifcates in the "validate" interface and click the plus button to request new one, Xcode will request for you and add it in keychain. in my case, maximum number was reached, so I deleted one which was lost in a old Mac and created new one.
This error may also be occur if you reach your distribution certificate limit. After creating 3 iOS Distribution Certificates in an account, the following error message will be displayed when you try to create 4th one: "You already have a current Distribution certificate or a pending certificate request."
Open this link
https://developer.apple.com/account/resources/certificates/add
Press + icon in front of Certificate
Check Apple Distribution section if its show the red text as shown in image then you should revoke you existing certificates to generate new one because you have reached you limit.
Just 2 step for fix this error.
Remove old certificate from developer.apple.com
Create new certificate from Xcode or developer.apple.com
Delete old developer certificate from https://developer.apple.com/account/ios/certificate/ and try to create developer certificate from xcode
1) Remove old certificate from apple developer account.
2) Go to the 'Xcode' 3) Select 'Preferences' option and then Select the 'Account' Tab
3) Select apple id from left side and click on 'Manage Certificate'.
4) Click on '+' (add certificate) button.
5) Add 'Apple Distribution' Certificate.
Unfortunately, only a macbook restart resolved this for me.
Creating another Distribution certificate was not an option, because it had already reached the max. number of certificates.
I manually added an existing one (incl. its private key) to the Keychain …and still Xcode said "Not in Keychain". I then tried to trigger a refresh of the Xcode listing by removing & adding my developer account to Xcode, but that didn't work — neither did restarting Xcode.
So, when all else fails, you try to reboot your system.
When you have three active distribution certificates that were created on distinct machines, you'll see this issue. You can either ask for the private key of a previously made one or simply revoke any of them and make your own.
My provisioning profile suddenly became invalid.
I logged in developer.apple.com couples of days ago and everything was fine. Today I logged in again and was surprised to find that both of my development profile and distribution profile were invalid. The certificates and App ID are valid, I did not revoke any of them and they are not expired at all. So why my profile became invalid?
I know I can re-generate profile but because I do enterprises distribution not app store distribution. I am worried that regenerating profile may affect current users. Also, I really need to figure out the reason to prevent it from happening again.
Any idea? Thanks!
Updated: First of all, it is not because the profiles were expired, their expiration date is at the end of 2015.
Second, I did re-generate development profile at morning but I just checked it and found the profile was invalid again! Something weird must happen and I have submitted a support ticket to apple and wait for their response.
I'm curious to see what Apple support says. According to Apple (https://developer.apple.com/library/ios/qa/qa1878/_index.html) :
Q: What causes the provisioning profile "Invalid" status? How do I resolve it, and how do I prevent it?
A: The provisioning profile invalid status is caused by changes to the profile’s associated certificate or App ID. Any time an App ID or certificate changes, all profiles that are associated to it are marked Invalid. This does not apply to Xcode's team profiles, but applies to all profiles that Xcode does not manage, specifically, custom development profiles and distribution profiles. This document explains the causes in detail and provides steps to resolve and avoid the profile invalid status.
One possibility is that you modified the app id by turning on or off services in Xcode:
Avoidance
Since Xcode started managing services on App IDs (through the Xcode >
Target > Capabilities tab), Invalidating provisioning profiles became
as easy as enabling or disabling a target capability. Remember that
every time the App ID changes with respect to its enabled services,
all profiles attached to that ID become invalid.
Hope this helps.
It seems that somebody still hits this problem after almost a year when I first raised it. So I am answering my own question trying to provide some insight.
Apple never answered my ticket instead they returned my credit. I took that as a sign that they had no idea either (saw my comments above). I can still use that "invalid" profile but it really made me uncomfortable. So I created a different one.
In summary it maybe just a bug in their system and if you have tried all the solutions and the problem still exists just create a new one.
If you generate a new provisioning profile, your old installations (store or adhoc) won't be affected
The provisioning profile lives for 1 year, maybe it expired so simply remove it and make another one with the same certificates, app ids and devices and you can use it without any problem
EDIT:
I don't know a case where a provisioing profile would become invalid unless:
It reached its expiry date;
You modified the app id or certificates that are related to it.
I guess it's related Automatically manage signing in Xcode. In case you switch to another branch which has different configures in Xcode > Target > Capabilities, Xcode will change your App ID settings
If you generate a new CSR for something like an APNS certificate, it will mark your provisioning profiles as invalid.
Guess I found the answer, it's simple go to the apple developer account and select those certificates which wasn't working.
1.Edit them and simply add some new name just to remember.
Select same App Id and certificate for both development profile and distribution profile and hit the download button
After downloading add them into you Xcode and you will them there.
it generally happens when you update your Xcode, so be sure when you check certification where Xcode is mentioned(For use in Xcode 11 or later in my case)
For me it's just opening the apple developer account, edit the profile, save it and download the provisioning. Made a new build and then reupload it.
So I was getting the no identities are available for signing error when I tried to upload my app, and I tried a number of ways to fix this.
That was a very bad idea.
I tried revoking my certificates and now it's telling me
No matching provisioning profiles found: None of the valid provisioning profiles include the device Justin's iPad (identifier: 5858525b2680f4b92838cd5d54e3c56bcb1edf98).
CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 7.1'
And under preferences, accounts it says the iOS Development is missing the private key.
I am completely and totally lost on what to do to fix this. Can anyone point me in the right direction?
I recently had this same problem. The mysterious message about the development profile is particularly telling - we should not be talking this way, because App Store is distribution, not development. Proceed as follows:
Look in your keychain with Keychain Access. You will probably see that the iOS Distribution certificate has gone bad or is missing entirely. So that's the place to start. Go back to the Member Center and get yourself a working Distribution certificate and get rid of the old one, deleting it entirely from the Member Center (that's important).
Now throw away your distribution profile both in Xcode and at the Member Center. Make a new distribution profile and download it. Adjust your build settings to match the new profile!
The reason for the whole problem is that the Member Center will happily make you a distribution profile with a bad certificate, and that's what you had. There is no easy way to detect that this has happened because it's hard to distinguish what certificate the distribution profile is using. You need to make sure that there is a good distribution certificate and that it is the only distribution certificate so that you can be sure that when you make the distribution profile, the good distribution certificate is used.
Yeah, revoke your previous certificates and then go through the process of requesting certificates again. You'll have to regenerate your provisioning profiles after the new developer / distribution certificates are issued, though.
You start by going to the "Certificates, Identifiers & Profiles" section of your account at https://developer.apple.com/account/overview.action.
After you revoke the previous certificate, you can click "+" (in the upper right hand corner of the Certificates screen on Apple's portal) to add a brand new iOS certificate (and there will be instructions there that tell you what to do.
Fot testing iPhone apps, is it a bad idea to have a development code signing provision that will run any app with com.mydomain.* ?
Why?
EDIT:
See italicized edit above.
I doubt it, the provisioning profile is specific to a set of UUIDs. No one else would be able to use the profile unless they had your developer certificate and the specific device.
However, you can't test push notifications nor in-app purchases with a generic profile.
Are you talking about the development or distribution code signing provision?
I use a generic code signing provision for development (otherwise it would be absurd to run any sample code from online, or test apps).
For distribution though, I get a unique identifier. I sort of assumed it was required. Just for safety's sake.