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
Can use Hermes on a new project #931
Comments
Duplicate of #952 |
@kelset the post install phase replacing ayomic_notify_one might be of interest to you here |
Ah, it seems it is not related to hermes, I just tried updating to rn-macos 0.66 and it's not working. I'll create a new issue later |
@ospfranco I think you need this in your podfile: https://github.com/microsoft/react-native-macos/blob/main/packages/rn-tester/Podfile#L100-L102 |
@Saadnajmi thanks a lot, that error is gone, but now I'm getting arm64 compilation errors, some people seem to have solved this by compiling the app in Rosetta mode? |
@ospfranco I run into that intermittently and haven't found a cause. I suspect it might be an xcode incremental build problem. One thing to try is to do a full clean (cmd+shift+k) in xcode before building. |
Already tried that, also deleting the derived data folder, still no luck :( |
I initialized a brand new project and there it seems to be working |
I managed to get it working after resetting a bunch of swift flags in the Build Settings with a brand new rn-macos project, some of my changes:
|
Environment
Steps to reproduce the bug
I created a new RN macOS project the other day, I wanted to start right away with Hermes, I followed the installation instructions and I got to the following issue:
https://stackoverflow.com/questions/68497865/rct-folly-error-when-using-hermes-with-ios
Debugging it is very confusing since all the info online points to flipper on iOS, but on macOS there is no flipper... anyways, I tried updating a bunch of things and had to resort to a similar solution to the one on the stack overflow answer on my Podfile:
is there any plan to fix this (AFAIK RCT-Folly already fixed this in some of the later versions?)
Expected Behavior
No response
Actual Behavior
No response
Reproducible Demo
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: