[v1][Android] react-native v.0.57 compatibility / remove deprecated UIImplementationProvider #3836
Conversation
This file contains 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
Update Jenkins build status badge
guyca
approved these changes
Aug 30, 2018
reimertz
pushed a commit
to mavencook/react-native-navigation
that referenced
this pull request
Sep 14, 2018
|
@guyca Can we revert this merge now that we can provide the |
|
Hey 👋 |
nathanielram
pushed a commit
to Osedea/react-native-navigation
that referenced
this pull request
Feb 11, 2019
|
Is there any way I could use the last version of react-native with the v1 react-native-navigation? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
com.facebook.react.uimanager.UIImplementationProviderhas been removed as of [email protected] (commit), breaking react-native-navigation v1 on android.Hence removing the usage of UIImplementationProvider in react-native-navigation.
I know, all your efforts are on v2 already, but it would be great not to see v1 compatibility with react-native break too soon. :)