-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Securely Store Location Data + Other improvements #788
Merged
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
Securely store locations in encrypted Realm db
…ation-stroage # Conflicts: # app/views/LocationTracking.js
tstirrat
previously approved these changes
May 9, 2020
testPathIgnorePatterns: [ | ||
'e2e', | ||
'node_modules', | ||
'node_modules/(?!(@react-native-community|react-native)/)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oooh this might be the fix we need for testing-library/react-native
tstirrat
approved these changes
May 9, 2020
tstirrat
changed the title
Feature/secure location stroage 2
Securely Store Location Data + Other improvements
May 9, 2020
aputinski
pushed a commit
to safe-paths-contrib/covid-safe-paths
that referenced
this pull request
May 11, 2020
* official/develop: Fix EULA modal close icon color (Path-Check#792) feat(i18n) Language updates, May 10 (Path-Check#790) feat(GPS) Store Location Data in an encrypted Realm DB (Path-Check#788) Enable location status checks in testing build (Path-Check#787) fix(Onboarding) Fix EULA links to open in device browser (Path-Check#783) chore(Build) Fix debug build error with apache commons-io lib (Path-Check#775, SAF-210) chore(Testing) snapshot tests for LocationTracking, main/* (Path-Check#785) Only render mayo clinic link when language is english (Path-Check#782) fix(UX) Fix pulse alignment on Android devices with “notch” (Path-Check#771) fix(Location) Improve location "tracking" status checks (Path-Check#749) Fix text crop in About screen (Path-Check#774) [iOS] add missing languages (Path-Check#773)
monaabd27
pushed a commit
to monaabd27/covid-safe-paths
that referenced
this pull request
May 18, 2020
Co-authored-by: Tyler Roach <[email protected]>
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.
Details are copy 🍝 from #747
Securely store locations in encrypted Realm db
This PR securely stores all captured Geolocation coordinates in an encrypted Realm database.
Secures Locations imported via Google
Migrates old locations to new secure storage -> deletes old on success
Still allows for json export
Fixes bug where locations stopped being captured after device restart
Linked issues:
#527
Fixes safe-paths-contrib#29
How to test
For debug builds, you can download the Realm database inside the apps storage. You can open the database using Realm Studio: https://realm.io/products/realm-studio/. Because the database is encrypted, you will need to log a hex-encoded encryption key.
Closes #747