TurboModuleRegistry: 'NativeReanimated' could not be found
Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'NativeReanimated' could not be foundShort answer
This means the JavaScript of react-native-reanimated loaded but its native code is not in the app binary. Rebuild the native app after install (pod install on iOS), add react-native-worklets for Reanimated 4, and use Reanimated 3 if the app is not on the New Architecture.
Fix it fast
1Find out which cause you have
Check which Reanimated and Worklets versions the project has, and whether the app was rebuilt after they were added.
npm ls react-native-reanimated react-native-worklets react-native2Match what you see, then jump to its fix
- 1
Native part of Reanimated doesn't seem to be initialized, right after install or upgradeThe native app was not rebuilt after installing ReanimatedFix - 2
Unable to find a specification for RNWorklets depended upon by RNReanimatedreact-native-worklets is not installed (Reanimated 4)Fix - 3
The error starts after upgrading Reanimated to 4.x in an app on the old architectureReanimated 4 in an app that is not on the New ArchitectureFix
- 1
What does the error look like?
Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'NativeReanimated' could not be foundNative part of Reanimated doesn't seem to be initializedUnable to find a specification for RNWorklets depended upon by RNReanimated
Cause 1 of 3
The native app was not rebuilt after installing Reanimated
1Check
A Metro reload only updates JavaScript. Native modules arrive only through a new native build.
ls ios/Pods | grep -i reanimated2Fix
Install pods (React Native CLI) or run prebuild (Expo), then build and run the native app again.
# React Native CLI
cd ios && pod install && cd ..
npx react-native run-ios
# Expo
npx expo prebuild3Verify
Start Metro with a clean cache and open the app.
npm start -- --reset-cacheConfirmed by docs.swmansion.com
Cause 2 of 3
react-native-worklets is not installed (Reanimated 4)
1Check
The troubleshooting guide names this error as a missing react-native-worklets package.
npm ls react-native-worklets2Fix
Install react-native-worklets in a version compatible with your Reanimated version, add its Babel plugin last in babel.config.js, and install pods again.
npm install react-native-worklets
# babel.config.js: plugins: ['react-native-worklets/plugin'] (listed last)
cd ios && pod install && cd ..3Verify
Rebuild the app.
npx react-native run-iosConfirmed by docs.swmansion.com
Cause 3 of 3
Reanimated 4 in an app that is not on the New Architecture
1Check
The getting-started page states that Reanimated 4 requires the New Architecture (Fabric).
npm ls react-native-reanimated2Fix
Either move the app to the New Architecture, or install Reanimated 3, which the same page names for the old architecture.
npm install react-native-reanimated@33Verify
Install pods and rebuild.
cd ios && pod install && cd ..
npx react-native run-iosConfirmed by docs.swmansion.com
How do I stop it coming back?
- After adding any package with native code, rebuild the app instead of reloading.
- Pin react-native-reanimated and react-native-worklets together and upgrade them in one commit.
- Keep the worklets Babel plugin last in the plugins array.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Mobile apps
Android build stops at processDebugManifest in a React Native app
Manifest merger failed
processDebugManifest is the step that merges your AndroidManifest.xml with the manifests of every library.
2 causes, each with a fixMobile apps
Running pod on a React Native project fails with can't find gem cocoapods
can't find gem cocoapods (>= 0.a) with executable pod
The pod command exists, but the Ruby that is running it has no CocoaPods gem.
3 causes, each with a fixMobile apps
React Native Android build cannot find the foojay-resolver-convention plugin
Plugin [id: 'org.gradle.toolchains.foojay-resolver-convention'] was not found in any of the following sources:
The foojay plugin is a settings plugin that Gradle downloads from the Plugin Portal.
3 causes, each with a fixMobile apps
Kotlin and Java compile to different JVM targets in a React Native Android build
'compileJava' task (current target is 1.8) and 'compileKotlin' task (current target is 11)
Gradle refuses to build when the Java task and the Kotlin task target different JVM versions.
3 causes, each with a fixMobile apps
Gradle cannot run node in a React Native Android build
Process 'command 'node'' finished with non-zero exit value 1
The React Native Gradle plugin starts node for bundling.
3 causes, each with a fixMobile apps
The Android emulator opens the app but never connects to Metro or Expo
Metro bundler ECONNREFUSED 127.0.0.1:19001
When the emulator cannot reach Metro, first prove each side on its own: adb sees the emulator, and Metro listens on its port.
4 causes, each with a fix