DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 963,503 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Feargal Walsh
Feargal Walsh

Posted on

Upgrading from react-native ~0.56 to 0.57.1 and Babel v7 after just installing MacOS Mojave and Xcode 10

Sequence of commands I used to install this.

Updated to MacOS Mojave

rm-rf node_modules

npm install

react-native-git-upgrade

Got errors about babel hot reloader but ignored them.

ran react-native run-ios

Got build error to do with react-native cli

opened project in Xcode, updatedΒ build tools for shared workspace that were still on legacy to latest.

Cleaned project

Found this

https://stackoverflow.com/questions/52452472/xcode-10-error-multiple-commands-produce-react-native/52452590

which led me to this

https://stackoverflow.com/questions/13751147/remove-or-uninstall-library-previously-added-cocoapods

Which gave me errors when I ran pod install referring to BoringSSL.

Decided to change track since I hate pods and update Babel instead.

That was pretty easy, I just followed this.

https://babeljs.io/blog/2018/08/27/7.0.0#babel-upgrade

I installed it globally, if I could do it again I wouldn't have done that, no reason why, just seemed like it could cause problems down the line.

App eventually ran after a little friction, manually started packager, but then I got some version mismatch errors.

Ran npm cache verify and erase all content and settings on the simulator to get around these, but realized that I'd been getting build errors all along so I morosely trekked back to

cd ./ios

Realized BoringSSL error was being caused by this file changing name on Github.

https://github.com/grpc/grpc/blob/master/src/objective-c/BoringSSL-GRPC.podspec

Changed name of pod BoringSSL to BoringSSL-GRPC too after that gave me an error.

pod install appeared to be successful subsequently.

Killed still running packager, deleted app from simulator and ran:

react-native run-ios

Build succeeded, one brief moment of joy, instantly brought back down to reality with lovely post build succeeding error.

Bunch of cache cleans and erase all content and settings type things got things fixed though.

Android should be a piece of cake right?

Terminal logs available on request and at your peril.

Top comments (4)

Collapse
 
franzandr profile image
Franz Andrusch Romero

I have issues with babel and watchman after update Mojave os. Problem with react-native run-ios

Collapse
 
feargswalsh92 profile image
Feargal Walsh Author

You may need to upgrade babel

Collapse
 
feargswalsh92 profile image
Feargal Walsh Author

But that should happen automatically if you update rn

Collapse
 
feargswalsh92 profile image
Feargal Walsh Author

Update

Android worked first time!

🌚 Browsing with dark mode makes you a better developer.

It's a scientific fact.