Can’t access test results b/c CWA is stuck at “Datenabruf”

[daimpi]

Avoid duplicates

Checked. It is not entirely clear currently whether this is Android exclusive, but as it happened under Android I've opened the issue here. If it turns out to also affect iOS, feel free to move this issue to the documentation repo.

Describe the bug

This is an issue @kira99 experienced for the first time yesterday (26.08).
On August 4th she got tested at "Rastanlage Donautal-Ost an der A3 bei Passau", scanned the QR code with CWA and never received her results.
Since then she has left the test in CWA and yesterday noticed that she cannot access her test anymore, instead this area now says

Datenabruf...
⚫ Das Ergebnis wird aktualisiert

And the wheel keeps spinning indefinitely.

Expected behaviour

Ability to access (and delete) ones stored test and therefore no indefinitely spinning wheel in the area where tests can be added on the main screen.

Steps to reproduce the issue

See description.

Technical details

• Mobile device: Xiaomi Redmi Note 7
• Android version: 10
• CWA 1.2.1

Additional context

Just guessing from the indefinitely spinning wheel symptom and the timing this could be related to: #1063 and #967 (comment).

Internal Tracking ID: EXPOSUREAPP-2398

[kira99]

IPhone XR with test from the same day and facility has this error:

[thomasaugsten]

After 21 days the variable to receive the test result is deleted on the server. We will fix the appearance of this state in the app.

[nerdiges]

Exact the same behaviour as described by daimpi on my OnePlus 7 Pro on Android 10 and CWA 1.2.1.
After I sucessfully received my test result on 3rd August via CWA I could access the test resukts for a couple of days. Since I left the test in CWA I noticed that I cannot access my test anymore, instead the "datenabruf" never finishes.

[daimpi]

@kira99 @nerdiges
Now that CWA 1.3.0 is available for Android and iOS, could you update and check whether the error persists?

(For me the update to 1.3.0 unfortunately didn't fix my problem).

[thomasaugsten]

1.3 is not solving this issue we are working on it to solve also this 400 error

[daimpi]

1.3 is not solving this issue we are working on it to solve also this 400 error

Ah ok thanks for the info. I was under the impression that there would be some kind of fix in 1.3 b/c of this statement (from my issue):

Hey,
we included a fix for this behaviour in RC1 for the 1.3.0 release, this means the fix is sadly not part of the 1.2.1 release. If the issue still persists after 1.3.0 has been released via google play please let me know :)

But thanks for clarifying that 1.3 doesn't contain a fix yet 🙂.

[parttimehorse]

I appreciate the update. I hope that will land sometime, as I cannot add a new test in the meantime. My original test result was never added to the server (probably the infamous non-ticked box on the test form) but I didn't remove it. Now, being stuck on "Your result is being updated", I couldn't even remove it to add a new test if I got one right now. And judging from how many people had the issue of non-reported results to their QR codes, I think a lot of phones will be stuck in this state now.

But at least it's being worked on. :)

[zyth0s]

I experienced a similar situation. I was tested at SXF airport on 1st of September. I do not know if box 9 was filled or not. A fillable sheet I got was for the doctor, so I did not fill it. I registered the test in the app and updated periodically. A friend told me two days later that she already had her results so I immediately checked it again. The app displayed "no results yet" but by fortune I found the results in a message from screeninglabor.de that was hidden among a pile of messages. I completely missed it and when I found it I was cautious because it inspired no confidence at all. By the way, the app still says "Test result is not yet available".

I find this behaviour misleading because I trusted more app notifications. In the app I know that I am receiving the results from an official source and the update button gives the impression that you are up-to-date. At that moment I though: the result is not available yet and the mail message could be phishing or be hiding a script behind the link given.

[svengabr]

Hey @zyth0s

The problem you are mentioning is this one: corona-warn-app/cwa-documentation#400

We are currently working on this to resolve this issue. We are in close contact with the laboratories at the moment and are making progress every day. Many parties are involved in a solution to counter this issue and we will post updates on the mentioned issue as soon as the issue gets resolved.

Best regards,
SG

Corona-Warn-App Open Source Team

[zyth0s]

As mentioned above I meant to write it in another issue. Thanks for the feedback.

[mnikander]

I'm having the same issue. Several weeks ago I did a test, scanned the QR code, got a negative test result via the app a few days later, forgot to remove the test result, and now the app is stuck at "Data being retrieved…" and the wheel is spinning infinitely. This is quite a serious problem since I would not be able to add a new test result without first resetting the CWA data, which means all the apps contacts are gone, i.e. I couldn't warn anyone with the app.

A possible quick fix for this could be to automatically delete a test result from the app a certain number of days after the QR code is scanned, though there could be problems if the system time is changed for whatever reason. A button to "delete all my test results", as a softer alternative to deleting all the app data could also be a quick work-around for the problem.

Is this issue likely to be fixed within the next week or two?

[abro1i]

Hello @Manik7,

thanks for your feedback.

As mentioned by @svengabr this issue is known and we are working on it.
Sadly, I cannot tell you when exactly this will be fixed.

As soon as I get more information regarding this issue I will let you know.

Best regards,
ABB

Corona-Warn-App Open Source Team

[mhhagen]

Same issue here. Got tested at Stuttgart Train Station at Sept 7th, and could access my test results after two days. Now the result should have been deleded on the server and my app is spinning at "Datenabruf" indefinitely. No error message.

Device Xiaomi A2 lite, Android 10

[daimpi]

@mhhagen
One thing which you could try is resetting the app data in CWA, that should not delete any of the collected keys as they are saved in the Google Exposure Notification Framework (ENF) and are only deleted once you uninstall the last ENF app: https://www.coronawarn.app/en/faq/#delete_random_ids

In the case that you reset the data in CWA your day counter will start from 0 again, but that's just a cosmetic issue which doesn't have an effect on actual functional aspects and can also be circumvented by following the steps described here if this is important for you.

Edit (Oct 30): Crossed out the last part of the sentence because of this.

[svengabr]

Short update:

The developers worked on the issue but are currently blocked due to UI/UX not final yet. We are waiting for feedback here.

Developer response:

This bug is related to a family of errors that all stem in some kind of failure during fetch of a users test result on the Homescreen. Since there is currently no design or specification on how to handle these issues except for "keep showing the loading card" we proposed introduction of a new ui state for the test result card on main screen wich displays the issue state and allows the user refetch/remove the test. This proposal is currently being investigated by the design team and is blocking implementation work.

[daimpi]

Thanks for the update @svengabr. I hope the design team can soon come up with an proposal, even if it's just a temporary one… just showing the option to delete/refetch would help a lot b/c this is the kind of error where users will probably not be very understanding why this is not already fixed and why they have to go to such lengths just to get their app working properly again, even though a solution seems so straightforward…

[lkuchenb]

Isn't this quite a serious issue, given that a lot of people are currently using the app to retrieve their test results and a potentially large fraction of them will not delete the test result manually in time?

If I understand correctly this will entirely block these users from sharing a future positive test result - they would have to delete the CWA app data to be able to enter their test result, which in turn would lead to the loss of the links to their recent contacts. Or am I not understanding something correctly here? I'm just surprised that this issue remains open for so long.

[daimpi]

If I understand correctly this will entirely block these users from sharing a future positive test result - they would have to delete the CWA app data to be able to enter their test result, which in turn would lead to the loss of the links to their recent contacts. Or am I not understanding something correctly here? I'm just surprised that this issue remains open for so long.

Fortunately the "resetting" can be done without loosing any keys saved on the device as I mentioned above as long as you don't re-install the app.

[lkuchenb]

I see, thanks for clarifying. I was fooled by the day counter effect then. I guess a regular Android user unaware of app data resetting may be inclined to reinstall the app when it doesn't work though.

[parttimehorse]

Indeed. When I had to do it, it triggered a few hours of constant error messages whenever I opened the app ("Ursache 3") so that was kind of unsettling even though I knew why it happened and that it was temporary. So I too am looking forward to this fix and hope it gets there asap. I appreciate the update very much as to why it's taking a little longer.

[MarBor8]

Are there any updates on the situation? This is so frustrating. We are almost at the three month mark since this issue was reported here.....

[heinezen]

@MarBor8 PR #1586 addressing this is merged, so the fix should be available in the next release (CWA 1.7).

---

Corona-Warn-App Open Source Team

[ThomasPiskol]

Any Forecast when version 1.7 will be available? The last time it took 16 days from merging (26th October) until the new version was available in the play store (11th November).

[MarBor8]

@MarBor8 PR #1586 addressing this is merged, so the fix should be available in the next release (CWA 1.7).

Corona-Warn-App Open Source Team

Ok. Fingers crossed then. Because that was also the info for 1.6.

[dsarkar]

Hi @ThomasPiskol, @MarBor8, once we have confirmed dates, we will let you know here when the next release is going to be available.

Best wishes,
DS

---

Corona-Warn-App Open Source Team

[dsarkar]

Dear community,

Thanks for contributing here. Regarding the update to CWA 1.7.1 (for both iOS and Android): Please note that it is a staged rollout. Over the next two days, 100% of the users should have received the update.

We would appreciate very much your feedback regarding this issue over the next few days!

Best wishes,
DS

---

Corona-Warn-App Open Source Team

[ThomasPiskol]

I just got the new version 1.7.1 and I can confirm that the issue is fixed.

[fra-nz]

I also had a stuck test result. With 1.7.1 I now was able to remove the test. Looks good.

[schorschl]

I can confirm as well that the issue is resolved. I could finally delete the test result without being stuck at "Datenabruf". Instead the test is marked outdated and can be deleted.

Google Pixel 4a, Android 11

[dsarkar]

Dear community,

Thanks for all the contributions and feedback!
For the moment we keep that issue open in order to monitor the feedback.

Best wishes,
DS

---

Corona-Warn-App Open Source Team

[ThomasAH]

We would appreciate very much your feedback regarding this issue over the next few days!

Same as the other recent replies here: We were able to delete old/expired tests from our phones with 1.7.1 which were stuck before. One phone Android 7.1.2 with 32 bit, the other is a newer Android version (I think 8.x) with 64 bit.
Thank you!

[mhhagen]

Issue seems fixed. I could delete the old test.
Thank to the devs! Good job!

[dsarkar]

Dear @mhhagen, @ThomasAH, @schorschl, @fra-nz, @ThomasPiskol, community,

Many thanks for the feedback and all your contributions. We will close this issue now! Best wishes,
DS

---

Corona-Warn-App Open Source Team