-
Notifications
You must be signed in to change notification settings - Fork 284
Exposure check failed when opening the CWA Version 1.6.0 / 1.6.1 (ExposureDetectionIsAlreadyRunning) #1497
Comments
@tibor Is this issue new in 1.6.0? |
@Ein-Tim haven’t seen this behavior in any of the previous app versions, so at least for me it’s new. |
@tibor Did you restart the app? |
Dear @tibor, dear community, Thanks for posting this issue. After an update to app version 1.6.0, you might get the error "Exposure Check Failed", even though there was a successful check in the past 24 hours. We are working on a solution for this error. In the meantime, try restarting your app. This helps in most cases. Nach einem Update auf Version 1.6.0 kann es vorkommen, dass Sie die Nachricht "Risiko-Überprüfung fehlgeschlagen" erhalten, obwohl die letzte Überprüfung noch keine 24 Stunden her ist. Wir arbeiten gerade an einer Behebung dieses Problems. Bis das Update zur Verfügung steht, können Sie das Problem in den meisten Fällen mit einem Neustart Ihrer App beheben. FAQ webpage DE: https://www.coronawarn.app/de/faq/#expcheck_160 Internal Tracking ID: EXPOSUREAPP-3683 Best wishes, Corona-Warn-App Open Source Team |
I have the same error and the same setup as @tibor but on an iPhone 11. |
Can you please try v1.6.1 |
@thomasaugsten works well so far. Thanks for the fast fix 🚀 |
Works well for me again now too. Appreciate the fast responses. |
@thomasaugsten unfortunately, I got the same error again today in the morning with 1.6.1 |
Updated date == time when I opened the app |
@tibor, each time when you open CWA version 1.6.1 it does an update, or so far only once in the morning? Can you close the CWA (swipe up to fully close) and reopen, please? Still time 8:38 or actual time? Thanks. |
@dsarkar still 8:38, so the app updated the first time I opened the app. |
@tibor thanks.
|
@tibor You can ignore the alreadyRunning error this can happen when two exposure check started at almost the same time. We will improve the message in the future. |
@thomasaugsten Thanks, I’m fine with that. Just wanted to let you know that the behavior is not (completely) fixed with 1.6.1 |
@Ein-Tim great, thanks! |
This comment has been minimized.
This comment has been minimized.
Since few days I get the same error messages on |
@FrankBuchholz This should be solved with the upcoming 1.7.0 release next week |
@tibor Can you please update manually on v1.7.1 and check again if this problem is fixed |
I can confirm that this Issue is not here anymore under 1.7.1 and the App also don't show this screen anymore 👍 |
Dear community, We would appreciate very much detailed feedback on this issue, now that CWA version 1.7 has been rolled out. Please monitor the behavior over the next few days. Thank you all very much for your contributions. Best wishes, Corona-Warn-App Open Source Team |
I did not experience this Issue anymore under 1.7.1 👍 |
@tibor, any feedback would be very much appreciated. Best wishes, Corona-Warn-App Open Source Team |
@dsarkar so far, for the last days, I haven't seen the exposure check failed message no more. Seems like it's working fine now 🙂 |
Dear @tibor, dear community, thanks for the feedback! We close this issue now. Please re-open in case of new occurrences! Best wishes, Corona-Warn-App Open Source Team |
Avoid duplicates
Describe the bug
When opening the app, I got an error message „Exposure check failed“ and „An error occured during exposure logging. Code: ExposureDetectionIsAlreadyRunning“.
Expected behaviour
It should work as normally with former versions of the app.
Steps to reproduce the issue
Technical details
Internal Tracking ID: EXPOSUREAPP-3683
The text was updated successfully, but these errors were encountered: