This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 285
Low risk contact seems like a high risk contact #1441
Labels
bug
Something isn't working
Comments
Hey @Reggirella Duplicate of corona-warn-app/cwa-documentation#422 |
Yes it is exactly this issue. Sorry have not found it when I was searching. |
Duplicate of corona-warn-app/cwa-documentation#422 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue: If your app is warning you about a high risk contact it shows how many days it dates back. This works fine. The problem is: If you have a low risk contact during the time that your app is red it changes the number of days and the communication makes it seem like you had another high risk contact.
Example: your app is red and tells you the last high risk contact is 6 days ago. You go to the get tested where you probably have a good chance to have a low risk contact with a corona positive person. Let's assume that you actually do have a low risk contact. As soon as this person gets the test result another risk contact shows in the app and the number of days reduces by 6 days. In the communication it makes you believe that you had another high-risk contact. Which leaves you confused and afraid that you have to get tested once again. If you wait and Don't do anything about it your CWA is getting green again 14 days after the real high risk contact. (How you find out that the second contact actually was not high risk)
Expected behavior: if you have a low risk contact during the time you're app is red it should not be given the impression that it was a high risk contact.
Solution: also in the state of a red CWA there need to be distinction of low and high risk contacts.
Thank you for looking in to this!
Cheers Reggirella
Avoid duplicates
Describe the bug
Expected behaviour
Steps to reproduce the issue
Technical details
Possible Fix
Additional context
The text was updated successfully, but these errors were encountered: