-
Notifications
You must be signed in to change notification settings - Fork 344
Inaccurate Low Risk exposure statement "No exposure up to now" #430
Comments
The problem on iOS is the same. |
Thanks for checking! |
Hello @MikeMcC399, I have created a ticket in Jira and assigned it to the responsible person. Thanks you, Corona-Warn-App Open Source Team |
I second the wish for an improvement and would appreciate an even more general fix, because the wording is misleading even for cases for which there were so far no risk encounters registered in the app. I have met real people who derived false confidence from the current wording. Best, Ulrike |
The problem is only in the English version of the App, in German the text says: |
This issue was also reported here: corona-warn-app/cwa-app-ios#1507 |
In CWA Android Version 1.6.1 the issue is still visible in both English and German displays. |
@ugroempi |
@Ein-Tim |
@ugroempi You're no pain, but since this is a bit off topic here I think it would be best if you open a new Issue regarding this 🙂 |
Dear @MikeMcC399, @Ein-Tim, Thanks for bringing this up again. We will check with the developers the progress of this issue. Best wishes, Corona-Warn-App Open Source Team |
This was fixed by PR corona-warn-app/cwa-app-android#1948. Now that "No exposure up to now" has been changed to "No exposures" the issue is resolved. Therefore closing. |
Current Implementation
After the CWA Android app previously showed
"Low Risk / 1 exposure with low risk"
it changed on a later day to
"Low Risk / No exposure up to now"
where the string "No exposure up to now" is stored in
risk_card_body_contact
The statement "No exposure up to now" is not true. There was an exposure during the time up to now, however this exposure has been aged out of the risk calculation.
Suggested Enhancement
Change
risk_card_body_contact
to something like:"No exposure" or
"No recent exposure" or
"No relevant exposure" or
"No current exposure" or
Expected Benefits
Increase confidence in truth of risk card statements
Internal Tracking ID: EXPOSUREAPP-2833
The text was updated successfully, but these errors were encountered: