Closed aurisnoctis closed 4 years ago
Could you click the error away and try to reenable the API by manually switching it on / off. We want to make sure that the API is able to connect properly to CWA
@jakobmoellersap
We want to make sure that the API is able to connect properly to CWA
Thank you, much appreciated. I will write in English but my OS is in German so translations might not match English version exactly.
undetermined risk
java.net.SocketTimeoutException: timeout
[1]Okay
reverts view to main app screen, with green low risk
plate and that latest update was today 11:34
, which is indeed when I opened the app, but still showing 13 out of 14 days active, so no increment since the day before yesterday :arrow_right: last successful increment was the day before the day that the Google API(20)
error appeared (yesterday)try to reenable the API by manually switching it on / off.
Here, I wasn't sure if you meant deactivating and activating the tracing in CWA or if you meant the Android Google setting for the Google Exposure Notification framework so I tried both, eventually ending up in the same CWA settings, see below:
activate COVID-19 EN?
:arrow_right: I click Activate
:arrow_right: risk assessment
is active, slider stays on11:34
, still 13 of 14 days active
COVID-19
menu item :arrow_right: looks like in its usual active state [2]deactivate notifications about possible ...
(Benachrichtigungen zu möglicher Begegnung mit Infizierten deaktivieren
)
Öffnen
to the right of Corona-Warn
risk assessment stopped: Activate risk assessment to calculate your risk status for today
(instead of the usual grey or green plates)switch on risk assessment
:arrow_right: app switches to the setting for activating risk assessmentrisk assessment
:arrow_right: pop-up activate COVID-19 EN?
:arrow_right: I click Activate
:arrow_right: risk assessment
is active, slider stays on (as already done above in (B1), doing everything inside CWA)risk assessment
settings view :arrow_right: no change: update time is still 11:34
, still 13 of 14 days active
error page 1 | error page 2 | error page 3 |
error page 4 | error page 5 | error page 6 |
Really sorry for the quality - my partner and his smartphone are not here and I don't have a camera except for my own smartphone so I only have a webcam here to take pictures of my phone screen. Had to install an app for taking pics with the webcam. Webcam always focuses on the background and I had to crop all the pics by hand - took all in all 20 Minutes just to get the pics here without Android screenshots :fearful:
Google COVID-19 EN in 'normal state', ignore notes included for other github issue |
Much better quality when I had my partner's phone to take pics of my phone screen.
Okay, so as far as I understand you have multiple error cases at once that match to different errors.
Regarding your original Issue 20: This seemed to be sporadically and does not seem to reappear, correct? Regarding your issue 10: This is confirmed and is being resolved in #737 Regarding the timeout: Did you maybe lose internet connection in the meantime? This only happens when we have issues connecting to the internet in a stable way. Regarding the issue of 13/14 days active: We have confirmed this issue and are working on it in #796
@jakobmoellersap The sequence of errors was
Google API(10)
error appears for the first time https://github.com/corona-warn-app/cwa-app-android/issues/737#issuecomment-649702108, date of last update of risk assessment (Aktualisiert
) and days active
in main windows incrementsGoogle API(10)
error appears again https://github.com/corona-warn-app/cwa-app-android/issues/737#issuecomment-650144069, date of last update of risk assessment and days active
in main windows increments as beforeGoole API(10)
error appeared after that -- but days active increased steadily every dayGoogle API(20)
appears :arrow_right: for the first time days active
is not incremented and stays at 13 of 14 days active
13 of 14 days active
I was at home with a stable internet connection. I could surf the internet with the same phone before and after. I think it is unlikely that it was a short gap in internet connection for just that half minute.
The days not incrementing started the day when the Google API(20)
error happened to me. Yes, it might be that it coincided with #796 by chance and that it's two separate issues.
I'd like to keep this open until I didn't have any errors starting the app for a couple of days and to see if others start seeing the Google API (20)
error these days.
Google API(20) error appeared again today. Brief summary:
Google API(20 error)
Google API(10)
error is displayed #737 Google API(39508)
timeout error appearsToday is the first day in CWA version 1.0.4 that the last update
(Aktualisiert:
) was not incremented.
This time I had a second phone to take pics:
Google API(20)
error as a pop-up. After the smartphone screen was off and I switched it on again, it was already overlaid with the Google API(10)
error pop-up. This is when the pictures below start.Google API(10) error over Google API(20) error | Google API(10) error details 1 | Google API(10) error details 2 |
Google API(20) error details 1 | Google API(20) error details 2 | Google API(10) error again over Google API(20) error |
after clicking Okay
to dismiss the errors, the main CWA screen is visible for some time, showing 13 of 14 days active
(see also #796) and last update Yesterday, 11:34
then the Google API(10)
error pops up again
still 13 of 14 days active
and last update Yesterday, 11:34
putting app in background
opening app again: Google API(39508)
error appears
still 13 of 14 days active
and last update Yesterday, 11:34
Additional info for https://github.com/corona-warn-app/cwa-app-android/issues/788#issuecomment-652871916 from Android debug log file - maybe that helps to sort out problems with Google GMS:
Additional info for https://github.com/corona-warn-app/cwa-app-android/issues/788#issuecomment-652871916: Internet connection was working on phone before during and after these errors occurred (WiFi at home).
Thanks for the detailed info. I will update once we investigated more closely and can give more input
Update to https://github.com/corona-warn-app/cwa-app-android/issues/788#issuecomment-652871916
Today is the first day in CWA version 1.0.4 that the last update (Aktualisiert:) was not incremented.
Today I 'only' had the Google API(10)
error [1], mentioned in the Update of https://github.com/corona-warn-app/cwa-app-android/issues/737#issuecomment-652873704, but no Google API(20)
error. Aktualisiert:
changed from day before yesterday, 11:34
to Today, 8:48
.
So it was presumably indeed the Google API(20)
error causing the Aktualisiert:
not to be updated.
[1] Have to take that back. While writing this comment another error came up that I have never seen before. Will report elsewhere.
Edit: This time I made sure not only internet is working, but also that bluetooth and location are switched on even though that shouldn't be necessary for the risk update. As with BT and location on, API(20) didn't appear today, I will keep an eye on that.
Edit 2: Today (05 Jul 2020) only the Google API(10)
error appeared when opening the app and this time it also caused Aktualisiert:
not to be updated. So that behavior is not unique to the Google API(20)
error.
I just want add that I am also encountering this error today. I haven't opened the app in 2-3 days and never changed anything after the initial setup 14 days ago.
I closed the app two times and on the third try the error message went away and the app updated again.
I observed the same error on my LG g7. "Cause 3 something went wrong" ...
Haven't encountered this error recently. It seems CWA version 1.1.1 either avoids the Google API errors or the notifications, so I close this issue.
Describe the bug
Opening the CWA for the first time today resulted in display of error message
Fehler bei Kommunikation mit Google API(20)
,Error when communicating with Google API(20)
. Every opening of the app shows this error untilGoogle API(39508)
error kicks in (too many calls to API).Today would have been the first time to have 14/14 active days. Now it stays at 13/14 days.
Sorry I cannot provide more details right now. Unfortunately I had USB debugging off and after switching it on, only the
Google API(39508)
error was captured in the log. Also, it is a massive hindrance to documentation not being able to take screenshots. I didn't have another smartphone or a computer nearby when the error happened. Users of CWA on iOS apparently can take screenshots without hindrance. Friends on iPhones share screenshots of CWA with me all the time. Frustrating.Expected behaviour
The app opens without any errors.
Steps to reproduce the issue
days active
incremented every dayGoogle API(10)
error appearing for the first time; error does not appear again that days and days active are incremented when opening the app againGoogle API(10)
error appearing and disappearing on other days after that (I don't have an exact log which days); days active are still incremented every dayGoogle API(20)
error appearing when opening CWA for the first time. Appears again every time the app is opened / put into foreground until no more calls to Google API possible (Google API(39508)
error).Technical details
Device
Additional context
This error happened for me after several days of seeing
Fehler bei Kommunikation mit Google API(10)
(Error when communicating with Google API(10)
) when starting the app, as described in #771. Today, only theGoogle API(20)
error appeared. The Google API(10) error so far seemed to "resolve itself" on my device, not reaching GoogleAPI(39508)
error (too many calls to API); days active was incremented in those cases after the error was not displayed anymore.Google API(20)
in contrast reappeared until no more calls to the API were possible. Days active was not incremented today.