-
Notifications
You must be signed in to change notification settings - Fork 345
Rapid Tests: Don't assume that the appointment of a test is accurate #630
Comments
|
Hello @jeyemwey This should have been fixed in CWA 2.3. We'll close the issue here. Corona-Warn-App Open Source Team |
Hi, thank you for the heads up and have a good week! |
@heinezen Are you sure this has been fixed? In the meantime I'd like to ask you to reopen this issue. |
@Ein-Tim btw: the issue here are actually 2 issues: negativ counter and corona-warn-app/cwa-quicktest-onboarding#24. |
@dsarkar Is there an update available here? |
The counter has been removed completely , this issue should be closed |
Hey @jeyemwey, please see #630 (comment). Would you like to close this issue now? |
Good for me! I thought the issue was resolved when the swab time was introduced about a year ago, but I will close this now anyways. Thanks for your help and time! |
Avoid duplicates
Technical details
Describe the bug
The rapid test integration assumes that the timestamp of the test is accurate (see e.g. Anbindung der Partnersysteme) and only has one timestamp. This creates problems if the test center is congested (and the actual time is later than the appointment) or the testcenter uses the appointment dates only for load balancing and does not care when you come in.
The second point can be an attack vector: If you come in earlier than your appointment, CWA will attest that you have a valid test for longer time since the relative time component calculates
now() - t_appointment
.Steps to reproduce the issue
I booked an appointment for 2021-06-05 on 2021-06-04, but already went to the test center today at 17:00. These are my results:
Expected behaviour
I would expect that the timestamp of the actual examination is used on the result screen. It is further unclear to me, why it seams to post the correct date in the welcome view, Date of adding the test to the app, maybe?
Possible Fix
Additional context
The appointment date is also used in the URL/QR Code as the
timestamp
property.corona-warn-app/cwa-quick-test-backend#82 and corona-warn-app/cwa-quick-test-backend#94 are connected, maybe?
Internal Tracking-ID: EXPOSUREAPP-7972
The text was updated successfully, but these errors were encountered: