React-native-reanimated: App is not starting up (RC 1) : ReferenceError: Can't find variable: _setGlobalConsole

Created on 18 Dec 2020  路  15Comments  路  Source: software-mansion/react-native-reanimated

Description

Screenshots

image

Steps To Reproduce

Expected behavior

App should start.

Actual behavior

App is stuck (error on start).

Snack or minimal code example

Package versions

  • React Native: 0.63
  • React Native Reanimated: v2 RC 1
馃彔 Reanimated2 馃悶 Bug

Most helpful comment

@JB-CHAUVIN I checked and this error also happens when you forget to add our babel plugin to babel config. Maybe that's your problem? Info here

All 15 comments

Issue validator - update # 1

Hello!
Congratulations! Your issue passed the validator! Thank you!

Hey @JB-CHAUVIN,
Just for sure - did you try to clean cache?
for example:
yarn cache clean && rm -r node_modules && yarn && cd ios && pod install && cd .. && yarn start --reset-cache

In my case, yarn start --reset-cache is working for me.

I had the same issue while using expo. I had to revert to 2.0.0-rc.0.

I had the same issue while using expo. I had to revert to 2.0.0-rc.0.

Same here. I also tried expo start -c with no luck.

Hey!
I see two cases here: either you didn't clear the cache or you are using expo.
In the second case, AFAIK, the latest version of reanimated 2, that expo supports is rc.0. Since rc.1 has native changes it won't work with rc.1. You can downgrade to rc.0 or wait for the expo to support rc.1.
The error you posted here comes exactly from this change.

@JB-CHAUVIN I checked and this error also happens when you forget to add our babel plugin to babel config. Maybe that's your problem? Info here

Not yet working with RN63.4+Typescript and Reanimated RC 1. I have tried downgrading to RC 0, almost same type of issue `ReferenceError: Can't find variable: _set*. Any pointers?

Clearing cache did not work, reinstalling the modules again did not make it work, (I am not using Expo, and I have the babel plugin set)

Can't find variable: _set*. Any pointers?

I see but what's the exact message in both cases? Those *** actually matter a lot. So could you tell me what stood for the stars *** for rc.0 and for rc.1?

The same here.
RN63.4+Typescript and Reanimated RC 1

@JB-CHAUVIN I checked and this error also happens when you forget to add our babel plugin to babel config. Maybe that's your problem? Info here

This is the answer for me. Add that plugin, restart with --reset-cache, problem solved. Thank you very much.

In my case worked when I did:

  • clean cache and node_modules - yarn cache clean && rm -r node_modules && yarn && cd ios && pod install
  • uninstall application from device
  • rebuild and install again application on device
  • run server with yarn --reset-cache

The same problem for me @piaskowyk solution didn't work for me

Same issue :(

I am using expo and rc.2 and ran into this issue suddenly. After reading this thread and this, I tried everything and the only workaround working is commenting out _setGlobalConsole(console) in node_modules/react-native-reanimated/src/reanimated2/core.js.
This comment is for those who are still struggling with this issue and not able to proceed like me. :)

Note: updating the package or reinstalling node_modules will reintroduce the issue until its fixed in react-native-reanimated

Was this page helpful?
0 / 5 - 0 ratings