-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
☂️ Supporting Xcode 10 and the new Xcode build system #19573
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
By "Xcode 10", I hope you mean using the new build system rather than requiring the legacy one. |
@LeoNatan the issue is intentionally ambiguous, and should cover support by the new build system even though it's available in Xcode 9 as well. In general, we want people, come September, to be able to install Xcode 10 and continue working on their projects without being held back by some incompatibility on our side. Ideally, we'd address any issues ASAP as people have already been working on iOS 12 updates using Xcode 10 for a month now. |
While available in Xcode 9, the amount of people that actually enabled it was miniscule. Now it is enabled by default, and is difficult in some cases. It is good that the team is looking into it from early on. 👍 |
Is there any other issue we need to take into account before we can close out this issue? |
I've been using Xcode 10 with these patches applied now for a couple of weeks and haven't encountered any other blockers. Thanks for following up on this, @hramos! |
Added #19839 to the list of pending issues. |
With public release days away - any update on when these issues will be resolved please? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Today, I created a new project with RN 0.57 and it compiled, run without any issues using XCode 10. |
Can confirm it’s working me now now too having cleared out /iOS and /android folders. |
Hey, try going into your XCode project settings (File->Project Settings) and change the build system to Legacy Build System. This helped me. |
It would be nice to get to 100% Xcode 10 / new build system support in time for 0.58. For people just arriving here, if you are facing issues in Xcode 10, please take a look at the list of known issues in the original post above. If your issue does not match any of those, please try the following:
If that does not work, please do the following to help us keep track of any remaining issues that need to be solved:
GitHub will show the list of related issues in this here thread. I'm going to lock this master issue in order to keep the discussion focused on moving support for Xcode 10 forward. |
Quick update: there is currently a PR in the working that should help with XCode 10 support #21458 |
I'm in the process of switching our CI to use Xcode 10 by default. We're currently blocked due to an issue with Circle CI's macOS image. While Xcode 10.0.0 is available, the command line tools for 10.0.0 are not available in the image. This is keeping us from being able to compile
==> Installing applesimutils from wix/brew
==> Downloading https://raw.githubusercontent.com/wix/homebrew-brew/master/Apple
######################################################################## 100.0% CompileC /tmp/applesimutils-20181102-18112-6h2nr4/build/Build/Intermediates.noindex/applesimutils.build/Release/applesimutils.build/Objects-normal/x86_64/main.o /tmp/applesimutils-20181102-18112-6h2nr4/applesimutils/applesimutils/main.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target: applesimutils) ** BUILD FAILED ** The following build commands failed: If reporting this issue please do so at (not Homebrew/brew or Homebrew/core): Error: A newer Command Line Tools release is available. Exited with code 1 There's some workarounds in wix/AppleSimulatorUtils#29 that we could attempt, if anyone is interested in getting this working. |
Xcode 10 is now properly supported with the latest releases of React Native, so I'm gonna close this issue :) Please feel free to create smaller issues for things that may still be broken. |
Is the new Xcode build system supported for certain in master now? |
For Discussion
This task tracks issues with Xcode 10 as well as the new Xcode build system. This modern build system was originally introduced in Xcode 9, and it is now used by default in Xcode 10.
Troubleshooting
Please take a look at the list of known issues below. If your issue does not match any of these, please try the following:
If that does not work, please do the following to help us keep track of any remaining issues that need to be solved:
A maintainer will then update this post with a reference to your issue as needed.
Known Issues
Fixed Issues
Xcode signing issues due to Facebook Team ID being used by default in npm release #16881 - Xcode signing issues due to Facebook Team ID being used by default in npm release
Xcode 10 libfishhook.a cannot be found #19569 - Xcode 10 libfishhook.a cannot be found
Problems with glog (config.h missing) and gflags/gflags.h on Xcode 10 #19774 - glog (config.h missing) and gflags/gflags.h
Make run-ios command play nicely with multiple Xcode versions #19781 - wrong iOS simulator is used in Xcode 10
Problem with third-party in Xcode 10 building to iOS physical device #19839 - third-party encounters a semantic issue during Xcode builds to physical iOS device
Xcode 10: unable to open dependencies file when archiving a project #21137 - Unable to open dependencies file when archiving a project
'Multiple commands produce' error when building with new Xcode build system #20492 - 'Multiple commands produce' error when building with new Xcode build system
Opting out of the new Xcode build system
For issues related to the new Xcode build system, you may be able to unblock yourself by switching to the legacy build system.
Using Xcode:
Using
xcodebuild
:You may use the
-UseModernBuildSystem=NO
flag to opt out of the new Xcode build system.Mitigating issues in future Xcode updates
Currently, our CI runs tests on the latest stable Xcode release. We could have caught many of these issues by doing two things:
PRs that add support for either of these are welcome. For the latter, we'd look for Xcode 11 beta support once it's presumably announced next summer.
The text was updated successfully, but these errors were encountered: