How do I fix this:
The version of iOS SDK (9.2) that’s installed on this computer does not match the target iOS version (9.0). You may encounter issues building or incompatibilities at runtime.
You should consider updating your version of Xcode or using xcode-select to enable a compatible version.
Do you want to proceed with a build?
Xcode version 7.2
Corona SDK Version 2015.2731 (2015.10.5)
Try using latest daily build
I have tried. The cure is worse than the disease. Does not recognize certificates from Apple. These things always happen. You end up getting tired.
If you use the latest daily build + Xcode 7.2 you shouldn’t have issues unless you have expired/invalid certificates that we used to let you use.
Go into Keychain Assistant and make sure you don’t have any expired certificates.
Rob
Hi Rob, my certificates expire in May. I’ve reinstalled the latest public version of the SDK and this does not happen.
What happens if the latest version of Xcode and Corona SDK is this:
The version of iOS SDK (9.2) that’s installed on this computer does not match the target iOS version (9.0). You may encounter issues building or incompatibilities at runtime.
You should consider updating your version of Xcode or using xcode-select to enable a compatible version.
Do you want to proceed with a build?
Xcode version 7.2
Corona SDK Version 2015.2731 (2015.10.5)
Look:
Why Corona SDK path lost certificates?
If you’re going to use 2731, you must use Xcode 7.1, not 7.2.
If you insist on using Xcode 7.2, you must use 2788 or later.
If you’re having problems with your certificates, you will need to trouble shoot them and you may have to start fresh.
Rob
Just by installing version 2788 certificates disappeared for Corona SDK.
We managed the support of Corona SDK Xcode but can not find the certificates.
What’s up!
This bureaucracy has me rotten.
Can you provide a better description of what you mean by you can’t find the certificates?
Rob
Look:
Go on line to the Provisioning Portal and regenerate those profiles. The are tied to an invalid or expired certificate.
Rob
Um, are you sure?
Watch the year certificates.You do not see something strange?
You can open up the two certificates and see if the private keys are expired.
But just because your certificates are current doesn’t mean the provisioning profiles are using the current certificates. After changing or renewing them, you have to regenerate your provisioning profiles.
Rob
Already it solved, Rob. I did what you told me: regenerate the development provisioning profile.
I’m tired of these things.
Thank you so much for your patience.
Using current Public Release 2731, I had this problem after upgrading to Xcode 7.2.
Problem immediately disappeared, when I upgraded to 2788.
Rob, do you know when the next Public Release is due? If imminent, I’d rather build app ready for upload to AppStore with that.
Your comment “if you insist on using 7.2” makes me wonder; are there are any issues that might crop up with 7.2 & 2788? If so, can you recommend the most stable pre-PR Daily Build to use for distribution? Thank you.
LB
We are close to entering our testing cycle for the next public release. The current daily build is fairly stable.
Rob
Thank you!
Try using latest daily build