Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Package Not Compatible with RN 0.63

See original GitHub issue

I upgraded my expo project which upgraded my RN version to 0.63.2

When I try to run npm install react-native-deck-swiper --save the below error is returned:

npm ERR! Found: react-native@0.63.2
npm ERR! node_modules/react-native
npm ERR!   react-native@"https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react-native@"^0.49.1" from react-native-deck-swiper@2.0.5

It looks like this package is requiring an older version of RN? Do you have any idea why it would be rejecting me?

My Expo Specs:

Expo CLI 4.0.4 environment info:
  System:
    OS: macOS 11.0.1
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.3.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.0.14 - /usr/local/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.0, macOS 11.1, tvOS 14.3, watchOS 7.2
  IDEs:
    Android Studio: 4.1 AI-201.8743.12.41.6953283
    Xcode: 12.3/12C5020f - /usr/bin/xcodebuild
  npmPackages:
    expo: ^39.0.0 => 39.0.5 
    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.3.tar.gz => 0.63.2 
    react-navigation: ^3.13.0 => 3.13.0 
  npmGlobalPackages:
    expo-cli: 4.0.4
  Expo Workflow: managed

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:7 (1 by maintainers)

Top GitHub Comments

1reaction

brtellercommented, Aug 13, 2022

So I’m using Expo to manage the project and I confirmed I’m using version 2.0.8. I was using npm which caused the conflicts. I switched over to using Yarn and it’s working now.

If the developers see this, this creates an issue of expo managed projects using npm which causes an issue of generating a proper info.plist whenever the iOS directory is created. Essentially making the usefulness of expo worthless.

I can confirm the package works fine, so if the developers could fix this dependency requirement to support newer versions of RN it should fix the issue. I’d imagine it’s relatively small of an issue since when I force it with no info.plist requirements it works fine but is completely unusable to send to the app store/running packages with npm.

0reactions

webraptorcommented, Jul 20, 2022

version 2.0.7 should work with latest RN / react combos.