react-native-reanimated: Crash with expo custom build (49.x or 50.x, or 51.x) when newArchEnabled set to true on iOS and with expo-dev-client installed

Description

When reloading (using r) and sometimes when starting the app, the app crash (on iOS, not Android) as soon as react-native-reanimated is installed, even if not used inside app, with the newArchEnabled.

As soon as your remove react-native-reanimted and expo prebuild --clean and yarn ios the app will no longer crash on boot or reload.

Just an fyi, you no longer need to add ‘react-native-reanimated/plugin’ in your babel.config.js with expo 50 as per their latest blog post.

Steps to reproduce

yarn create expo-app --template tabs@beta
yarn expo install --fix
yarn expo install expo-build-properties
add to app.json

      [
        "expo-build-properties",
        {
          "ios": {
            "newArchEnabled": true
          },
          "android": {
            "newArchEnabled": true
          }
        }
      ]

yarn expo install expo-dev-client
Change “react-native-safe-area-context”: “4.8.1”,
Change “react-native-screens”: “3.29.0”,
Add this to package.json

  "expo": {
    "install": {
      "exclude": [
        "react-native-safe-area-context",
        "react-native-screens"
      ]
    }
  }

Change this inside package.json

    "android": "expo run:android",
    "ios": "expo run:ios",

yarn expo install react-native-reanimated
yarn ios

Snack or a link to a repository

https://github.com/sync/new-arch-crash

Reanimated version

3.6.1

React Native version

0.73.0

Platforms

iOS

JavaScript runtime

Hermes

Workflow

Expo Dev Client

Architecture

Fabric (New Architecture)

Build type

Debug app & dev bundle

Device

iOS simulator

Device model

iPhone 15 Pro

Acknowledgements

Yes

About this issue

Original URL
State: closed
Created 7 months ago
Reactions: 4
Comments: 28 (11 by maintainers)

Commits related to this issue

Prevent iOS bridgeless initialization from getting the wrong bridge (#5953) ## Summary As I pointed out [here](https://github.com/software-mansion/react-native-reanimated/pull/5901#discussion_r15677... — committed to software-mansion/react-native-reanimated by gabrieldonadel 2 months ago

Most upvoted comments

@gabrieldonadel

the-office-michael-scott

tjzel on Dec 22, 2023

I have a similar problem without expo and newArch. The problem occurs when the application is reloading

react-native: 0.73.2
react-native-reanimated: ^3.6.1

Screenshot 2024-01-19 at 11 10 55

RalissonMattias on Jan 19, 2024

@tjzel tested with latest version of expo 51 beta with yarn create expo-app --template default@beta and I am experiencing the same issues on boot or hot reload with the new architecture enabled, see repro here: https://github.com/sync/pastlife

Version of reanimated: => Found "react-native-reanimated@3.9.0-rc.1"

 (NOBRIDGE) ERROR  Error: [Reanimated] Native part of Reanimated doesn't seem to be initialized.

cc @brentvatne

sync on Apr 26, 2024

Update: Since React Native is going to come with bridge-less mode by default in 0.74 release, the code that causes this issue is very likely to undergo major changes. Therefore, until we adapt Reanimated to bridge-less mode, we will wait with this issue to see if it’s resolved then.

tjzel on Feb 22, 2024

updated sample reproduction repo with latest expo and reanimated 3.7.0, crashes like before, haven’t had a chance to have a deeper look so far

sync on Feb 13, 2024

@sync It seems to be a different issue, probably on the Expo side this time – we’ll investigate this.

tsapeta on Apr 30, 2024

Yeah, the problem is the DevMenu bridge, which gets initialized along with the main app. I just tested an using self.bridge fixes the issue

gabrieldonadel on Apr 29, 2024

@sync - i tried this on a new project with sdk 51 beta and it works well for me on android, but had the same issue as you on ios: https://github.com/brentvatne/mittaz. @gabrieldonadel will investigate!

brentvatne on Apr 27, 2024

I reproduced with react-native 0.73.2 without expo and new architecture enabled

migueldaipre on Jan 19, 2024

@tjzel thanks for this, the issue: https://github.com/expo/expo/issues/25968

sync on Dec 15, 2023

Hi @sync, thanks for submitting this issue! I investigated it and it turns out there’s some problem with how React Native’s bridge is handled by/with Expo. I forwarded the issue to them.

tjzel on Dec 15, 2023