Cwa-documentation: Number of days since last risk-encounter may be not correct on the "increased risk" card

[kbobrowski]

Where to find the issue

Increased-risk card (on Android, not sure about the behavior on iOS, but possibly it affects both apps)

Describe the issue

When there is increased risk, "X days since last risk-encounter" is displayed. This information may be not correct, since number of days since any encounter will be displayed there, not necessarily number of days since high-risk one.

As an example, if a user had high-risk encounter 5 days ago, and then low-risk 2 days ago (can be even single ping with very weak signal), then it will result in red "increased risk" card with "2 days since last risk-encounter".

Suggested change

Use ExposureInformation (on Android) to get proper date of high-risk encounter, or switch to v1.5 API and correctly infer information from Exposure Windows

---

Internal Tracking ID: EXPOSUREAPP-2961

[GPclips-zz]

Hello @kbobrowski,

I have contacted the development team. Thanks for letting us know, we will inform you as soon as possible about a possible fix.

Thanks,
LMM

Corona-Warn-App Open Source Team

[rsplaul]

This also affects iOS. Ideas for possible UI fixes in https://github.com/corona-warn-app/cwa-app-ios/issues/1287.

[Ein-Tim]

@GPclips
Any update when this will be fixed?

[webermike]

Please show Date and Time of later on announced risk contacts, even if this leads to still having a green status.

As such contacts might occur only at shopping or eating in a restaurant, one can reconstruct with Date and Time where one habe been and if shopping or queuing anywhere is the risk reason.

This would enhance the analyse and discussion and avoiding of behavior in the future much, when it ia shown if the risk contact was at 8:00 in the bus ir at 12:00 in the McDonalds restaurant or at work at 10:00 o'clock at a certain date/day.

so it is not about "10 days ago" but about exact time and day.

Thanks for implementing that local showup fast.

[Ein-Tim]

This will be solved with the 1.8.0 release (https://github.com/corona-warn-app/cwa-app-ios/pull/1550)

[Ein-Tim]

Should be fixed with 1.9 release

[MikeMcC399]

@kbobrowski
Can this issue be closed now?

CWA 1.9 provided a major rework in this area https://www.coronawarn.app/en/blog/2020-12-16-corona-warn-app-version-1-9/ including the migration to v2 GAEN.

[dsarkar]

Dear @kbobrowski, @Ein-Tim, @MikeMcC399, @webermike, @rsplaul, and community,

Thanks for all the contribution. We will close this issue now as suggested, the issue is considered resolved. Best regards, DS

---

Corona-Warn-App Open Source Team