StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I had this same issue ... I figured this out... There are apparently a lot of things that can happen to cause this issue. This was my particular flavor so you may or may not find this useful...it is just one more thing to check. I thought I would post the solution so when I am trying to figure this out next year I can find my post and fix it ;) Also if anyone else see a similar problem they can find this and maybe it is what they are seeing... My particular problem was I did not catch all the places that need to be updated. I got two out of three which may be close but we're not playing horseshoes here ;) Before you ridicule me just remember hind sight is 20/20...and I'm old and can't remember stuff I probably figured out last year.</p> <p>There are several areas to check to make sure your provisioning profile is updated.</p> <p>First there is the new developer identity certificate. Make sure this is put into your keychain. Mine is under Keychains - login in the Key Chain Access app on the Mac. Next you need the new provisioning profile on the device. Delete out your expired ones and get a new one generated through the use of your new developer identity. Do this through the XCode4 Organizer. Trust the warnings in Organizer that a valid certificate cannot be found... Finally, this is the one I missed, update the Library Provisioning Profiles! Again through XCode4 Organizer above "DEVICES" there is a "LIBRARY" section select "Provisioning Profiles" delete out your old expired profiles and add your new provisioning profiles.</p> <p>The big hint was in the project build settings - the code signing area tells you what provisioning profile the signing matches. Mine said "currently matches..." and then listed an older profile that was different from the new one I was putting on the device. Even though that older profile was not expired it was - I believe - based on the old developer identity which had expired last night. So I think the problem was XCode was signing with that older provisioning profile and the device had the newer provisioning profile and so I get the really clear error message above ;) ...</p> <p>I was looking for this for hours and hope I can save someone a bit of time. I am sure I will be looking for this next year when I screw it up again.</p> <p>Note to self: I told you that you were going to mess this up next year...and here it is next year and you are reading this post.</p> <p>This same post is at: <a href="https://devforums.apple.com/message/425569" rel="nofollow">https://devforums.apple.com/message/425569</a></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