-
Notifications
You must be signed in to change notification settings - Fork 495
Reset App delays risk evaluation for one day "Unknown Risk" #1510
Comments
I can confirm the aforementioned behavior for:
|
One option to fix this would be to drop the display of "Number of Active Days" completely and immediately show a the screen with the results (feel free to upvote the linked issue). Regarding
I'm not sure whether CWA can actually do this at least in the currently used v1 legacy ENF mode. Afaik keys don't get exposed to CWA and are handled fully within ENF. Just to also mention the workaround for this problem here:
|
I didn't want to specify what methods to be used, since I'm not really confident in understanding the API exactly. Hopefully it just means ignoring the one day delay and just immediately showing the results of the exposure check. Thank you very much for listing the workaround! In fact what is even more important, even if a user has already carried out a Reset App from inside the app, they can do it one more time, but the next time setting the clock back first, before doing a repeat reset and they will get the full risk card (without Unknown Risk) displayed! |
Thank you for the report @MikeMcC399 and @daimpi for the workaround. I have mirrored the issue to Jira now (ticket ID: EXPOSUREAPP-3547). The devs will pick it up and look for a solution. We will notify you here, if we get any feedback on the bug. Regards, Corona-Warn-App Open Source Team |
This issue is no longer reproducible with CWA Android 1.9.1. After resetting the app and completing the onboarding sequence, the app displays in sequence:
It no longer displays "Unknown Risk" after resetting the app. The final state is green Low Risk. 🚀 |
@MikeMcC399 Thanks for feedback. |
Avoid duplicates
Describe the bug
Using the Reset App function appears to delay risk evaluation for one day. In the meantime the "Unknown Risk" status is shown.
Expected behaviour
CWA should re-evaluate the risk data and display the results without delay after a Reset App has been done.
Steps to reproduce the issue
check that there are exposure check log entries and make a note of the first date / time.
confirm RESET APP, RESET
Technical details
Possible Fix
Check for usable key data in the Google ENS datastore, evaluate and display a risk if possible, without delay.
Additional context
A similar situation can occur after using another ENS compatible app from another country, then moving to Germany and activating CWA. There will be key data in the ENS store which can be immediately evaluated without waiting one day. (Thanks to @ndegendogo for pointing this out.)
Internal Tracking ID: EXPOSUREAPP-3547
The text was updated successfully, but these errors were encountered: