Repository navigation
React Native Debugger - ERROR - TurboModuleRegistry.getEnforcing(...): 'NativeReanimated' #1663
Description
Description
Running a basic example in an Expo client while running React Native Debugger on port 19000. Getting the following error:
Invariant Violation
ExceptionsManager.js:179
TurboModuleRegistry.getEnforcing(...): 'NativeReanimated' could not be found. Verify that a module by this name is registered in the native binary.
Screenshots
Steps To Reproduce
Expected behavior
No errors
Actual behavior
Error (see above)
Snack or minimal code example
import Animated, {
useSharedValue,
withTiming,
useAnimatedStyle,
Easing,
} from "react-native-reanimated";
import { View, Button } from "react-native";
import React from "react";
export default function AnimatedStyleUpdateExample(props) {
const randomWidth = useSharedValue(10);
const config = {
duration: 500,
easing: Easing.bezier(0.5, 0.01, 0, 1),
};
const style = useAnimatedStyle(() => {
return {
width: withTiming(randomWidth.value, config),
};
});
return (
<View>
<Animated.View
style={[
{ width: 100, height: 80, backgroundColor: "black", margin: 30 },
style,
]}
/>
<Button
title="toggle"
onPress={() => {
randomWidth.value = Math.random() * 350;
}}
/>
</View>
);
}
Package versions
{
"dependencies": {
"@react-native-async-storage/async-storage": "^1.13.3",
"expo": "~40.0.0",
"expo-status-bar": "~1.0.3",
"react": "16.13.1",
"react-dom": "16.13.1",
"react-native": "https://github.com/expo/react-native/archive/sdk-40.0.1.tar.gz",
"react-native-reanimated": "2.0.0-rc.0",
"react-native-web": "~0.13.12"
},
"devDependencies": {
"@babel/core": "~7.9.0",
"babel-preset-expo": "8.3.0"
},
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo web",
"eject": "expo eject"
},
"private": true
}
Activity
github-actions commentedon Jan 27, 2021
Issue validator
The issue is valid!
productdevbook commentedon Feb 1, 2021
The same problem happened with me.
piaskowyk commentedon Feb 1, 2021
Hey @ionflow
My first association with this issue is a missing configuration Reanimated for android. Did you add a dependency to
MainApplication.java, enabled Hermes, and added the babel plugin? It isn't added by default, unfortunately 😕Look at this instruction: https://docs.swmansion.com/react-native-reanimated/docs/installation
Please let me know if it doesn't help then I will check this.
productdevbook commentedon Feb 1, 2021
@piaskowyk
These are all attached. I am having the same problem.
dpyeates commentedon Feb 1, 2021
I see this on iOS. It ONLY happens when you turn on debugging. With debugging turned off it does not occur.
jgonet commentedon Feb 1, 2021
Have you tried using Flipper for debugging?
Remote debugging in Chrome works by running JS code in Chrome's V8 and connecting to the Bridge. We use Turbomodules (which don't use Bridge at all) so Chrome can't connect with the native side – this error is expected but could be described better.
AFAIK Flipper should work with Android without problems on any recent RN version and iOS should work after RN 0.64.
EDIT: Seems like Flipper doesn't work with Expo yet. If you need a debugger functionality you probably should wait with the Reanimated upgrade.
productdevbook commentedon Feb 1, 2021
@jakub-gonet hmm flipper used thank you.
How to console.log() see flipper ?
walterholohan commentedon Feb 20, 2021
@jakub-gonet when do you think a update will be pushed to fix this issue?
We are using this library in a project however some of our developers use the chrome debugger to debug our app on a physical ios device. Flipper is sometimes difficult to get working on a real physical device.
jgonet commentedon Feb 20, 2021
It's not a matter of fixing this issue - chrome debugging works via running JS in the browser and establishing a tunnel to the native app via the bridge. Turbomodules doesn't use the bridge and they're C++ binaries without any means of communication so running their code through chrome is impossible. The only way to debug a component written with turbomodule integration is by using Flipper.
eee9 commentedon Mar 8, 2021
The same error on react native cli project. react native reanimated 2.0.0.
It doesn't matter device/emulator and Hermes on/off. Android version only checked.
When I downgrade react native reanimated to 1.13.2 the error disappear.
arled commentedon Mar 27, 2021
This is still an issue. is there a fix for this?!!!!!!
walterholohan commentedon Mar 28, 2021
@arled there is no fix. This is expected behaviour. Check out @jakub-gonet answer above. TLDR: use flipper to debug
Dakuan commentedon Mar 28, 2021
Flipper doesn't work with expo...we have reluctantly refactored to remove all our renanimated code :( vote here: https://expo.canny.io/feature-requests/p/integrate-flipper
range-of-motion commentedon Apr 5, 2021
Same issue here, once you enable debugging shit hits the fan (same error as OP).
fjaffrezic commentedon Apr 29, 2021
Same issue :-(
devshorts commentedon May 17, 2021
What does "use flipper to debug" even mean? Flipper doesn't have a way to connect to a debug port to set breakpoints. You still can't do performance profiling. If "debug" just means see "console.log" statements thats a poor statement of debugging, I can see that in the terminal now. What does flipper even give you?
1337mus commentedon Nov 6, 2021
@jakub-gonet Any thoughts on @devshorts comment above? Thanks in advance.
dj0024javia commentedon Mar 16, 2022
Any Updates on this?
AzeemSarwar1 commentedon Jul 25, 2023
No update till react-native-reanimated 3.3.0😩
piaskowyk commentedon Jul 25, 2023
Latest version of Reanimated 2 (2.17.0) and 3 (3.4.0). should supports remote debugger 🤔
amadeus commentedon Aug 15, 2023
When attempting to profile on the UI thread, I can start the profiler, but when I end it, the app crashes (both on ios and android) with the following error on Android: