Description

This PR creates a new notification and filtering feature for Healthcare Authorities in a user's location.

Issue

#425

How to test

Unit

npx jest HCAService.spec.js

Integration

• Visit the Choose health authority screen and press the Add Trusted Source button. Press the GPS filter switch and confirm that all health authorities are removed (the current live yaml file does not include a bounds field so by default there will be no authorities in your area)

Comments / Concerns

• I added a line to the BackgroundTaskService that will send a push notification to the user every 12 hours if there is an authority in their region that they haven't subscribed to.
  • Is 12 hours too frequent? I believe we can only have a single BackgroundTaskService (ours runs every 12 hours to check for intersections), so I'm not sure how else we could check at a pre-defined interval.
  • What if a user intentionally decides not to subscribe to a particular authority? Currently, they will continue to get a notification every 12 hours to subscribe.
• It would be nice if upon receiving a push notification, we could direct users to the Choose health authority screen. However, the only way to do that on iOS as far as I can tell is through the deprecated alertAction param. I believe that we can do this for Android through the action field for local notifications, but I'm not sure if we want that inconsistency between platforms.
• I'm not sure of a good way to test the push notification piece of this PR without changing some code around to force the notification and then revert the changes. I was thinking of doing a similar approach that we use for intersections but would like some feedback before implementing. @tstirrat - feedback here would be appreciated.
• Currently, the authorities list does not contain bounds info. @penrods - how should we go about updating that file on raw.githack, and in general, is there a way that we're going to force authorities to include bounds? And in the case where a user uploads an authority with the Add authority via URL option, will we just allow them to not include bounds?

Translation Notes

There are several new strings for translation.

Rebase of https://github.com/tripleblindmarket/covid-safe-paths/pull/282.

This PR addresses 2 issues:

• Improve Google Location Data import experience
• Import Locations from Google on iOS: Browser opens the Zip file in the Webview.

Other things done besides fixes above:

• Add logic to import last 2 months from Google takeout as safe paths is concerned only about locations for recent couple of weeks
• Add checks if files exist before reading
• Add info messages on import complete:

Success:

Already imported:

No recent locations:

Select file screen if downloaded locally:

Closes #77 Closes #69 Closes #315

We need to be able to support very high levels of points of concern, with a "full" set of location data (over the last 14 days).

As a rough estimate, this is users location data should be on order of 28 x 24 x 12 = 8064 As a rough estimate, based on NY, the current 14 day growth is ~64000, so points of concern could be on order 64000 x 14 x 24 x 12 x 0.5 = 53,760,000

The point of this test would be to know processing time and memory usage. Also, determine limits so the app can protect itself in case of extreme data loads.

I was not able to get this function to work, despite following all on-screen instructions. o Within the embedded Google Account pane, I was able to export & download my location history. o After that, instructions were to “open this screen again. The data will import automatically”. I tried to do this many times, but did not succeed. I don’t know whether that’s a functional issue or a UX issue.

Notes in https://github.com/tripleblindmarket/covid-safe-paths/issues/69 suggest that other users have managed to get this to work (though they lamented the user experience).

So I don't know what the issue was with my phone. Please let me know what diags would be useful and I'll aim to provide.

Note that this is one of the key basic functions of the App, so if it's not working on some devices, that seems like a serious concern.

Currently the user must manually subscribe to a Healthcare Authority. This will grow to a point where it is a difficult UI to work with. I propose the following:

1. Extend the Healthcare Authority yaml which lives on the safe-places repo to include a GPS bounding box.
2. If the user has no existing Healthcare Authority, the app checks that file once every 24 hours. If the user's current GPS coordinate is within any bounding box, they should be given a popup notification that a Healthcare Authority exists in their are, "Would you like to subscribe?" ** This should only happen until they have the first authority to avoid overloading the server with millions of requests **
3. A similar process can be used when the user manually enters the Subscription page. I'm not worried about server overload on a manual process. This can limit the list to authorities which contain any of the points in their full 28-day GPS history, then have a checkbox that will show All Authorities.

The list which they are checked against should be a "production" URL from http://raw.githack.com/. This will provide decent buffering of the Github server infrastructure, but it is VERY IMPORTANT we purge the cache anytime a new Healthcare Authority is added to the YAML.

This is the production (cached for a year) CDN URL: https://rawcdn.githack.com/tripleblindmarket/safe-places/940edc081b8a4771deca806ed570eda907b5a261/healthcare-authorities.yaml

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 https://github.com/safe-paths-contrib/covid-safe-paths/issues/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.

Description

react-native-background-geolocation bug fix that described in #523

How to test

Restart your device. You should see the SafePaths notification in drawer within a minute or two, indicating that react-native-background-geolocation is pulling location again.

Fixed the issue using patch-package. The patch show many lines changed due to jettifier, but the patch itself was a single line (L248)

Description:

Fixes crash on launch of bt build variant because .env.bt is not read correctly

Linked issues:

Fixes #1221 Fixes luggit/react-native-config#467

Screenshots:

How to test:

yarn run-android-bt -- no crash in App.js

Description

resolves issue 564. the message was confusing so was changed (in the english resourse only ) to the suggested stopped when location services are disabled or stopped at user request

How to test

1 go to settings, click on stop logging text or icon, see message appears. it should now read Location Tracking was disabled Stopped at user request. 2 go to settings turn off location services from OS. click on stop logging text or icon see message appears. it should now read Location Tracking was disabled Stopped. (any ideas for unit tests)

Still todo other languages (please advise!) (In another locale the english text will appear until the translation is present I think)

Fixes #564

The Import functionality is great, but still tricky to use. It might take a few iterations to get it to what we want, but here are some thoughts:

Break the Import into three stages, kinda like an old-school Wizard.

1. "Intro" page. Explain what this does and give instructions to log in and start the process w/Google. Q: Can we explore the DOM on the webview? It would be cool to watch for an indicator that the request for a takeout has happened, then move to the "Waiting" step described below.
2. "Waiting on Google takeout" page If the user returns to Import page, show a message that we are still waiting on the takeout file. Include a "Start over" button to go back to Step 1 in case something fails.
3. "Import Complete" After an import completes, the results of the import should be remembered and displayed. E.g. "28 day of data imported from Mar 1 - Mar 28". Also have an "Import again" button that goes back to step 1.

During Step 2 the user should be be able to leave the app or go back to the main page. We should have a background task look for the takeout file when one is pending, so you don't have to go back to Import. The app should show a notification when the takeout file is found and process completes.

Discussion is welcome. I expect the implementer will find challenges and opportunities to improve this sequence. For instance, there might be a step 2.5 that helps with the download of the Takeout file.

Version

• Type of phone: Android / iPhone
• OS Version:
• Model: iPhone 11 (simulator)

Steps to reproduce

Go to Settings, turn off location

1. You get notification
2. now you pull the notification drawer and swipe on notification to get rid of it
3. Drawer closes and the app comes in foreground and another notification gets triggered
4. Go to 2.

Expected Behavior

Any event should generate notification only once in general, the way we trigger notification in our app is asynchronously checking states at every screen mount/refresh, we need to shift the logic perhaps

placeVisit" : { "location" : { "latitudeE7" : 324914959, "longitudeE7" : -921784525, "placeId" : "ChIJbbNi6KM3LoYRvSDTmrO3fYY", "address" : "223 W Heights Dr\nWest Monroe, LA 71292\nUSA", "name" : "223 W Heights Dr", "sourceInfo" : { "deviceTag" : -1864277346 }, "locationConfidence" : 36.61622 }, "duration" : { "startTimestampMs" : "1607129593011", "endTimestampMs" : "1607130430990" },

Why this issue The notification problem is a bit confusing, so I wanted to create a document to explain my findings. Also, there will be PRs in 2 repositories, so I wanted a place to describe the whole solution.

Existing problem

Issue reported here on Jira. There are 4 different notification categories (called Channels in code) on Android, and they're a bit confusing. In addition to being confusing, having a Sync Service notification might cause concerns that the app is syncing collected data.

Cause

• Every notification on android requires having a channel.
• The existing 4 channels are created in 2 different places
  • Setting up the react-native-push-notification to be used for pushing local notifications. This is a valid category of notifications, however, the configuration in the AndroidManifest here used the code name "covidsafepaths_kit_notification_channel" for the category instead of a human readable name.
  • The Path-Check/background-geolocation-android submodule setting up the other 3 categories (a) Service channel - required to do background notification. This is valid, but should be renamed. (b) Sync channel - this should be removed as we're not doing any syncing work. (c) Android Permission Channel - as far as I can tell, this is not being used, as we're creating our own notifications for the permission here. However, I don't want to remove it without additional knowledge. We should still rename this to avoid the duplication and make it clear.

Proposed solution

1. Remove the sync service category, and rename the other categories as follows

Note: the unreadable channel name was configured in AndroidManifest.xml instead of code, so the change will not be reflected after the app update, but only after a fresh install or reinstall. I have tried to find solutions to this but haven't found any. Perhaps someone with better Android experience can help.

2. Once we've determined that the Android Permission category is not actually used, we should remove it, leaving only 2 valid categories, Background service and General notifications.

3. Rename the background notification from

as it is not clear, and some text is cut off (no option to expand) to the newer version (copy can be changed):

I will submit the related PRs for this proposed solutions and update the issue.

Hello there! I got this error when i run yarn react-native-local-resource . I run this react-native unlink react-native-local-resource but still not working. Thank you all

$ yarn react-native run-android
error React Native CLI uses autolinking for native dependencies, but the following modules are linked manually:
  - react-native-local-resource` (to unlink run: "react-native unlink react-native-local-resource")
This is likely happening when upgrading React Native from below 0.60 to 0.60 or above. Going forward, you can unlink this dependency via "react-native unlink <dependency>" and it will be included in your app automatically. If a library isn't compatible with autolinking, disregard this message and notify the library maintainers.
Read more about autolinking: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md

Issue type

Environment

Version

• Release build version: 1.22.4

Affected Devices

| Brand | Model | OS | | ------------ |:-------------:| ----:|

Samsung Galaxy S8 emulator Samsung Galaxy S9 device

Affected Languages

Steps to reproduce

yarn run-android-bt

Expected Behavior

Normal onboarding

• When I click Stop Logging I am taken to the Import screen. Expect to go back to the Welcome greeting.

Issue type

UI

Steps to reproduce

• Navigate to permissions steps in onboarding
• Select "Enable Location"
• Screen advances immediately without waiting for the user to approve/deny location permissions

Expected Behavior

• When I click "Enable Location", the screen does not advance until I approve or deny

Upload any files to the Issue useful in helping us to investigate

In the screenshot below, note that the screen has advanced to the HA permissions before the user has selected approve/deny from location permissions

Steps to reproduce

Open the App Open Hamburger menu Tap "Latest News" to navigate to SafePath News screen Tap on Hamburger Menu against COVID SafePaths Tap on FAQ

Expected Behavior

The FAQ page should display the hamburger menu without scrolling horizontally and wrap all the content to fit the container width.