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 is an exploratory PR about migrating the BrightID app to expo. I basically patched it together to get it compiling and haven't taken any steps to fix anything. Some things are broken.
The main reasonings for moving to expo are as follows:
expo upgrade
)dev
branch with Expo GoSwitching to expo should help BrightID spend less time with react native bugginess and App store updates and more time building the app. It's a massive pain to switch, so I understand pushback, but it would be a massive boost to long run productivity and app health
Here is a checklist of definitely broken things (there may be more):
fetch-blob