-
Notifications
You must be signed in to change notification settings - Fork 44
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
Not working with use_frameworks! :linkage => :static (Expo 51 & RN 0.74.3) #261
Comments
I have the same issue if I use Update: |
Thank you @mrcool-ru! Indeed downgrading to version 7.2.0 seems to work. (sad because I had sightly more crash on android with the 7.2.0) Unfortunately, I have to use Hopefully the 7.4.0 will fix that |
I encountered a similar issue on ios. The build works fine in debug mode, but the IOS app crashes on startup with version |
+1 |
Same happening to me. It seems that use-frameworks is not compatible with latest 7.3.0 version. |
Thanks for reporting this! The problem is that our repo is a couple of RN versions behind. I've just started working on updating the it to support the latest couple of versions of RN. Step one is getting all of our packages upgraded to more recent versions while still using RN 0.72.x. This'll make it easier to do the next couple of upgrades. If anyone wants to give it a test on a 0.72.x project, that'd be super helpful: #267 |
I encountered the same issue and have been digging into it. IMO it's not related to Expo or React Native version as out-of-the-box, even latest versions are working fine with The issue seems to be tied to It seems like with static linkage, symbols from Rive’s Yoga fork are being exported, which is causing a collision with React Native’s Yoga and leading to that bad access error. I haven’t found a workaround, and I think this might need to be handled in Any thoughts or ideas? |
This should be resolved with 8.2.0. Please let me know if it doesn't work for you and we'll reopen this issue. Troubleshooting
|
I have a similar issue and upgrading to 8.2.0 this morning, following your debug steps, did not work for me.
|
Still having the same issue (EXC_BAD_ACCESS) on 8.2.0 (runtime 6.3.7) |
Sorry @casualWaist for the false positive on 8.2. I'm just pushing 8.3 to npm now. This one has been tested by a couple of different people with the same issue so I'm confident it'll fix the problem this time. If it doesn't, please let me know. |
I am upgrading from expo 50 to expo 51 with
"rive-react-native": "7.3.0"
My builds on android & ios are working.
Everything is working well on android.
after a successful
eas build -p ios --profile simulator --local --clear-cache
, I start the app and it crashes.I can see
0x10e7cc000 - 0x10eceffff rive.app.ios.runtime.RiveRuntime (5.14.0)
in the crash.I tried to remove
rive-react-native
from my app & it workedHas anyone managed to get it to work on Expo 51?
The text was updated successfully, but these errors were encountered: