Migration React Native from 0.65 to 0.68 Troubleshooting Guide
1 min readOct 5, 2023
Last month, I upgraded the Kickgoing project to RN 0.68. I will show you how I resolved the issues I encountered during the upgrade.
The upgrade was easier than upgrading from 0.63 to 0.65.
0.65 To 0.66
Could not get unknown property ‘rnMinorVersion’ for project ‘:react-native-reanimated’
yarn add react-native-vision-camera@2.15.4
yarn add react-native-reanimated@2.9.1
0.66 To 0.67
Configuration ‘provided’ is obsolete and has been replaced with ‘compileOnly’
yarn add react-native-send-intent@1.3.0
Using insecure protocols with repositories, without explicit opt-in, is unsupported
android/build.gradle
maven {
url '...'
allowInsecureProtocol true
}
0.67 To 0.68
No signature of method: build_xxx.android() is applicable for argument types
I missed some differences of android/app/build.gradle. like this
include (*reactNativeArchitectures())
Invariant Violation: “KickgoingApp” has not been registered.
make same app name between
index.js
AppRegistry.registerComponent('KickGoingApp', () => gestureHandlerRootHOC(HeadlessCheck))
and ios/KickGoingApp/AppDelegate.mm
UIView *rootView = RCTAppSetupDefaultRootView(bridge, @"KickGoingApp", nil);