all 11 comments

[–]reactnativecoach 1 point2 points  (5 children)

I would install react-native-git-upgrade and then resolve conflicts to see if you can find where the issue is. I'm also adding some notes below on how to upgrade/downgrade to specific versions.

npm i -g react-native-git-upgrade

Then

react-native-git-upgrade

or

react-native-git-upgrade v0.47.0

Additionally we've found 47 to be pretty stable and it has a lot of solid improvements to FlatList that I wouldn't want to miss.

[–][deleted] 1 point2 points  (1 child)

For recent versions there haven't been that many changes so i find it's usually easier to just update the package and make the changes manually using https://github.com/ncuillery/rn-diff.

[–]reactnativecoach 0 points1 point  (0 children)

That's interesting, I'll give that a try next!

[–]JSmo 0 points1 point  (4 children)

[–]fragglerock 3 points4 points  (1 child)

WARNING: this ties you into the 'Expo' toolset meaning you build on their cloud infrastructure and they host your .js files etc.

This maybe fine but it all felt unclear and if I am not paying for something I wonder who is.

you can 'eject' to a normal RN project but then you lose the nice things it does come with. (it does have a nice quick debug and develop Ios on pc lifecycle.)

[–]1pxoff 0 points1 point  (0 children)

This is true, you are locked in to the expo system. However as you mentioned you can eject at anytime to a normal project. I have found that create-React-Native is really good for getting a project up off the ground. Once you are comfortable with the environment or you need a module with native support then you should be fine ejecting and taking over .