Problem with third-party in Xcode 10 building to iOS physical device
See original GitHub issue- Review the documentation: https://facebook.github.io/react-native
- Search for existing issues: https://github.com/facebook/react-native/issues
- Use the latest React Native release: https://github.com/facebook/react-native/releases
Environment:
Environment:
OS: macOS 10.14
Node: 8.11.2
Yarn: 1.7.0
npm: 5.6.0
Watchman: 4.7.0
Xcode: Xcode 10.0 Build version 10L176w
Android Studio: 2.3 AI-162.4069837
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4
__
Description
third-party
encounters a semantic issue during Xcode builds to physical iOS device. The error is No member named '__rip' in '__darwin_arm_thread_state64'
Reproducible Demo
On macOS Mojave with Xcode 10.
react-native init Test
cd Test
yarn start
Xcode build to device
Fails due to No member named '__rip' in '__darwin_arm_thread_state64'
Issue Analytics
- State:
- Created 5 years ago
- Reactions:13
- Comments:20 (11 by maintainers)
Top Results From Across the Web
Running xCode 10 on device error | Apple Developer Forums
The simple card game I made up said build suceeded on simulator but not the device. I made a new program with simply...
Read more >Xcode is not linking the debugger to simulator and ...
This is currently happening on one machine of the team the other machine is working fine yet we are unable to solve the...
Read more >Troubleshooting on iOS devices - Unity - Manual
Using third party Thumb compiled native libraries. Such libraries trigger a known problem in the iOS SDK linker and might cause random crashes....
Read more >Install third-party software on iPad Simulator in Xcode?
No, it is not possible to install and run a 3rd party app on iPad Simulator, like you do on a physical iPad....
Read more >How to Deploy your App on an iPhone (Updated for 2019)
Testing your iOS app on a device is the best way to gauge performance issues before you deploy your app ... Launch Xcode...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Not @dlimx, but can report the same. Using the latest (-1) RC.
This error also occurs when building for a “Generic iOS Device” The error seem to stem from
signalhandler.cc
in theglog
folder, on line 78return (void*)context->PC_FROM_UCONTEXT;
I saw that there was a version bump to rc.3, I couldn’t use
react-native-git-upgrade
norreact-native upgrade
to upgrade to that version.The problems seems to be resolved now. I’m not entirely sure but I think it had to do with the way I was installing
glog
.With earlier iterations (both Xcode / RN) I was running the glog
./configure
script manually due to Xcode failing to do it properly.But that actually produces a
config.h
that breaks on Xcode 10. The following react-native script is actually required for getting the correctconfig.h
for Xcode 10: https://github.com/facebook/react-native/blob/v0.57.0/scripts/ios-configure-glog.sh#L44-L51 That will build glog with./configure --host arm-apple-darwin
and taking into account patching thePC_FROM_UCONTEXT
macro.I learned that Xcode 10 failed building / installing the third-party dependencies only at the first build and that subsequent builds actually takes care of installing
glog
correctly: https://github.com/facebook/react-native/issues/21168#issuecomment-422502787