Re: When distribution profiles expire and the employee who created them has left.
Re: When distribution profiles expire and the employee who created them has left.
- Subject: Re: When distribution profiles expire and the employee who created them has left.
- From: Alex Zavatone <email@hidden>
- Date: Fri, 16 Nov 2012 20:28:57 -0500
On Nov 16, 2012, at 5:11 PM, Matt Neuburg wrote:
>
> On Nov 16, 2012, at 1:49 PM, Laurent Daudelin <email@hidden> wrote:
>
>> As for not being able to get your team provisioning profile, have you tried the Refresh button in the lower right corner of the organizer window? I have found that Xcode will be able to refresh all my provisioning profiles and will renew the ones that are no longer valid.
>
> That's what I expected to happen when I pushed that button. I can't quite remember what did happen, but that isn't it. :) And I tried several times, at various stages of the story... m.
Yeah, that was what I initially outlined in my email. Refresh doesn't.
I ended up having to go through Apple's iOS provisioning website and when it asked me to issue a CSR, all it said (yesterday) to my freshly requested and saved CSR on the desktop was "Invalid" something or other.
Today when I tried to issue a CSR against my corporate keychain using the Keychain Access app, it told me that it saved the CSR on my desktop, but looking there, there was no fresh CSR.
There was nothing.
Trying again, this is still the case.
Looking in the console, there was an error doing this:
11/16/12 8:11:54 PM /System/Library/CoreServices/Certificate Assistant.app/Contents/MacOS/Certificate Assistant[55511] MDS Error: unable to create user DBs in /var/folders/Eq/EqgU5+XVEuuxV6cWpmgPyk+++TI/-Caches-//mds
Of course, I've run Disk Utilities and repaired permissions. But I just tried this again and that's the console output you see above.
Of course, this issue did not happen yesterday, the file was saved.
Of course, if I try this and specify "let me specify my own key pair information", I am never asked to enter my key pair information.
If I run the Keychain First Aid, it says that my keychains are all fine.
Bearing in mind all of this, I opened a spare Lion box up, created a new user and tried to find any Apple document which showed where the starting point would be and what needs to be set up so that you can continue.
Good luck.
When creating a new user, you have no public/private key, so not sure what the exact base state is, to start from, I searched the dev docs to no avail.
This is simply insane. Apple lets you start a process - that is knows will fail if you have not set up the starting conditions exactly correctly - but never checks to see that you have done this. And when you reach a roadblock when something doesn't work there is no option to resolve the issues.
This happens from requesting your certificate refresh from the provisioning portal at developer.apple.com, this happens when going through the assistant for provisioning your apps, in fact, in many cases (if you have more than one dev license) where it is critical that you make a request from a specific keychain, there is no indicator that you need to make sure that you do so.
This is why I am trying to start fresh from a brand spanking new user on a foreign machine. But try to find the doc that shows you where you are in the process and what you have to set up beforehand to continue? Good luck!
There is too much documentation that points the user in all sorts of directions, but nothing that points you to "this is where you are, this is what you needed to have done, this is what you have to do".
To even refresh my certificate to then update my distro profiles, I can't even rely on the Keychain Assistant even saving the CSR that it told me it saved.
Apple really needs to expand its failure modeling and resolution in this process, because this is simply hell and the 29 page documentation TN 2250 doesn't point to a single path to help resolve what have been near daily issues in deployment on iOS.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden