Xcode 10.2 build failed

[mhpyzzy]

🐛 Bug Report

/configure:-1: in `/Users/zhangzhenyang/Documents/practice/test/node_modules/react-native/third-party/glog-0.3.4':
/configure:-1: C compiler cannot create executables

To Reproduce

1. react-native init test --version 0.51.0
2. Double-click the test.xcodeproj
3. Click the run button on Xcode

Actual Behavior

Environment

Environment:
OS: macOS 10.14.3
Node: 11.13.0
Yarn: 1.15.2
npm: 6.7.0
Watchman: 4.9.0
Xcode: Xcode 10.2 Build version 10E125
Android Studio: Not Found

Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0

[react-native-bot]

It looks like you are using an older version of React Native. Please update to the latest release, v0.59 and verify if the issue still exists.

The "Resolution: Old Version" label will be removed automatically once you edit your original post with the results of running `react-native info` on a project using the latest release.

[mhpyzzy]

i del old project, and react-native init newtest:

Environment

React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Memory: 9.07 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.13.0 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.7.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
IDEs:
Xcode: 10.2/10E125 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.4 => 0.59.4
npmGlobalPackages:
react-native-cli: 2.0.1

Actual Behavior

[colin-kudos]

What about on macOS 10.14.4? You are listed as macOS 10.14.3 - it worked for me

[hramos]

Are you using the legacy build system? See #20774

[MaheshNandam]

RN 0.57.7 and XCode 10.2

if I'm trying to run the app into 12.2 version simulators or devices, then app got crashed with
Thread 1: signal SIGABRT

ISSUE LINE -> 0x102eda2f8<+8>: b.lo 0x102eda310 ; <+32>

if I'm trying to run into 12.1 version simulators or devices, it works fine.

With this (RN 0.57.1 and XCode 10.2) configuration, if I generate IPA, it's only working in 12.1 devices and when it comes to 12.2 devices, app getting the crash on the launch screen with Thread 1: signal SIGABRT.

Any suggestions or workarounds to solve this issue?

Thanks for that savior.

[vikasdosi]

you can try my purposes and installed the fix within the node_modules/react-native package. Normally I would prefer not to modify a node_module directly, but under this circumsance, I felt that it was worth it and allowed us to add a simple script in our yarn start script and we get a clean run from a fresh clone.

npm install or yarn - install packages
cd node_modules/react-native - go to node modules directory
scripts/ios-install-third-party.sh- install @ node_modules/react-native/third-party
cd third-party - go to newly created third party directory
cd glog-0.3.x - ls -la to find your directory version number or just use tab to auto-complete)
./configure - run setup
cd ../../../../- change back to your project directory
react-native run-ios or react-native run-android - deploy

[hramos]

@MaheshNandam in your case, I'd try updating to RN 0.59 or newer. In general, when building your app using a newer Xcode or against a newer iOS SDK, you'll want to upgrade your RN version as well in order to get the latest fixes, especially when downgrading to the iOS 12.1 SDK seems to help.

[MaheshNandam]

@hramos, you are right, there are few compatibility issues's with newer 10.2 Xcode with RN and I solved it by replacing RCTBridegModule.h file with the latest version of RN.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.