Today, I revoked and reissued my certificates since they were set to expire this weekend and regenerated all my provisioning profiles (well all that I’m working with at the moment)
And I upgraded Xcode to 4.3
And I upgraded Corona SDK to the latest daily build
and I haven’t run Corona SDK yet…
Wish me luck!
[import]uid: 19626 topic_id: 22707 reply_id: 322707[/import]
Yep, it didn’t go well. Got lots of certificate based errors on the build… 
EDIT: Here is the error I got…
warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
failed to extract requirements data: 1
/Users/rmiracle/Lua/AppBuilds/MyApp.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: /SourceCache/codesign_wrapper_Sim/Security-1245/codesign_wrapper/codesign_wrapper.c, line: 866
warning: Unable to extract codesigning entitlements from your application. Please make sure MyApp is a valid Mach executable that’s properly codesigned. (-19050)
/Users/rmiracle/Lua/AppBuilds/MyApp.app/MyApp: invalid signature (code or signature have been modified)
[import]uid: 19626 topic_id: 22707 reply_id: 90580[/import]
yep… rob, we r looking into it…
c. [import]uid: 24 topic_id: 22707 reply_id: 90597[/import]
uhgh - could be your newly certified certificates…
looking into it…
[import]uid: 24 topic_id: 22707 reply_id: 90598[/import]
First, can you give us a baseline and build the Hello World sample project with a Developer (not distribution) certificate?
Can you look through the terminal output and your system log (Console.app). We are printing some debugging messages about the Xcode paths and versions. Can you paste the information here?
Also, please verify your installation:
Mac OS X 10.7.3
Xcode 4.3 (4E109)
Do you still have older versions of Xcode installed? If not, did you delete Xcode or is this a fresh install? If you deleted it, did you use the uninstall script or drag it to the trash or let Xcode 4.3 delete it?
[import]uid: 7563 topic_id: 22707 reply_id: 90608[/import]
I think I just have my keys/certs screwed up. I just successfully built a development version. So now I’m going to go redo the process for distribution and hopefully I’ll be back in good shape. I’ll report back in a few minutes.
BTW: All things I’ve seen said that when your year is up you have to revoke your cert early or wait until it expires, then go through the whole get a new cert process, which I’m trying to do.
Apparently all you have to do is go into Xcode organizer, and click on a provisioning profile that is red for expired, and it does all the renewing for you according to a little hidden blurb I found in Apple’s documents.
[import]uid: 19626 topic_id: 22707 reply_id: 90612[/import]
OOh that’s a handy tip, Rob! Thanks! 
[import]uid: 10389 topic_id: 22707 reply_id: 90613[/import]
Okay, I think I have things straightened out. I just have to go redo all my provisioning profiles but the certificate issues seem to be solved.
But I did get this warning in the console while trying to build the app:
2012-03-01 20:35:14.315 Corona Simulator[29901:2403] xcode-select is using Xcode version: Xcode 4.2.1
Build version 4D502
xcode-select is using Xcode version: Xcode 4.2.1
Build version 4D502
2012-03-01 20:35:14.395 Corona Simulator[29901:2403] Warning xcode-select found Xcode (version 4.2.1) is older than Launch Services Xcode (version 4.3). If this is incorrect, run 'sudo xcode-select -switch ’ to change it
Warning xcode-select found Xcode (version 4.2.1) is older than Launch Services Xcode (version 4.3). If this is incorrect, run 'sudo xcode-select -switch ’ to change it
[import]uid: 19626 topic_id: 22707 reply_id: 90614[/import]
Did you uninstall 4.2 and use xcode-select to reroute to the new version? [import]uid: 10389 topic_id: 22707 reply_id: 90615[/import]
No, I went to the developer portal, clicked on XCode 4.3, it took me to the Mac AppStore and I did an install.
How do I remove the old one?
EDIT: So far I’ve been able to build all of my apps as Ad Hoc and install them with no problems. I don’t have anything to release right now, so I can’t test store releases. [import]uid: 19626 topic_id: 22707 reply_id: 90620[/import]
http://pushkararora.com/how-to/how-to-uninstall-xcode-completely/
Then just install the one you want and use xcode-select to pick it.
There’s been other people having issues after installing 4.3 when 4.2.x is still installed. It confuses things. [import]uid: 10389 topic_id: 22707 reply_id: 90621[/import]
I’m still a bit confused. If I run xcode-select -print-path it shows:
/Developer
This is the only path for Xcode that I’m aware of.
I’m not sure what to type in for:
xcode-select -switch <xcode_folder_path>
It appears that my xcode_folder_path is /Developer but apparently it isn’t. [import]uid: 19626 topic_id: 22707 reply_id: 90624[/import] </xcode_folder_path>
XCode 4.3 does not install in /Developer it installs under Applications [import]uid: 10389 topic_id: 22707 reply_id: 90626[/import]
http://useyourloaf.com/blog/2012/2/17/updating-to-xcode-43.html [import]uid: 10389 topic_id: 22707 reply_id: 90627[/import]
Please go to this thread for the info you seek.
http://developer.anscamobile.com/forum/2012/01/13/trying-build-ios-app-get-error-please-reinstall-ios-sdk [import]uid: 7563 topic_id: 22707 reply_id: 90629[/import]
I’m all good now. My problem was that I had Xcode in my dock. So after installing 4.3, I ran it from the dock and everything looked normal. I didn’t get the prompt to remove 4.2.1.
Once I removed the dock icon and replaced it from the Applciations folder, it prompted me to remove the old version and I just did a completely clean Corona Build.
Now given that I have over 30 years of experience dealing with computers and software, I know perfectly well that you are not supposed to change multiple things at once, which I foolishly did even though I knew better.
[import]uid: 19626 topic_id: 22707 reply_id: 90631[/import]
@Rob,
first, thanks for sharing all of this boring info.
BTW, I`ve renewed my membership with Apple one month ago (because my membership will expire now in 10 days from now) and I am very confused!
Look, I have 3 apps on the AppStore already. So I have at least 3 distribution profiles as well. And so I have 3 provisioning profiles as well. AND I have my own Developer Certificate surely. BUT my problem comes now: What do I need to do exactly about it all? How about my apps? updates? and my own certificate of developer?
I am so sorry for these question, BUT after read your own journey about it same here, I would not “escape” the chance to ask you.
Could you please take a moment here regarding my trouble? :\
Many thanks in advance as usual,
Regards,
Rodrigo. [import]uid: 89165 topic_id: 22707 reply_id: 90675[/import]
I think the first thing that needs said is:
Relax. Breath. Don’t panic.
Your existing apps in the app store will continue to work fine. If you had not re-up’ed your Apple Developer License, they would have come down until you joined back up, but since you’ve done that already your existing apps are safe and sound as they are now.
However, your certificates (two of them, development and distribution) will expired shortly (1 year after you created them). When that happens, your provisioning profiles will expire too and any Ad Hoc or Development builds you have on devices will expire and won’t run. This will impact your beta testers if you use a service like TestFlight, or if you have multiple devices, those apps will stop until you renew them.
All of my research on the certificate renewal process is scary. None of us like dealing with certificates, public and private keys, signing requests, certificate authorities etc. It’s plain and simple evil.
But I caught a blip of a statement on the Apple developer’s portal that said, all you have to do is wait until the provisioning profiles go red in XCode’s orgainzer, then click on it and it will renew everything for you. I wish I had kept the URL for that because everything else I’ve googled goes against that process.
I went against that process and it took me several hours to get things straight because I missed a couple of steps.
In my case, I chose to deal with this before they expired so there was the basic workflow that seemed to work:
In the Provisioning Portal: Revoke your certificates. All of your Provisioning profiles will still be there, but they are now invalid.
Bring up Keychain Access and remove your old certificates. They are no longer valid anyway. At some point I ended up removing the public and private keys too.
Back to the provisioning profile, and request a new Development certificate. (do the development and distribution separatly just for sanity purposes). It will give you the instructions on what to do to request a new certificate.
It will create a signing request file on your desktop. From the Provisioning profile you will upload that request. When its done you will get a chance to download the certificate to your Mac.
Apple kindly leaves off a step, double click on the downloaded .cer file to have it installed properly in Keychain access. This should re-create the public and private keys if you deleted them. in theory…
Now go to your provisioning profiles and click on “Modify” I think, it should be the only think you can click on. Then select your new certificate and save. You will find that the new profile is valid again and after a screen refresh, you can download it.
Copy the profile to your ~/Library/MobileDevice/Provisioning Profiles/ folder (in Lion Library’s are hidden from the finder, so I do this from the command line:
cd ~/Library/MobileDevice/Provisioning\ Profiles
mv ~/Downloads/\*.mobileprovision . Note the backslash escaping the space in the cd command. This also assumes that your web browser downloads to your Downloads folder.
Launch Corona SDK and try and build a development version of that app and make sure everything is okay.
If it is (and I’ve not missed a step in my instructions), then go back, and renew all of your development profiles and download them. At this point you can repeat the two command line shell commands above, but you can also wait because we are going to be doing it again.
Now back to the provisioning portal, and follow the process to create a new distribution certificate. You can use the same signing request you used earlier, just upload it, request the new cert, download it. Double click to install it into the keychain.
Back to the provisioning portal, to provisioing profiles… Now its time to refresh all of those guys. You likely will have both Ad Hoc and Distribution ones.
Unlike the development ones, when you visit this screen, the certificate will already be selected. In theory you should be able to just hit the save button and be done, but Apple doesn’t make it that easy. That button is grayed out until you make a change on the form. What I found as the best way to do this is to change the radio button from Ad Hoc to Distribution and then back to Ad Hoc will enable the save button. If you’re doing a distribution profile, then you would check ad hoc and then back to distribution.
Like with development, now would be a good time to test your ad hoc builds before you renew all the profiles you have.
Refresh and download the profile. Quit Corona SDK, use the two command lines above to put the profiles in place. Relaunch Corona SDK, do a test build with one of the AdHoc profiles and install it via Xcode or your normal method to your device and make sure everything runs.
If you’re good at that point, go back to the provisioning profile, renew all of your profiles, download them.
Quit Corona SDK, repeat the two command line commands and you should be all done. You can now launch Corona SDK and continue like nothing is different.
The latest daily builds should continue to work with XCode 4.2, so I would advise NOT changing your XCode during this process. Make sure your certs and profiles are all in happy land first.
Then if you want to go to 4.3 of Xcode, then follow all the advice above from @Waulok and @ewing to manage that upgrade. If you have Xcode in your Dock, make sure to remove the one there and install the new one from /Applications.
Corona’s daily builds you continue to do like you always do.
[import]uid: 19626 topic_id: 22707 reply_id: 90747[/import]
@Rob,
being very honest with you: I have no words to “translate” my BIG THANKS to YOU!
Man, its wonderful that you wrote an explanation book about the apples membership black side.(lol)
By the way, as you said at the start of your post above, I can “wait” to see if my Xcode will show my profiles in RED and then go to try the “easy” proccess of doing it as you said you did find it at some point but lost the URL. No problem.
Im using Xcode 4.2.1 and I do not want to upgrade it for 4.3 at lease as yet! Ive had many problems doing that few time ago. :\
So, I am going to save this amazing explanation of yours and will read it carefully again and try to understand all because my time is expiring in 1 week.
I`ll notice you here when I get this boring proccess finished @Rob. I have to do.
Thank you so much for taking the time,
Regards,
Rodrigo.
[import]uid: 89165 topic_id: 22707 reply_id: 90798[/import]
Actually, I ask that you start trying/testing Xcode 4.3 now since we’re spending so much time trying to fix it right now. We think it’s fixed, but need you guys to verify that.
[import]uid: 7563 topic_id: 22707 reply_id: 90801[/import]