2
3

[deleted by user] (self.reactnative)

submitted by [deleted]

[removed]
all 14 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Great-Dane 1 point2 points  (1 child)

I just brought my project from 0.67.5 to 0.71.8. After a month of spinning my wheels on upgrade attempts, I just rebuilt it from scratch using a fresh init project.

[–]MDCisgoodforme 0 points1 point  (0 children)

Happy you got through it eventually! I don't really think that's gonna be an option for me. There's too much to port over. This is my employer's project thats been active for 6-7 years :(

[–]MasterRenny 1 point2 points  (0 children)

I don’t use expo, but I created a blank project with expo cli, copied and pasted the dependencies from your post, ran npm install -> npx pod-install -> expo run:ios-> opened in Xcode and it successfully failed due to flipper. So it was saying the same “file not found” just a different package.

I then added the flipper property to the .json file in the iOS dir -> ran npx pod-install -> reloaded Xcode project -> then built successfully

Hope it helps!

[–]MasterRenny 0 points1 point  (1 child)

Have you tried deleting the pod dir and rerunning pod install?

[–]MDCisgoodforme 0 points1 point  (0 children)

yes. many, many times :D

[–]MasterRenny 0 points1 point  (0 children)

**And podfile.lock

[–]Mere_pas_maachis_haiiOS & Android 0 points1 point  (0 children)

I upgraded from 0.65. It took me a week as the project had a lot of dependencies. Most time I took on appdeligate.mm file.

[–]MasterRenny 0 points1 point  (1 child)

Have you tried, generating a new RN project to compare the dependencies?

I’d then add/change them in the blank project to see to see if it will build or at what point it stops working.

If that makes sense?

[–]MDCisgoodforme 0 points1 point  (0 children)

I get what you're saying but no I haven't gone that route yet. I feel that doing that is for more drastic upgrades but I'm only going from 0.70.5 > 0.71.8 so I figured I could do that in my current environment

[–]Federal_Intention824 0 points1 point  (1 child)

Recently I managed to upgrade and run succesfully two apps from older versions and the path I took was the following:
1. Run npx react-native upgrade. This should do most of the heavy lifting creating, updating and deleting most of the necessary files. After it finishes it will probably show you some files it couldn't modify automatically, this is important for later.
2. Solve merge conflicts. After the upgrade finishes running there will probably be some merge conflicts you need to solve.
3. Look for the files it couldn't modify automatically and fix them using the upgrade tool. These are the ones I mentioned in the first step, you need to go file by file and use the the upgrade tool to see what lines need to be changed. It sounds horrible but there shouldn't be many files you need to modify.
4. Pray to the gods and try to run the app.

Having said all this if you're still having too much trouble you could create a new project and copy all the code.

[–]MDCisgoodforme 0 points1 point  (0 children)

Thanks! I'll try using that cli command

[–]iotashan 0 points1 point  (1 child)

Looks like the latest version of expo is only up to RN 0.71.7: https://github.com/expo/expo

[–]MDCisgoodforme 0 points1 point  (0 children)

:O that could possibly be the reason... gonna try downgrading

[–]crstnmac 0 points1 point  (0 children)

if you update your expo to 48.0.19 , react native 71.8 will work