10

I have this warning when starting a new expo native base js project native base 3.2.0 expo 4.12.0 every package is good no problem when running the project has this error:-

at node_modules/react/cjs/react.development.js:315:4 in printWarning
at node_modules/react/cjs/react.development.js:287:16 in error
at node_modules/react/cjs/react.development.js:1424:13 in forwardRef
at node_modules/native-base/src/components/composites/Skeleton/SkeletonCircle.tsx:12:20 in <global>
at node_modules/native-base/src/components/composites/Skeleton/index.tsx:3:0 in <global>
at node_modules/native-base/src/components/composites/index.ts:37:0 in <global>
at node_modules/native-base/src/index.tsx:7:0 in <global>
at App.js:2:0 in <global>
at node_modules/expo/AppEntry.js:3:0 in <global>
at http://packager.gi-qyq.anonymous.my-furniture.exp.direct/node_modules/expo/AppEntry.bundle?platform=android&dev=true&hot=false&minify=false:202324:3 in global code````
Ahmed__Anter
  • 101
  • 1
  • 1
  • 5

2 Answers2

12

Update native-base to 3.2.1.

"dependencies": {
     "native-base": "^3.2.1"  
},
karel
  • 5,489
  • 46
  • 45
  • 50
Greñas Carreño
  • 121
  • 2
  • 1
    As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Sep 27 '21 at 23:12
  • Any reason this may fix it? I'm still getting the issues on 3.2.0 – MercPls Sep 29 '21 at 00:56
  • 2
    The right version is `3.2.1-rc.1` and I confirm this does make the stack trace go away. – jpmelanson Sep 30 '21 at 18:39
  • I can confirm it works, but I am interested in what was changed that fixes the ref forwarding (what element was it about) ? – MRadev Oct 14 '21 at 12:08
  • In the meantime native-base 3.2.1 was released. I can confirm it too. Updating fixed the issue. – Mathias Arens Oct 15 '21 at 03:36
1

are you using react-navigation 6.x? if so try using hooks, like useRoute, useNavigation, instead of passing them as props.

Jason AG
  • 11
  • 2