-
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
0.69.4 hermes crashes with use_frameworks! enabled #34381
Comments
Comment out use_flipper in podFile then its working fine use_fipper is not working with use_framework! |
Yeah I have that commented out.
I cannot get it to not crash without -
Is something missing in the fix for hermes? |
My package.json:
|
Do I need |
We ran into this issue, too. react-native-firebase https://rnfirebase.io/#altering-cocoapods-to-use-frameworks For us, the solution was to downgrade It's trivial to reproduce this issue. Just bootstrap a new, vanilla |
Thank you! SO they can fix it. It locks up on real device in Release mode, not on simulator.
|
FWIW, it crashes if you run a |
Can we cherry pick - this one? |
I have the same issue with my project as well as a Vanilla rn app. |
same with 0.69.5 too, |
Yeah, can confirm 0.69.5 crashes on Release iOS build with What's almost worse is that development builds work. They apparently silently fall back to JSC.
The fix for this seem to clearly lie with react-native or hermes. How can we get this issue some attention? It's likely impacting a lot of people. |
Anyone - thoughts? I am happy to help figure it out - but no idea why it is crashing. |
react-native-reanimated/pull/3491 this solution it work for me |
@nanthawat can you go into more details about how you applied the fix[1]? The PR you linked modifies a podspec -- are you applying the same kind of modification but to the podfile? |
OK this appears to work on react-native-reanimated. We need t get that pushed out ....
|
Try to use add :linkage => :static to use_framework.
|
same. |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Description
Using RN 0.69.4 and enabled hermes causes crash.
Able to get it working with Podfile changes, or disabling hermes.
It crashes at Could not get BatchedBridge, make sure your bundle is packaged correctly:
Is this acceptable solution or is there another work-around?
Version
0.69.4
Output of
npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 12.4
CPU: (10) arm64 Apple M1 Max
Memory: 159.59 MB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.16.0 - /usr/local/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 8.11.0 - /usr/local/bin/npm
Watchman: 2022.03.21.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 25, 26, 27, 28, 29, 30, 31
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0
System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-31 | Intel x86 Atom_64, android-31 | Google APIs ARM 64 v8a, android-31 | Google APIs Intel x86 Atom_64, android-32 | Google APIs ARM 64 v8a, android-R | Google APIs Intel x86 Atom, chromeos-67 | Chrome OS 67
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8609683
Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
Languages:
Java: 11.0.16 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
See above desc.
Snack, code example, screenshot, or link to a repository
Nothing more.
The text was updated successfully, but these errors were encountered: