9002: Timeout waiting for 180000 ms

[YtvwlD]

Avoid duplicates

• Bug is not mentioned in the FAQ
• Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
• Bug is not already reported in another issue

Describe the bug

Timeout bei Prüfung und daher keine aktuelle Risiko-Ermittlung

Ich habe ein ziemlich altes und etwas langsames Handy (Fairphone 2 mit Android 7) und ich habe die App da letzte Woche installiert und sie hat die ersten paar Tage auch gut funktioniert.
Nach fast einer Woche dauert die Risiko-Überprüfung allerdings so lange, dass sie abbricht.
Wenn ich die App öffne, sehe ich den "Prüfen"-Bildschirm. Dort steht, dass der Vorgang mehrere Minuten dauern kann.

Nach ca. einer Minute bricht der Vorgang aber ab mit der folgenden Fehlermeldung:

Einen Tag später war der Fehler immer noch da (er ist vollständig reproduzierbar bei mir) und die Risikoeinschätzung ist von grün auf unbekannt gesprungen:

Expected behaviour

Dass die Überprüfung lange dauert, ist wohl leider so. Mein Gerät ist halt langsam.
Aber ich würde mir wünschen, dass sie funktioniert.

Steps to reproduce the issue

Ich weiß nicht, ob sich das einfach reproduzieren lässt. Vielleicht:

1. Die App auf einem alten Handy installieren.
2. In einen Supermarkt gehen.
3. Status sollte grün sein.
4. An zwei Tagen in Folge durch einen vollen Hauptbahnhof laufen.
5. Prüfung läuft in einen Timeout.

Technical details

• Mobile device: Fairphone 2
• Android version: Android 7.1.2
• App version: 1.3.0

Possible Fix

Den Timeout verlängerne – vielleicht auf so zehn Minuten?

Additional context

Das könnte das gleiche Problem sein wie #809, aber das war mit einer älteren Version der App.

Ich benutze Fairphone Open OS mit microG statt Fairphone OS mit den originalen Google Apps.

---

Internal Tracking ID: EXPOSUREAPP-2863
Internal Tracking ID: EXPOSUREAPP-2893

[vaubaehn]

Hi @YtvwlD , es gibt schon eine Code-Änderung, die den Timeout von 1 Minute auf 3 Minuten verlängert #1138 . Leider kommt die Änderung erst mit der App-Version 1.4.0, es wird also noch eine Weile dauern.
Halte uns hier doch bitte auf dem Laufenden, ob sich nach dem Update auf die Version 1.4.0 das Problem bei dir erledigt. Vielen Dank und Grüße

[kereng5]

Auf den Screenshots ist der Flugmodus aktiviert. Könnte es daran liegen?
Ich vermute, dass dann die Kommunikation mit dem Server nicht klappt.
Dass auch Bluetooth deaktiviert ist, sollte an dieser Stelle nicht stören.

[YtvwlD]

Nee, das hat damit nichts zu tun. Ich hab auch schon probiert, den aus zu machen. Und WLAN ist ja da.

[heinezen]

Hey @YtvwlD ,

have you had a look at #998? The error message is slightly different, but maybe the issues are related. Other have posted workarounds there that might work for your problem too.

As @vaubaehn already pointed out, the timeout problem is addressed in #1138 and should hopefully be fixed in a future update.

---

Corona-Warn-App Open Source Team

[YtvwlD]

Hey @heinezen,
yes, I've looked at this issue. But I don't think they are related. The other issue is about failing to download the data in time. I don't have a firewall or something like that and I tried it on multiple occasions and both on mobile data and on wifi. Also, it worked in the past.

[daimpi]

@YtvwlD could you share your ENF log? I'd like to see whether the keys for today have been downloaded successfully.

Do you also experience "CAUSE: 3 Something went wrong. ApiException: 39508" like the user here when you open CWA afterwards?

[YtvwlD]

@daimpi How do I get the ENF log? Is that just inside Android's normal logcat?

I can't remember this happening before but after opening the app today I got "URSACHE 3: Etwas ist schiefgelaufen. Fehler bei der Kommunikation mit der Google-Schnittstelle (8)" (after clicking on "details" the stacktrace begins with "com.google.android.gms.common.api.ApiException: 8")

(At this point it might be relevant to remind you that I'm using microG instead of Google's com.google.android.gms.)

[daimpi]

@YtvwlD

(At this point it might be relevant to remind you that I'm using microG instead of Google's com.google.android.gms.)

That's a good point. Usually the ENF log can be found under Settings -> Google -> Covid-19 Notifications -> Click on "checks performed in the last 14 days" -> burger menu in the upper right corner -> export checks.

You can upload it here by either packing the file into a .zip archive or renaming the ending from .json to .txt.

I can't remember this happening before but after opening the app today I got "URSACHE 3: Etwas ist schiefgelaufen.

Interesting, thanks for the info 🙂.
You might want to check out my and @vaubaehn's comments here and here for further details.
(@heinezen you might also wana check out those comments as they're directly related to the reason why the "9002: Timeout waiting for 60000 ms" error is happening)

[dukleinekkmaus]

After we Figure out that my phone has the same Problem, what can I do? Just wait until CWA 1.4 is available?
Shall I try to empty the RAM (daily use is 627 MB of 940 MB)? Could this help to speed up the performance?

[daimpi]

@dukleinekkmaus that's a good question. I'm not entirely sure what can be done from the user side at this point, b/c in your test you already provided basically optimal conditions for CWA but it failed nevertheless.
Maybe @vaubaehn & @kbobrowski have an idea?

One thing the CWA-Team could do to spot such problems in the future, is to add low power devices like your Blackview A5 to their Telekom testing center.

[kbobrowski]

Not sure what can be done. @YtvwlD regarding "ApiException: 8" maybe you can ask at https://github.com/microg/android_packages_apps_GmsCore, since you are using alternative ENF implementation this error may have different meaning than in the original Google implementation, maybe microG developer can say something more about it

[heinezen]

Looks like this error is different from #998 then.

@YtvwlD @dukleinekkmaus

I've mirrored your report to an internal Jira ticket (EXPOSUREAPP-2863), so the developers will take care of it now. If new information on the bug is available, it should get posted here.

Regards,
CH

---

Corona-Warn-App Open Source Team

[RalfJung]

Hi @YtvwlD , es gibt schon eine Code-Änderung, die den Timeout von 1 Minute auf 3 Minuten verlängert #1138 . Leider kommt die Änderung erst mit der App-Version 1.4.0, es wird also noch eine Weile dauern.
Halte uns hier doch bitte auf dem Laufenden, ob sich nach dem Update auf die Version 1.4.0 das Problem bei dir erledigt. Vielen Dank und Grüße

Gibt es die Möglichkeit, diesen Patch auf 1.3.1 zurückzuportieren, damit er schneller ausgerollt wird? Ich habe bei meinem (ebenfalls langsamen und alten) Telefon dasselbe Problem.

[daimpi]

Gibt es die Möglichkeit, diesen Patch auf 1.3.1 zurückzuportieren, damit er schneller ausgerollt wird? Ich habe bei meinem (ebenfalls langsamen und alten) Telefon dasselbe Problem.

Ich befürchte dafür ist es mittlerweile zu spät…
1.3.1 wurde bereits gestern released: https://github.com/corona-warn-app/cwa-app-android/releases/tag/1.3.1

[RalfJung]

Ah schade, eine Zeitmaschine wollte ich jetzt wirklich nicht verlangen. ;)

[svengabr]

There is a separate Topic on our end regarding the 9002 Timeout Issue. I will bring this up in our developer meeting today again and ask for an update. I will keep you updated.

These are the currently released versions:
1.3.1 Android
1.3.2 iOS

1.4.0 will hopefully be released within the next week. Unfortunately, I can not give exact dates for the release.

[svengabr]

The developers confirmed that the timeout will be increased with release 1.4 and they will continue working on the timeouts in the following release 1.5.

[nidico]

This is the (kind of) corresponding issue in the MicroG repository:

microg/GmsCore#1171

[nidico]

Not sure what can be done. @YtvwlD regarding "ApiException: 8" maybe you can ask at https://github.com/microg/android_packages_apps_GmsCore, since you are using alternative ENF implementation this error may have different meaning than in the original Google implementation, maybe microG developer can say something more about it

According to the MicroG developer, this error code is most likely emitted by the client library, thus it shouldn't matter which service is used. 8 means INTERNAL_ERROR.

[dukleinekkmaus]

The Update solve the Problem, but it takes more then 2 minutes to check the risk. I am afraid to run into the timeout again if there is more to compare ...

[daimpi]

@maethes does the problem reported in #998 (comment) still happen for you?

[maethes]

Hi @daimpi, yes, i am still receiving timeouts. I can provide the ENF log if necessary.
I realized that each check contains about 270.000 to 314.000 keys. Not sure if this is related to the fact that there are several people nearby using the app.
Please let me know if there is anything I can help with.
Thanks, Matthias

[dukleinekkmaus]

Also heute hat die APP selbstständig den Risikostatus aktualisiert, allerdings erst kurz vor 9:00 Uhr. Gestern und vor dem Wochenende habe ich den Risikostatus manuell aktualisiert zwischen 6:30 und 7:00 Uhr das hat auch Funktioniert. Nur am Wochenende bin ich bei dem Versuch den Risikostatus zu aktualisieren am timeout gescheitert, an beiden Tagen hatte ich nach 9:00 Uhr keine Internetverbindung (höchstens gedrosseltes mobiles Netz) mehr. An beiden Tagen bekam ich abends den Fehler 38905.
Warum ich am Wochenende den Timeout hatte, kann ich nicht verstehen.
Hier der Screenshot von heute, als sich der Risikostatus selbstständig aktualisiert hat:

Und hier noch einmal die aktuellen ENF:
all-exposure-checks2710.txt

[thomasaugsten]

v 1.5.1 is available with increased timeout

[maethes]

Hi, after updating the app to 1.5.1 I received the 39508 error message. I will check again tomorrow morning and let you know the result.
Thanks, Matthias

[vaubaehn]

Hi @maethes ,
can you do us a favor? Before you sleep tonight, plug your phone to the charger. Then, inside CWA, deactivate exposure logging. Have a good sleep ;)
Tomorrow morning, leave your phone connected to the charger. Open CWA and activate exposure logging.
The moment exposure logging is active again, CWA should begin to download data and after start exposure checking.
If there is still any problem (left), then an error message should appear (which would not be shown, if CWA would check for exposures automatically in the background during the night).
If there is any error, could you take a screenshot and post it here tomorrow? If there is no error, could you shortly report your success? Thanks in advance!

[maethes]

Hi @vaubaehn, yes, sure.
Thanks ;-), Matthias

[daimpi]

@dukleinekkmaus

Thanks for the log. The problem with timeouts seems still to be present on your phone even on days where it ultimately didn't present an error. Just looking at the checks per day since CWA 1.5:

Date	No. of checks performed
27. Okt	14
26. Okt	12
25. Okt	20
24. Okt	20
23. Okt	12
22. Okt	13
21. Okt	12
20. Okt	10

This should have been 1 check per day if everything was working correctly not 10+ ^^.

Maybe the even further increased timeout will help, could you update to CWA 1.5.1 and share your EN log with us again tomorrow?

[dukleinekkmaus]

Oh okay, that explains a lot. Yesterday I updated the APP. Today it was only one ENF and the risk check worked automaticly in the night ^^.
all-exposure-checks2810.txt

[maethes]

Good Morning! Huray, the app was able to update the logs succesfully today! ;-)

I activated exposure logging at about 6:34. The update has been completed at 6:41. I will check the next days and let you know if the problem occurs again.

Thank you so much for investigating! Please let me know if there is any additional information I can share with you.

[vaubaehn]

Hi @maethes

I activated exposure logging at about 6:34. The update has been completed at 6:41. I will check the next days and let you know if the problem occurs again.

When you write, "update has been completed at 6:41", you mean the timestamp in ENF?

I mean, that's fine at first sight, and it looks like, in general your phone will be able to start exposure checks without problems, and that's fantastic!

but...

I activated exposure logging at about 6:34. The update has been completed at 6:41

That's 7 minutes! ... and increasing infection rate in Germany/Europe means increasing amount of exposure checks, means increasing amount of time, until the exposure check result can be transmitted from ENF to CWA.

@svengabr could you discuss with the devs, if there can be a problem, if one day the exposure check takes more than 10 minutes? If the Android system sets CWA to idle after 10 minutes, will CWA still be able to receive the ACTION_EXPOSURE_STATE_UPDATED and ACTION_EXPOSURE_NOT_FOUND intents, and be able to send a notification in case of increased risk? If not, we may run into trouble in some weeks for the older devices, if CWA is not opened regularly once per day...

Anyway, thanks for your report @maethes !

[maethes]

Hi @vaubaehn,
with "completed by 6:41" I meant the time when CWA was switching from "Updating..." to "Low risk". Anyway the timestamp is also 6:41.
Attached please find the screenshot of the google settings:

corresponding entry in all-exposure-checks.json:
{"timestamp":"28. Oktober 2020, 06:41","keyCount":268412,"matchesCount":0,"appName":"Corona-Warn","hash":"mToAiAZR7/fWbZmTufwXarfS+Mooh2+ssaY1Qs1hNtc="}

[daimpi]

@dukleinekkmaus thanks for the feedback. Looks like it's working fine now with the extended 8min timeout. Maybe you could keep checking your log from time to time and if multiple entries reappear for no apparent reason report back to us? 🙂

[thomasaugsten]

@maethes can you give us some details about your device?

[daimpi]

@thomasaugsten see his original post here:

Device: Huawei Honor 6
Android 6
Corona-Warn Version 1.5.0

[maethes]

Hi @thomasaugsten,

Sure:
Device: Huawei Honor 6
Android 6.0 / EMUI 4.0
Corona-Warn Version 1.5.1 (since yesterday)

Prior to the timeout issue, I received mainly the 39508 error message. I changed following settings which finally made the status update of CWA possible.

• Activated mobile data, WLAN and background update for CWA app
• allowed background activity for the app
• protected the app in power saving settings
• activated prioritized background activity
• changed power savings of my phone to full power
• freed internal disk space
• disabled Huawei Mobile Services in "apps having access to usage data" ("Apps mit Nutzungsdatenzugriff")
• uninstalled system apps using following commands:
  adb shell pm uninstall -k --user 0 com.huawei.powergenie
  adb shell pm uninstall -k --user 0 com.huawei.android.hwaps

Let me know if you need further details.
Thanks, Matthias

[dukleinekkmaus]

@daimpi yes i will check the enf log every day. If there is something odd I will report it Here. Today the difference between the timestamps of the APP and the enf was 4 Minutes....

[svengabr]

Happy to see that the timeout increase improved the overall situation, we will still continue to monitor this issue.

[dsarkar]

Dear community, do we have any new reports on the 9002 timeout issue?

Best wishes,
DS

Corona-Warn-App Open Source Team

[maethes]

Hi,

since update 5.0.1 the app is working fine on my device. In most cases the update is being executed overnight without a timeout, which I can see because there is only one entry in ENF log.

On some days I can see 2 entries in ENF log (for example at 01:34 AM and 01:50 AM). I think this should be fine because CWA shows a current timestamp and tells me everything is good.

I have exactly one day (November 14) showing 19 checks in ENF log from 01:42 AM to 08:50 AM. I think the last checks have been executed after starting the app showing the old update-date. After waiting a while I recognized it was able to update because it showed a current timestamp in CWA. The next days were working fine again.

In conclusion, I think there are still timeouts, however after automatically retrying the update works fine.

Thanks for your investigation,

Matthias

[dsarkar]

Hi @maethes,

Thank you for your feedback and good news. We still keep monitoring this issue though.

Best wishes,
DS

---

Corona-Warn-App Open Source Team

[dsarkar]

Dear community,

This issue will be closed now. Please re-open if any new problems related to this issue should occur. Thanks for contributing!

Best wishes,
DS

---

Corona-Warn-App Open Source Team