Tracking dependencies while using expo run:ios

Expo Development Tools
1

Expo sdk: 42

My expo EAS build is crashing when released for testflight. Tried to debug in expo production mode and followed expo guide. Tried to build the project locally on Xcode using expo run:ios. Which helped me track down possibilities of having failure with one of my packages, i.e., react-native-reanimated. But after removing the package from my dependencies, I ran expo run:ios and it happens to reinstall that package again. Below is my package.json, any kind of help is welcome!

  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject"
  },
  "dependencies": {
    "@react-native-async-storage/async-storage": "^1.15.9",
    "@react-native-community/masked-view": "0.1.10",
    "@react-native-community/viewpager": "5.0.11",
    "@react-navigation/core": "^6.1.0",
    "@react-navigation/material-bottom-tabs": "^5.3.15",
    "@react-navigation/native": "^5.9.4",
    "@react-navigation/stack": "^5.14.5",
    "@stripe/stripe-react-native": "0.1.4",
    "card-validator": "^8.1.1",
    "expo": "~42.0.1",
    "expo-av": "~9.2.3",
    "expo-camera": "~11.2.2",
    "expo-constants": "~11.0.1",
    "expo-image-picker": "~10.2.2",
    "expo-linear-gradient": "~9.2.0",
    "expo-media-library": "~12.1.2",
    "expo-status-bar": "~1.0.4",
    "firebase": "8.2.3",
    "lottie-react-native": "4.0.2",
    "moment": "^2.29.1",
    "prop-types": "^15.7.2",
    "react": "16.13.1",
    "react-dom": "16.13.1",
    "react-native": "https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz",
    "react-native-animatable": "^1.3.3",
    "react-native-confetti": "^0.1.0",
    "react-native-confetti-cannon": "^1.5.2",
    "react-native-gesture-handler": "~1.10.2",
    "react-native-icon-badge": "^1.1.3",
    "react-native-keyboard-aware-scroll-view": "^0.9.4",
    "react-native-masked-text": "^1.13.0",
    "react-native-paper": "^4.9.2",
    "react-native-safe-area-context": "3.2.0",
    "react-native-screens": "~3.4.0",
    "react-native-slick": "^1.6.0",
    "react-native-vector-icons": "^8.1.0",
    "react-native-web": "~0.13.12",
    "react-redux": "^7.2.4",
    "redux": "^4.1.0",
    "redux-thunk": "^2.3.0",
    "styled-components": "^5.3.1",
    "unimodules-permissions-interface": "^6.1.0",
    "uuid-random": "^1.3.2",
    "yup": "^0.32.11"
  },
  "devDependencies": {
    "@babel/core": "^7.9.0"
  },
  "private": true
}```
2

Hey @sanmati846, you can run yarn why to determine why a package is installed in your project (such as another of your dependencies relying on it/installing it.

Cheers,
Adam

3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.