9002: Timeout waiting for 180000 ms

YtvwlD commented 4 years ago

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x] 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:

photo_2020-09-20_11-36-17 photo_2020-09-20_11-36-18

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:

photo_2020-09-20_11-36-19

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:

Die App auf einem alten Handy installieren.
In einen Supermarkt gehen.
Status sollte grün sein.
An zwei Tagen in Folge durch einen vollen Hauptbahnhof laufen.
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

dukleinekkmaus commented 3 years ago

Today I run into the timeout.... Edit: Here are the Screenshots and the exposure file all-exposure-checks.txt Screenshot_20201024-083756 Screenshot_20201024-083801 Today it was the first day that I open the APP later then 7 o'clock (the And I think I enable everything for the hintergrundaktualisierung but for the check I always has to open the APP and do it manually.

Edit 2: Ehen I now Start the risk check, I run Into the 38905 error.

daimpi commented 3 years ago

Maybe the title of this issue could be changed to accommodate the new timeout limit of 180s such that ppl with this error message can find it more easily?

One new report of this issue (under CWA 1.5) has recently been filed here: https://github.com/corona-warn-app/cwa-app-android/issues/998#issuecomment-715775412

heinezen commented 3 years ago

@daimpi I've changed the title to reflect the increased timeout limits.

Corona-Warn-App Open Source Team

dukleinekkmaus commented 3 years ago

I don't und erstand it. Today there was no Problem with the risk check. Tomorrow I purpose to open the APP later and check, if the risk check run into the timeout again. [Uploading all-exposure-checks2610.txt…]()

daimpi commented 3 years ago

@maethes does the problem reported in https://github.com/corona-warn-app/cwa-app-android/issues/998#issuecomment-715775412 still happen for you?

maethes commented 3 years ago

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 commented 3 years ago

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: Screenshot_20201027-092949 Und hier noch einmal die aktuellen ENF: all-exposure-checks2710.txt

thomasaugsten commented 3 years ago

v 1.5.1 is available with increased timeout

maethes commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

daimpi commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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

daimpi commented 3 years ago

@thomasaugsten see his original post here:

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

maethes commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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

dsarkar commented 3 years ago

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

Best wishes, DS

Corona-Warn-App Open Source Team

maethes commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

corona-warn-app / cwa-app-android