Skip to content

Conversation

@mikehardy
Copy link
Contributor

Summary:

Apple defines the minimum version of Xcode that is truly usable.
They will enforce iOS15 SDK (thus transitively requiring Xcode 13) in April 2022:
'Starting April 2022, all iOS and iPadOS apps submitted to the App Store must be built with Xcode 13 and the iOS 15 SDK.'

Until then, Xcode 12 is still a viable compiler.

Test Plan:

I have side-by-side installations of Xcode.app installed in one of my test environments.
I switched to Xcode-12.4, the oldest one I still have, and then did npx react-native init TestApp124 --version=0.68.0-rc.1 and ran it, it seemed to run fine. So Xcode 12 still seems to compile fine.

Note the converse is not true in reverse, not sure how to enforce it, but if you use react-native 0.63 with Xcode 12.5+ it will not work, but you don't want to limit the upper version range really. Not sure if it makes sense to release a patch on an old version of react-native-cli doctor for react-native <= 0.63 that clamps the version of Xcode to <= 12.4 - but the idea that an forward-incompatibility is discovered retroactively is something that will be needed in the future again, so it's interesting to think about

Apple defines the minimum version of Xcode that is truly usable.
They will enforce iOS15 SDK (thus transitively requiring Xcode 13) in April 2022:
'Starting April 2022, all iOS and iPadOS apps submitted to the App Store must be built with Xcode 13 and the iOS 15 SDK.'

Until then, Xcode 12 is still a viable compiler.
@grabbou
Copy link
Member

grabbou commented Feb 14, 2022

I guess it's good if Doctor command checks for the best combination of tools and will warn if e.g. there's a different Xcode version (when done on purpose, I bet developer will know what is doing).

@grabbou
Copy link
Member

grabbou commented Feb 14, 2022

@mikehardy

Not sure if it makes sense to release a patch on an old version of react-native-cli doctor for react-native <= 0.63 that clamps the version of Xcode to <= 12.4 - but the idea that an forward-incompatibility is discovered retroactively is something that will be needed in the future again, so it's interesting to think about

Mind opening an issue for it? I don't want this to get lost and this is interesting. I wouldn't touch previous version of the CLI, since no-one complained, but I think we could tackle that going forward. It's not a big priority since we usually recommend staying on the latest RN which supports the latest Xcode release most of the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants