invariant violation: viewproptypes has been removed from react native. migrate to viewproptypes exported from 'deprecated-react-native-prop-types'.

Question

invariant violation: viewproptypes has been removed from react native. migrate to viewproptypes exported from 'deprecated-react-native-prop-types'.

jainmca21 opened this issue 2 years ago · comments

Getting below error after upgrading the RN version 0.69.1 when run 'npx react-native run-ios'.

invariant violation: ViewPropTypes has been removed from react native. migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.

In React-native version 0.69 'ViewPropTypes'. has been removed.

Sam van Leer · Answer 1 · Sat Jul 16 2022 00:13:08 GMT+0800 (China Standard Time)

Not sure if anyone is maintaining this anymore as stated on the README.

However, if you want to get it working you need to do the fpollowing:

run npm i deprecated-react-native-prop-types
go to /node-modules/react-native-camera/src/RNCamera.js
delete the imported ViewPropTypes from 'react-native'
add import {ViewPropTypes} from 'deprecated-react-native-prop-types'

This should get it working temporarily.

Aakash A · Answer 2 · Mon Jul 18 2022 04:04:23 GMT+0800 (China Standard Time)

Not sure if anyone is maintaining this anymore as stated on the README.

However, if you want to get it working you need to do the fpollowing:

run npm i deprecated-react-native-prop-types

go to /node-modules/react-native-camera/src/RNCamera.js

delete the imported ViewPropTypes from 'react-native'

add import {ViewPropTypes} from 'deprecated-react-native-prop-types'

This should get it working temporarily.

Worked for me

João Dematé Jr · Answer 3 · Tue Aug 09 2022 02:01:13 GMT+0800 (China Standard Time)

thanks 👯

Almas-Asghar-730 · Answer 4 · Fri Sep 16 2022 14:24:04 GMT+0800 (China Standard Time)

not using react native camera but getting the same error, is their any way to know which module is having the ViewPropTypes

Sam van Leer · Answer 5 · Fri Sep 16 2022 16:22:19 GMT+0800 (China Standard Time)

not using react native camera but getting the same error, is their any way to know which module is having the ViewPropTypes

Are you not getting any errors in Simulator? The error should point exactly to the file causing the issue.

jkester1986 · Answer 6 · Sat Oct 01 2022 02:40:13 GMT+0800 (China Standard Time)

not using react native camera but getting the same error, is their any way to know which module is having the ViewPropTypes

@Almas-Asghar-730 another known one is react-native-snap-carousel

Jan Dominik Franz · Answer 7 · Sat Oct 08 2022 21:12:00 GMT+0800 (China Standard Time)

Temporary solution works.
How can we make it work by switching to another library to have a long term solution?

Almas-Asghar-730 · Answer 8 · Mon Oct 10 2022 17:55:32 GMT+0800 (China Standard Time)

not using react native camera but getting the same error, is their any way to know which module is having the ViewPropTypes

Are you not getting any errors in Simulator? The error should point exactly to the file causing the issue.

no

Almas-Asghar-730 · Answer 9 · Mon Oct 10 2022 17:55:53 GMT+0800 (China Standard Time)

not using react native camera but getting the same error, is their any way to know which module is having the ViewPropTypes

@Almas-Asghar-730 another known one is react-native-snap-carousel

not using this too

jlok · Answer 10 · Thu Oct 27 2022 15:50:59 GMT+0800 (China Standard Time)

Temporary solution works. How can we make it work by switching to another library to have a long term solution?

Use the pr instead or branch your own with the fix included.
#3443
yarn add react-native-camera/react-native-camera#3443/head is a drop in replacement

jkester1986 · Answer 11 · Thu Oct 27 2022 20:34:59 GMT+0800 (China Standard Time)

Temporary solution works. How can we make it work by switching to another library to have a long term solution?

Use the pr instead or branch your own with the fix included. #3443 yarn add react-native-camera/react-native-camera#3443/head is a drop in replacement

Can also use patch-package

MdImranNazeer1011 · Answer 12 · Mon Nov 14 2022 20:22:33 GMT+0800 (China Standard Time)

I am getting this warning ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types, even I haven't used ViewPropTypes anywhere in my code. and error occured after using snap carousel.

jkester1986 · Answer 13 · Mon Nov 14 2022 22:27:57 GMT+0800 (China Standard Time)

I am getting this warning ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types, even I haven't used ViewPropTypes anywhere in my code. and error occured after using snap carousel.

@MdImranNazeer1011 as mentioned already, this is a known issue with that package. You will need to patch it, or fork it, or similar. IIRC there's an open PR in the package with a fix that's been requested for merge for months, it has the solution you need

Samih Sghier · Answer 14 · Wed Nov 23 2022 04:14:59 GMT+0800 (China Standard Time)

@jkester1986 patch-package not working

chandannath98 · Answer 15 · Wed Jan 11 2023 14:43:45 GMT+0800 (China Standard Time)

i am getting the same error
this is my package.json file

{
"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": {
"@expo/vector-icons": "^13.0.0",
"@react-native-async-storage/async-storage": "~1.17.3",
"@react-native-community/masked-view": "0.1.10",
"@react-navigation/bottom-tabs": "^5.11.2",
"@react-navigation/native": "^5.8.10",
"@react-navigation/stack": "^5.12.8",
"expo": "^47.0.0",
"expo-font": "~11.0.1",
"expo-linking": "~3.3.0",
"expo-status-bar": "~1.4.2",
"moment": "^2.29.1",
"react": "18.1.0",
"react-dom": "18.1.0",
"react-native": "0.70.5",
"react-native-elements": "^1.2.7",
"react-native-gesture-handler": "~2.8.0",
"react-native-paper": "^3.12.0",
"react-native-reanimated": "~2.12.0",
"react-native-safe-area-context": "4.4.1",
"react-native-screens": "~3.18.0",
"react-native-vector-icons": "^7.1.0",
"react-native-web": "~0.18.9",
"react-navigation": "^4.4.3",
"react-navigation-drawer": "^2.6.0",
"react-navigation-material-bottom-tabs": "^2.3.3",
"react-navigation-tabs": "^2.10.1",
"react-redux": "^7.2.2",
"redux": "^4.0.4",
"redux-thunk": "^2.3.0"
},
"devDependencies": {
"babel-preset-expo": "^8.3.0"
},
"private": true
}

russel rajitha · Answer 16 · Wed Jan 18 2023 17:05:21 GMT+0800 (China Standard Time)

why are they really doing this kind of change? i am using tons of libraries and suddenly getting this. is there one fix to apply all of these libraries?

vmsilva · Answer 17 · Wed Jan 18 2023 18:02:55 GMT+0800 (China Standard Time)

This issue occur because React-native 0.70 > deprecade ViewPropTypes from react-native, To solve this trouble remove ViewPropTypes import from react-native and them import from deprecated-react-native-prop-types, for now this is what can we do.

with my project its occur with react-native-snap-carousel.
"react": "18.1.0",
"react-native": "0.70.5",

chandannath98 · Answer 18 · Wed Jan 18 2023 18:09:49 GMT+0800 (China Standard Time)

i am getting the same error this is my package.json file

{ "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": { "@expo/vector-icons": "^13.0.0", "@react-native-async-storage/async-storage": "~1.17.3", "@react-native-community/masked-view": "0.1.10", "@react-navigation/bottom-tabs": "^5.11.2", "@react-navigation/native": "^5.8.10", "@react-navigation/stack": "^5.12.8", "expo": "^47.0.0", "expo-font": "~11.0.1", "expo-linking": "~3.3.0", "expo-status-bar": "~1.4.2", "moment": "^2.29.1", "react": "18.1.0", "react-dom": "18.1.0", "react-native": "0.70.5", "react-native-elements": "^1.2.7", "react-native-gesture-handler": "~2.8.0", "react-native-paper": "^3.12.0", "react-native-reanimated": "~2.12.0", "react-native-safe-area-context": "4.4.1", "react-native-screens": "~3.18.0", "react-native-vector-icons": "^7.1.0", "react-native-web": "~0.18.9", "react-navigation": "^4.4.3", "react-navigation-drawer": "^2.6.0", "react-navigation-material-bottom-tabs": "^2.3.3", "react-navigation-tabs": "^2.10.1", "react-redux": "^7.2.2", "redux": "^4.0.4", "redux-thunk": "^2.3.0" }, "devDependencies": { "babel-preset-expo": "^8.3.0" }, "private": true }

the issue is in my "react-native-elements" package version, after updating the package my issue was solved.

mikeRChambers610 · Answer 19 · Wed Feb 15 2023 21:47:54 GMT+0800 (China Standard Time)

They never fail to make our lives difficult.

Anas Alaqeel · Answer 20 · Thu Feb 16 2023 01:12:17 GMT+0800 (China Standard Time)

none of the above works for me because I don't even have react-native-camera module in my app it was from react-native-snap-carousel module, so I finally fixed it. see the link for the solution
https://stackoverflow.com/a/75463206/12861001

jkester1986 · Answer 21 · Thu Feb 16 2023 01:25:08 GMT+0800 (China Standard Time)

none of the above works for me because I don't even have react-native-camera module in my app it was from react-native-snap-carousel module, so I finally fixed it. see the link for the solution https://stackoverflow.com/a/75463206/12861001

yep, patch-package (which is in the stackoverflow solution) has been mentioned, I think people are overlooking it though. patch-package is probably the best solution, short of forking whichever repo is causing the problem in order to fix it

KiranSayone · Answer 22 · Tue Apr 25 2023 14:14:26 GMT+0800 (China Standard Time)

none of the above works for me because I don't even have react-native-camera module in my app it was from react-native-snap-carousel module, so I finally fixed it. see the link for the solution https://stackoverflow.com/a/75463206/12861001

yep, patch-package (which is in the stackoverflow solution) has been mentioned, I think people are overlooking it though. patch-package is probably the best solution, short of forking whichever repo is causing the problem in order to fix it

But don't we need to apply the patch each time we clone the project repo or when we delete the node modules and install the packages using npm install again.

jkester1986 · Answer 23 · Tue Apr 25 2023 21:16:51 GMT+0800 (China Standard Time)

That's what patch-package is for

…

On Tue, Apr 25, 2023, 2:14 AM KiranSayone ***@***.***> wrote: none of the above works for me because I don't even have react-native-camera module in my app it was from react-native-snap-carousel module, so I finally fixed it. see the link for the solution https://stackoverflow.com/a/75463206/12861001 yep, patch-package (which is in the stackoverflow solution) has been mentioned, I think people are overlooking it though. patch-package is probably the best solution, short of forking whichever repo is causing the problem in order to fix it But don't we need to apply the patch each time we clone the project repo or when we delete the node modules and install the packages using npm install again. — Reply to this email directly, view it on GitHub <#3423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMNB7D3WQU7PUETHLVBZATXC5TU5ANCNFSM53SA4P7A> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>