New Bug: ReanimatedError: [Reanimated] Native part of Reanimated doesn't seem to be initialized

[jeeva-2311]

Description

When reanimated library is added to a expo managed workflow project this error occurs. I had a project where I used the library. The project worked fine in expo go build but in the final apk and in development build, the above error is thrown. I have followed exactly as per documentation, still the error is thrown.

Note: Previous issue opened for the same issue closed stating that the bug is fixed in RNv 76.5. However the bug occurs in this version too.

my package.json.

{
"name": "teach",
"version": "1.0.0",
"main": "index.ts",
"scripts": {
"start": "expo start",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web"
},
"dependencies": {
"@react-navigation/native": "^7.0.14",
"@react-navigation/native-stack": "^7.2.0",
"babel-preset-expo": "~12.0.0",
"expo": "~52.0.20",
"expo-dev-client": "~5.0.6",
"expo-status-bar": "~2.0.0",
"react": "18.3.1",
"react-native": "0.76.5",
"react-native-gesture-handler": "~2.20.2",
"react-native-reanimated": "~3.16.1",
"react-native-safe-area-context": "4.12.0",
"react-native-screens": "~4.1.0"
},
"devDependencies": {
"@babel/core": "^7.25.2",
"@types/react": "~18.3.12",
"typescript": "^5.3.3",
"@react-native-community/cli": "latest"
},
"private": true
}

babel.config
module.exports = function (api) {
api.cache(true);
return {
presets: ['babel-preset-expo'],
plugins: ['react-native-reanimated/plugin'],
};
};

metro.cofig.js
// Learn more https://docs.expo.io/guides/customizing-metro
const { wrapWithReanimatedMetroConfig } = require('react-native-reanimated/metro-config');
const { getDefaultConfig } = require('expo/metro-config');

/** @type {import('expo/metro-config').MetroConfig} */
const config = getDefaultConfig(__dirname);

module.exports = wrapWithReanimatedMetroConfig(config);

Steps to reproduce

1. create a expo app using blank typescript template.
2. install reanimated using npx expo install react-native-reanimated.
3. update babel and metro config file. (Although expo documentation states that this step is not necessary. Only reanimated 4. documentation recommends this step)
4. In the home page, define a example as per documentation.
5. create a development build.
6. The apk will not work.

Snack or a link to a repository

https://github.com/jeeva-2311/teacherBotTesting

Reanimated version

3.16.1

React Native version

76.5

Platforms

Android

JavaScript runtime

None

Workflow

Expo Dev Client

Architecture

None

Build type

Release app & dev bundle

Device

Real device

Device model

Google pixel 8

Acknowledgements

Yes

[rushant11]

@jeeva-2311 have you found out any solution?

[jeeva-2311]

When you use use any of the default example templates in expo while creating a project. The example will come pre installed with reanimated and this works. So I created a new project like this and ported everything from old project to the new one. The issue lies somewhere in the expo internal linking process and I not able to pinpoint the issue. But the package works in any of the expo example templates.

[PatrickLQuirk]

I have also had issues with this bug. When I created a default expo project, the project worked for me, but when others cloned the project, installed the packages, and ran it, they got this error.

[PatrickLQuirk]

My issue is fixed. More specifically, the error had to do with certain files not being able to be found. The reason this happened for me was that some of our team members had the repository in OneDrive, and it seems OneDrive was messing with the files. Cloning the repository to a folder that is not in OneDrive fixed the issue for me.

[Bhavik-smn]

i got this error can anyone have solution of it
ReanimatedError: [Reanimated] Native part of Reanimated doesn't seem to be initialized.
See https://docs.swmansion.com/react-native-reanimated/docs/guides/troubleshooting#native-part-of-reanimated-doesnt-seem-to-be-initialized for more details. [Component Stack]

[jeeva-2311]

So far you can either start the project with a expo example templates or if you are on windows, see if onedrive is syncing your folder. If it is, move out of onedrive folder and run npx expo install react-native-reanimated again

[Bhavik-smn]

So far you can either start the project with a expo example templates or if you are on windows, see if onedrive is syncing your folder. If it is, move out of onedrive folder and run npx expo install react-native-reanimated again

It's not in EXPO it's in CLI

[jeeva-2311]

RN v1.0 is completely changed and native libraries are now being directly rendered instead of in a separate bridge. Hopefully this solves the problem. So I am closing the issue for now. If anyone have this same issue, comment and we can work together