StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>OK - I think I've fixed this. Here is what I did and it seems to work - when I upload the next release I'll know for sure.</p> <ul> <li>In X-Code, I deleted all of my provisioning profiles</li> <li>I then quit out of X-Code</li> <li>From the Development Portal, I revoked my developer and distribution certificates</li> <li>I created new keys using the Key Chain application</li> <li>Still in Key-Chain, I removed my old, soon to be expiring key/certificate</li> <li>Back on the Development Portal, I created new certificates</li> <li>Still on the Development Portal, I was able to edit all of my provisioning profiles and associate the correct new certificate to it</li> <li>I downloaded the new profiles</li> <li>I then followed this link's advice and worked around the apparent bug in X-Code to remove the old provisioning profiles from my project: <a href="https://stackoverflow.com/questions/1760518/codesign-error-provisioning-profile-cannot-be-found-after-deleting-expired-prof">Codesign error: Provisioning profile cannot be found after deleting expired profile</a></li> <li>Started X-Code back up and copied the provisioning profiles into Organizer</li> <li>Built for a device and tested OK.</li> <li>Built for IOS Device as though I'm preparing to upload to the AppStore and build was successful. I haven't tried uploading to the store.</li> </ul> <p>I actually did the steps twice, once for the development profiles and then once that worked/tested on my test devices, I modified the distribution profiles. </p> <p>These set X-Code up w/ no warning and Organizer now shows all my valid provisioning profiles that won't expire for another year. Hopefully, next year, if I don't forget these steps, I'll be able to do it a bit more quickly.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload