-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Problem with third-party in Xcode 10 building to iOS physical device #19839
Comments
Can you try using the latest 0.56 RC? That release contains some related fixes and we'd like to ensure the issue you're describing is not something that is already fixed. |
I've applied manual fixes for |
Not @dlimx, but can report the same. Using the latest (-1) RC.
This error also occurs when building for a "Generic iOS Device" I saw that there was a version bump to rc.3, I couldn't use |
@hramos In response to your question^^, I'm using the same environment as OP and having the same issue on rc.2, rc.3, and rc.4 |
This comment has been minimized.
This comment has been minimized.
It happens to me on a recently created RN project, but I'm using xCode 9.4 |
I got error as well after updating to Xcode 10. Build goes fine for simulators but not for Generic / Physical Devices. This is blocking development using Xcode 10 atm :( Which wouldn't be a problem if we could use Xcode 9.4. But that means we cannot develop with iOS 12.
|
I haven't. I can try but I don't expect this will make a difference. I think this has something to do with the glog library: During the build / configure step of that library it outputs the follow:
...
checking for sys/ucontext.h... yes
checking how to access the program counter from a struct ucontext... uc_mcontext->__ss.__rip
checking that generated files are newer than configure... done
... Looking at the relevant script it seems that they do some one-off trial 'n error for obtaining this "program counter":
Which in turn only works for simulators (which is the same architecture as macOS: darwin/x86) but no longer for devices (darwin/arm) |
I found a workaround but its untested: Replace: /* How to access the PC from a struct ucontext */
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__rip With: /* How to access the PC from a struct ucontext */
#if defined(__arm__) || defined(__arm64__)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__pc
#else
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__rip
#endif Using this it will compile for both targets. My knowledge is pretty much absent regarding the use of these values. Except that
|
Well in 0.57 we use glog 0.3.5, maybe that script is fixed there? |
@kelset I missed that part. I give it a try! |
I updated to 0.57.0 and did a full clean using: rm -rf node_modules
npm cache clear --force ; watchman watch-del-all ; rm -rf $TMPDIR/react-* ; rm -rf ~/.rncache But the error remains the same. The above workaround still seems to work though. |
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 With earlier iterations (both Xcode / RN) I was running the glog But that actually produces a 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 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The original issue appears to be resolved in 0.57. For anything else related to third party dependencies, the issue you're looking for is #20774. |
Environment:
__
Description
third-party
encounters a semantic issue during Xcode builds to physical iOS device. The error isNo member named '__rip' in '__darwin_arm_thread_state64'
Reproducible Demo
On macOS Mojave with Xcode 10.
Fails due to
No member named '__rip' in '__darwin_arm_thread_state64'
The text was updated successfully, but these errors were encountered: