Nt/expo #2848
Merged
Nt/expo #2848
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
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.
What does this PR?
basic expo integration
at this stage it does not directly impact anything in app but makes the app capable of supporting expo managed packages moving forward.
purpose of this PR is to start testing app for any instabilities that expo might have caused as my first attempt of integration few days back disturbed the redux persistence for some reason, had to revert all and do again every integration manually.
Initially testing suggests app is stable, but we should build and let testers use app to check stability. meanwhile will integration expo-image, the primary package for which we initially started all the up gradation process.
Screenshots/Video