react-native-reanimated: Upgrading 0.72.0-rc.5 with 3.2.0 causes runtime error with metro.

Description

I’m experiencing an error after upgrading RN to 0.72.0-rc.5. I tried reseting the cache with yarn start --reset-cache too.

 ERROR  Error: [Reanimated] The native part of Reanimated doesn't seem to be initialized. This could be caused by
  - not rebuilding the app after installing or upgrading Reanimated
  - trying to run Reanimated on an unsupported platform
  - running in a brownfield app without manually initializing the native library, js engine: hermes
 LOG  Running "mobile" with {"rootTag":1,"initialProps":{}}
 ERROR  Invariant Violation: "mobile" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes
CleanShot 2023-06-01 at 12 01 12@2x

Steps to reproduce

  1. Create a project with reanimated 3.2.0
  2. Upgrade React Native to 0.72.0-rc.5
  3. Run the app

Snack or a link to a repository

n/a

Reanimated version

3.2.0

React Native version

0.72.0-rc.5

Platforms

iOS

JavaScript runtime

None

Workflow

React Native (without Expo)

Architecture

Paper (Old Architecture)

Build type

Debug mode

Device

iOS simulator

Device model

No response

Acknowledgements

Yes

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 5
  • Comments: 21 (7 by maintainers)

Commits related to this issue

Most upvoted comments

Hey @gtokman, thanks for reporting this issue. We’re actively working on it but adding support for upcoming releases is not that easy these days. Will keep you updated!

I upgraded from 2.14.4 to 3.3.0 and am now seeing this error. How exactly should the native part be initialized? Should I call something in AppDelegate?

RN version is 0.72.0