react-native-reanimated icon indicating copy to clipboard operation
react-native-reanimated copied to clipboard

Crash on iOS with RN 0.76.x and reanimated 3.16.7 after upgrade

Open fjmorant opened this issue 11 months ago • 12 comments

Description

App is randomly crashing on launch and getting issue in iOS using old architecture, this has happened since we upgrade it React Native to version 0.76.5 and reanimated to 3.16.7. It is difficult to determine the reason of it because it is very random but we can check the stacktraces.

Steps to reproduce

At launch of the app we are getting these stack traces all related to Hermes GC:

crash_init_4.txt crash_init_3.txt crash_init_2.txt crash_init.txt

Snack or a link to a repository

cannot share

Reanimated version

3.16.7

React Native version

0.76.5

Platforms

iOS

JavaScript runtime

Hermes

Workflow

React Native

Architecture

Paper (Old Architecture)

Build type

Release app & production bundle

Device

Real device

Device model

Any iPhone or iPAd

Acknowledgements

Yes

fjmorant avatar Feb 07 '25 09:02 fjmorant

Hey! 👋

The issue doesn't seem to contain a minimal reproduction.

Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?

github-actions[bot] avatar Feb 07 '25 09:02 github-actions[bot]

It seems from the stacktraces as if it was an excessive consumption or memory by animations due to some sort of too frequent operation

fjmorant avatar Feb 07 '25 11:02 fjmorant

Maybe these cherry picks can help to this crash https://github.com/software-mansion/react-native-reanimated/issues/6996

fjmorant avatar Feb 10 '25 09:02 fjmorant

We're seeing a crash that looks identical in our app as well. It started after upgrading several of our dependencies, including Reanimated from 3.6.3 to 3.16.7 and React-Native from 0.72.10 -> 0.76.6. Hoping that you're correct and the next release fixes the crashes.

iressler avatar Feb 21 '25 17:02 iressler

I'm on 3.17.5 and on 0.76.9 of react-native. That release didn't fix the problem for me :(. Any news on this matter?

MarlonAEC avatar Apr 29 '25 14:04 MarlonAEC

@MarlonAEC Hi, have you tried upgrading react-native to the latest version?

tomekzaw avatar May 05 '25 08:05 tomekzaw

@tomekzaw hello,

Did you try on last react native version (0.79.x). I tried and i encountered crash.

  • new arch disabled
  • react-native-reanimated: 3.17.5
  • react-native: 0.79.2

hasanalicansu avatar May 09 '25 08:05 hasanalicansu

I did tried @tomekzaw actually I'm struggling with the update. I found several issues while upgrading, the most annoying one is this:

error: no such module 'XXX'

error: failed to verify module interface of 'XXX' due to the errors above; the textual interface may be broken by project issues or a compiler bug

where XXX are several modules, to mention a few:

'React-Codegen',
'FirebaseSharedSwift',
'react-native-didomi',
'PromisesSwift',
'FBLPromises',
'FirebaseRemoteConfigInterop',
'FirebaseCoreInternal',
'FirebaseCore',
'FirebaseRemoteConfig',
'FirebaseABTesting',
'FirebaseInstallations',
'FirebaseSessions',
'FirebaseCoreExtension',
'AppAuth'

But anyways, I need to figure out the update first and make it work to see if I can replicate the original problem in this version, although as I mentioned in the other issue, I tried 3.17.1 and it worked fine I just landed in another problem which I'm still trying to figure it out

MarlonAEC avatar May 13 '25 14:05 MarlonAEC

Try updating to, at least, React Native 0.77.0. I believe Xcode 16.3 doesn't play well with versions bellow that. This fixed a similar crash to me.

RicardoJesusS4 avatar May 14 '25 11:05 RicardoJesusS4

We are seeing a lot of similar crashes, in fact our Sentry is swarmed with hundreds of different variations of EXC_BAD_ACCESS, big production app. I know that it happens randomly on app launch but I have never seen this happen locally. For us it started happening after we updated Expo from 52 to 53 which in turn prompted an updated of RN from 0.76.2 to 0.79.2 and Reanimated from 3.16.7 to 3.17.4 (among many other updates). Old arch, iOS only. I am not entirely convinced that this is the same issue, but some of our crash logs look very similar.

Shaninnik avatar Jul 03 '25 13:07 Shaninnik