Getting error after running eas build

I just am trying to upload my with I created with expo when I run the eas build --platform android they process will start and stop at the install dependencies showing the below error:

Running "npm install" in the root dir of your repository 
[stderr] npm ERR!
[stderr] code ERESOLVE
[stderr] npm ERR!
[stderr] ERESOLVE could not resolve
[stderr] npm
[stderr] ERR!
[stderr] npm ERR! While resolving: react-native-qrcode-svg@6.1.2
[stderr] npm ERR! Found: react-native-svg@13.4.0
[stderr] npm ERR! node_modules/react-native-svg
[stderr] npm
[stderr] ERR!   react-native-svg@"^13.4.0" from the root project
[stderr] npm ERR! 
[stderr] npm ERR! Could not resolve dependency:
[stderr] npm ERR! peer react-native-svg@"^12.1.0" from react-native-qrcode-svg@6.1.2
[stderr] npm ERR! node_modules/react-native-qrcode-svg
[stderr] npm ERR!   react-native-qrcode-svg@"^6.1.2" from the root project
[stderr] npm ERR! 
[stderr] npm ERR! Conflicting peer dependency: react-native-svg@12.5.0
[stderr] npm ERR! node_modules/react-native-svg
[stderr] npm ERR!   peer react-native-svg@"^12.1.0" from react-native-qrcode-svg@6.1.2
[stderr] npm ERR!   node_modules/react-native-qrcode-svg
[stderr] npm
[stderr] ERR!     react-native-qrcode-svg@"^6.1.2" from the root project
[stderr] npm ERR! 
[stderr] npm ERR! Fix the upstream dependency conflict, or retry
[stderr] npm ERR! this command with --force, or --legacy-peer-deps
[stderr] npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
[stderr] npm ERR! 
[stderr] npm ERR! See /home/expo/.npm/eresolve-report.txt for a full report.
[stderr] 
[stderr] npm ERR! A complete log of this run can be found in:
[stderr] npm ERR!     /home/expo/.npm/_logs/2023-01-15T12_37_33_265Z-debug-0.log

npm exited with non-zero code: 1

Below is the list of my dependencies:

├── @babel/core@7.20.2
├── @react-native-community/masked-view@0.1.11
├── @react-native-community/netinfo@9.3.5
├── @react-navigation/bottom-tabs@6.4.1
├── @react-navigation/native@6.0.14
├── @react-navigation/stack@6.3.5
├── axios@0.26.1
├── expo-app-loading@2.1.1
├── expo-blur@12.0.1
├── expo-dev-client@2.0.1
├── expo-font@11.0.1
├── expo-image-picker@14.0.2
├── expo-optimize@0.2.20
├── expo-screen-capture@5.0.0
├── expo-secure-store@12.0.0
├── expo-splash-screen@0.17.5
├── expo-status-bar@1.4.2
├── expo-updates@0.15.6
├── expo@47.0.8
├── formik@2.2.9
├── lottie-react-native@5.1.4
├── npm-check-updates@12.5.12
├── react-dom@18.1.0
├── react-native-animatable@1.3.3
├── react-native-autocomplete-dropdown@2.1.0
├── react-native-dashed-line@1.1.0
├── react-native-expo-image-cache@4.1.0
├── react-native-fast-image@8.6.3
├── react-native-gesture-handler@2.8.0
├── react-native-linear-gradient@2.6.2
├── react-native-maps@1.3.2
├── react-native-pager-view@6.0.1
├── react-native-paper@4.12.5
├── react-native-paystack-webview@4.0.3
├── react-native-qrcode-svg@6.1.2
├── react-native-qrcode-transparent@0.2.6
├── react-native-qrcode@0.2.7
├── react-native-read-more-text@1.1.2
├── react-native-reanimated@2.12.0
├── react-native-safe-area-context@4.4.1
├── react-native-screens@3.18.2
├── react-native-select-dropdown@1.13.0
├── react-native-shared-element@0.8.4
├── react-native-svg@13.4.0
├── react-native-swiper-flatlist@3.0.17
├── react-native-swiper@1.6.0
├── react-native-tab-view@3.3.0
├── react-native-web@0.18.10
├── react-native-webview@11.23.1
├── react-native@0.70.5
├── react-navigation-shared-element@3.1.3
├── react@18.1.0
└── yup@0.32.11

I appreciate your help, thanks

Hi @onseyi

This means that you have directly installed react-native-svg version 13.x, but you’ve also installed react-native-qrcode-svg, which says that it has a “peer dependency” on react-native-svg version 12.x so npm is telling you there’s a conflict.

Ideally, react-native-qrcode-svg should update its react-native-svg peer dependency to 13.x (so you might want to contact them about this problem), but you can work around it by installing with the legacy-peer-deps option.

e.g.:

Thanks @wodin it worked, I appreciate, but I have a question.

what if I want to update the app, after working on a new screen hope the same error will not appear and secondly, you made mention of many ways to do it, just for the purpose of understanding can you name others, once you are less busy.

Thanks