Migrate to Kotlin 2.0 & RN 0.79 #18
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release 1.0.3
Release 1.0.3
fix(SEC-312): pin GHA dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades the example app to React Native 0.79.3 to align with Zello Kotlin SDK 2.0, which requires compatibility with more recent native APIs. The upgrade follows the official React Native Upgrade Helper from version 0.74.5.
TODO: Migrate to Zello Android SDK 2.0.0 once it's ready (@anoooooj please let me know once ready)
🛠 Key Changes
• Migrated project to RN 0.79.3
• Migrated Zello iOS SDK 2.0.0
• Upgraded all dependencies for compatibility
• Applied required manual changes per Upgrade Helper
🐛 Issues Fixed
• Safe Area Context Errors
• No ViewManager found for class RNCSafeAreaProvider
• Invariant Violation: Tried to register two views with the same name RNCSafeAreaView
• Caused by either:
• Missing or incorrectly linked react-native-safe-area-context
• Multiple versions or duplication due to local package usage