Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

TurboModuleRegistry: 'NativeReanimated' could not be found

ErrorInvariant Violation: TurboModuleRegistry.getEnforcing(...): 'NativeReanimated' could not be found

Short 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.

  • Applies to React Native 0.8x, react-native-reanimated 4.x, react-native-worklets
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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-native
  2. 2Match what you see, then jump to its fix

    1. 1Native part of Reanimated doesn't seem to be initialized, right after install or upgradeThe native app was not rebuilt after installing ReanimatedFix
    2. 2Unable to find a specification for RNWorklets depended upon by RNReanimatedreact-native-worklets is not installed (Reanimated 4)Fix
    3. 3The 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

What does the error look like?

  • Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'NativeReanimated' could not be found
  • Native part of Reanimated doesn't seem to be initialized
  • Unable 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 reanimated

2Fix

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 prebuild

3Verify

Start Metro with a clean cache and open the app.

npm start -- --reset-cache

Confirmed by docs.swmansion.com

Did this fix it?

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-worklets

2Fix

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-ios

Confirmed by docs.swmansion.com

Did this fix it?

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-reanimated

2Fix

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@3

3Verify

Install pods and rebuild.

cd ios && pod install && cd ..
npx react-native run-ios

Confirmed by docs.swmansion.com

Did this fix it?

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:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.