Fatal Exception: com.facebook.jni.CppException Maximum call stack size exceeded (native stack depth) RangeError: Maximum call stack size exceeded (native stack depth) at apply (native) at anonymous on release android apk

[NadeemKhanFh]

Description

hey, i am facing this issue on release apk android. debug is working fine.

Steps to reproduce

1. make android release apk
2. install it
3. build crashes

Snack or a link to a repository

no snack

Reanimated version

3.5.1

React Native version

0.71.12

Platforms

Android

JavaScript runtime

None

Workflow

None

Architecture

None

Build type

Release mode

Device

Real device

Device model

redme note 11 pro

Acknowledgements

Yes

[github-actions]

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?

[NadeemKhanFh]

here are the complete logs

com.cheezious_issue_0b598d98548bbd9c1bd7807151e229af_crash_session_6504375E037D000135881127C9F1961A_DNE_0_v2_stacktrace.txt

[manoj-makkuboy]

#5067 The patch is mentioned here but still no release.

[tjzel]

Fixed in 3.5.2.

[Vrunalbenke]

Fixed in 3.5.2.

can u share how you fixed this error, because i am also getting same error in release apk

[iamrohitagg]

I am on the latest version(3.5.4) and getting the crash.

[tjzel]

@Vrunalbenke It was fixed with #5087. Make sure you reset your bundler's cache after upgrading. If the issue persists, please attach some logs and preferably check if your runOnJS function (node_modules/react-native-reanimated/src/reanimated2/threads.ts) is the same as in the npm package.

[pabloluz]

Updated to 3.5.4 and keep getting the same error in release APK.

Bundler's cache was reset and checked runOnJS function is the same as in the NPM package.

[tjzel]

@pabloluz I believe this is fixed in #5264. Please confirm if it's gone for you on our nightly version react-native-reanimated@nightly.

[pabloluz]

@pabloluz I believe this is fixed in #5264. Please confirm if it's gone for you on our nightly version react-native-reanimated@nightly.

I can confirm react-native-reanimated@nightly is working in prod, the exception I mentioned above is not happening anymore. Thank you very much @tjzel!

[Pingou]

Hi all, did you all have the same stacktrace with the error appearing in apply()?
I am experiencing the same error since upgrading to react native 71 but the stacktrace is a bit different and occurs in render. Upgrading reanimated didn't fix the issue.

[tjzel]

@Pingou This should be fixed. Feel free to open another issue with your error.