[SDK39] Animated node with ID 2 already exists

🐛 Bug Report

Summary of Issue

Animated node with ID 2 already exists error after updating to sdk 39
image

Environment – output of expo diagnostics & the platform(s) you’re targeting

`Expo CLI 3.27.7 environment info:

System:
  OS: Windows 10 10.0.18362
Binaries:
  Node: 12.16.2 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.4 - C:\Users\ST\AppData\Roaming\npm\yarn.CMD
  npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
IDEs:
  Android Studio: Version  3.6.0.0 AI-192.7142.36.36.6392135
npmPackages:
  expo: ^39.0.0 => 39.0.2 
  react: 16.13.1 => 16.13.1 
  react-dom: 16.13.1 => 16.13.1 
  react-native: https://github.com/expo/react-native/archive/sdk-39.0.0.tar.gz => 0.63.2
  react-native-web: ~0.13.7 => 0.13.13
  react-navigation: ^4.4.0 => 4.4.0
Expo Workflow: managed

`

“react-native-skeleton-content”: “^1.0.20”
“react-native-reanimated”: “~1.13.0”,

Steps to Reproduce

This happens when you update SDK 39.

Expected Behavior vs Actual Behavior

I updated all the packages, but the results were the same.
Should I wait for an update from another package?

In the previous case, it seems that the sdk has been updated and has been modified!..
alexZajac/react-native-skeleton-content-nonexpo#15 (comment)

1 possible answer(s) on “[SDK39] Animated node with ID 2 already exists

  1. Hey! This problem usually occurs when there are more than one react-native-reanimated version in the project. Try running yarn why react-native-reanimated / npm ls react-native-reanimated to see what versions of the dependency are installed. Most probably you’ll have at least two: v2.0.0-alpha.6 (from package.json) and v1.x.x (installed by some other dependency). Could you please verify if that’s the case?