Fehler bei Kommunikation mit Google API (39508)

[ascheman]

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

Opening the app I get "Fehler bei Kommunikation mit Google API (39508)"
A details page shows a stack trace.

Expected behaviour

No error message!

Steps to reproduce the issue

1. (Re-)open the app
2. See error message
3. Swear why the app forbids to take screen shots 👎
4. Search for other smart phone
5. Take photos:

Technical details

• Mobile device: One Plus Two
• Android version: 6.0

Possible Fix

Additional context

---

Internal Tracking Id: EXPOSUREAPP-1854

[tobiaslvoss]

I get the same bug
Device: Honor 6c (DIG-L21HN)
Android Version: 6.0
App Version: 1.0.4
[Update 2020-06-29 09:15 - error resolved for me, thanks]

[pyromaniac78]

I get the same bug 39508
Mobile Device: Honor 7 (PLK-L01)
Android Version: 6.0
App Version: 1.0.4

[tomjschwanke]

First question: WHY IS IT NOT POSSIBLE TO MAKE SCREEN SHOTS? THE APP DISABLES IT - IT WOULD BE VERY HELPFUL TO SEND ERROR REPORTS!?

Writing in caps (aka screaming) isn't helping. The screenshot prevention is being discussed.

[ascheman]

First question: WHY IS IT NOT POSSIBLE TO MAKE SCREEN SHOTS? THE APP DISABLES IT - IT WOULD BE VERY HELPFUL TO SEND ERROR REPORTS!?

Writing in caps (aka screaming) isn't helping. The screenshot prevention is being discussed.

You are right, sorry. Removed it (was a bit annoyed that forwarding details about the problem is such a pain).

[tomjschwanke]

You are right, sorry. Removed it (was a bit annoyed that forwarding details about the problem is such a pain).

I understand your frustration. Let's hope the screenshot prevention only gets applied to the TAN screen (although maybe people would maybe demand screenshot of risk status)

[wende60]

get the same error since today. Additional Info: "Risiko Ermittlung" is active, but still it requires to activate it. Before it was working properly since 11 days...
HTC One A9s
Android 6.0

[tekkiexxl]

get same issue
Sony Experia E5 (F3311)
Android 6.0

[KlugB]

Same issue on
LG G4
Android 6.0 (not rooted)
Tried reboot, cleaning cache of Google Play Services, refreshing all updates
App states last successful update yesterday (2020-06-27) 19:25
Worked properly for 11 days

[jakobmoellerdev]

The error is related to rate limiting as a result of Error 10 since we have a sporadical SSL breakdown that we are working on together with Google as documented in #737. We keep you posted. Please wait for a day and the issue will resolve itself. Sorry for the inconvenience, and thanks for helping us with your reports.

[ascheman]

Nope, it does not resolve itself. I am out of sync for three days now, though the error has change to Fehler bei Kommunikation mit Google API (10) meanwhile.

[jakobmoellerdev]

This means the error has in fact resolved itself however Error 10 still persists for you as mentioned.

[grmblfxhoch10]

Same here.
Worked for 8 days. Now the error 39508.
Android 6.0
Huawei P9.

[YvesKlein111]

Worked 4 days until yesterday night.
After turning on GPS+BT this morning, error 39508
Galaxy S5-neo, Android 6.0.1

Screenshot of remote control via Anydesk:

[Truthmattersww]

Problem persists on my device since 26.06, despite reinstallation of app and Google-Play-Services cache reset
Model: Samsung S5 neo, SM-G903F
Android: 6.0.1

[jakobmoellerdev]

The error will not reset if you do not explicitly wait for 24 hours until the next query. The limiting will reset at 0:00 UTC

[ascheman]

This means the error has in fact resolved itself however Error 10 still persists for you as mentioned.

Hmm, yesterday I had error 39508, today I have 10 again. It seems the error is kind of oscillating between these two states, @jakobmoellersap?

[grmblfxhoch10]

This means the error has in fact resolved itself however Error 10 still persists for you as mentioned.

Hmm, yesterday I had error 39508, today I have 10 again. It seems the error is kind of oscillating between these two states, @jakobmoellersap?

Same here, error 39508 is gone, now error "Fehler bei Kommunikation mit Google API(10)".

[jakobmoellerdev]

For all errors regarding Error Code 10, please refer to #737 where we will update accordingly.

[tkowark]

This means the error has in fact resolved itself however Error 10 still persists for you as mentioned.

Hmm, yesterday I had error 39508, today I have 10 again. It seems the error is kind of oscillating between these two states, @jakobmoellersap?

Yes, depending on when 10 happens, 39508 is triggered or not. Jakob describe that also here: #737 (comment)

[x662]

Same Error here on LG 4 and Android 6.0

[morber13]

Same error(s) on my smartphone: Samsung Galaxy A3 (2015), Android 6.0.1. Last update was 29.06. 18:27. Error changing from 10 to 39508 and back.
I installed this app the first day it was published (16.6.?).

[morber13]

According to some hints I re-installed the app. Now apparently all data has been deleted: "unbekanntes Risiko".
This is not the aim of the app - run 14 days and then restart from start...

[morber13]

For such cases issue #17 (Report Error Context...) would be very helpful!

[jakobmoellerdev]

@morber13 since you uninstalled the app, all data has been deleted. This is by design. I am not sure where you got the idea that reinstalling the Application would solve the problem mentioned here, but I would appreciate if you could give us a direction on where you have retrieved this information from.

[morber13]

@jakobmoellersap in #737 somewhere i found: Your chain of keys is not broken. These are not stored by the app and deleting the app will not remove the keys. To do that, you have to explicitly remove them via the Settings for the Covid-19 Exposure Protocol.
So I tried to re-install.

[gizmo21]

Same error, first time here.
At first API (10), then directly after that API (39508).

Android 6.0.1
Google LG Nexus 5
Google Play Dienste 20.21.17 (040308-316502805)

[tkowark]

in #737 somewhere i found: Your chain of keys is not broken. These are not stored by the app and deleting the app will not remove the keys. To do that, you have to explicitly remove them via the Settings for the Covid-19 Exposure Protocol.
So I tried to re-install.

That was me. And that statement is still correct. The RPIs in the exposure log are not deleted upon deletion of the app. All app data, such as the active days or your current risk state is of course deleted when you delete the app.

See #774 (comment) for an update.

[stevie21]

Hi @vaubaehn,
now i installed cwa version 1.2.0 (17.08.2012 at 14:35). Also in this version cwa app runs in mode "Priorisierte Hintergrundaktivität" as already before.
On weekend i had no problems with cwa (running my handy in normal energy mode)
I also run my handy now in normal energy mode. I will switch in the night to low energy mode and keep network enabled. I will set bluetooth and location to inactive mode (in the night).
On tuesday morning i will switch from low energy mode to normal mode and will start directly cwa app to see if actualization will be done online and if i will run again into error 9002 and then into 39508.
If i shall do something other: keep me informed.

[vaubaehn]

Hi @stevie21 ,
sounds like a good plan, let's wait for the results then! Good that it worked with normal energy in the week-end.

[stevie21]

Hi @vaubaehn,
I switched today from low energy mode into normal energy mode. I immediateley opened cwa app.
I got immedateley the message that actualization was done on yesterday (again at 03:33). See screen:

So i was confident. Then (without any aim, just by luck) i touched the green screen and i immedateley get the following screen:

I also made screens of the details, but do not upload now (only if you need it). After confirmation with OKAY i went to next screen "Ihr Risikostatus":

The expectation from my side is, that switching from screen "Niedriges Risiko" to screen " X Ihr Risikostatus" should be done without any error message. Also when i go back from screen " X Ihr Risikostatus" to screen "Niedriges Risiko" i get this error message inbetween.

I also have a additional proposal for next night.
When i switch my handy into low energy mode, then automatically WLAN, Bluetooth, and Standort (location) are switched off by this low energy function. But you are able to switch them manually on active again. Next night i keep all 3 of them as inactive. Then on next day in the morning i will go back into normal mode and open cwa immediateley. Then i think that actualization will be done again in online mode and let's see what happens. If you have other proposal: just let me know.

[vaubaehn]

Hi @stevie21 ,
thanks for reporting back!
I think, your today's error message is related to this: #1021 (comment) - I had a similar problem this morning.
If it's ok for you, could you keep WLAN on again this night? It's just to be sure, that not WLAN is causing your 9002: Timed Out while waiting... (it can also cause a slightly different error, when CWA is opened while WLAN is still getting initialized).
Thanks for all your efforts! I think, tomorrow we're done.

[stevie21]

Hi @vaubaehn,
yes i will keep WLAN on and i will go into low energy mode this night. I will again report the behaviour back tomorrow.

[stevie21]

Hi @vaubaehn,
some minutes ago (12:40) i switched my handy from low energy mode to normal energy mode. WLAN was active all the time, since my last message (see above). Bluetooth and location (Standort) was off. But i think that's not so important. I got immediateley the following screen:

When i switched the screen to "X Ihr Risikostatus" i got again the screen: "Ursache: 3 Etwas ist schiefgelaufen" (see above picture from yesterday). Also again when i switched back to main screen, i got again the switch to the screen with message "Ursache: 3 ... ", before i came back to main screen.

If i shall run my handy in other mode just let me know. If i hear nothing from you this day i will run my handy in low energy mode until 23:00. And i will switch to normal mode over the night. If you have other proposal: just let me know.

[vaubaehn]

Hi @stevie21 ,
hmmm... that's not so good news, seemingly there was an automatic background update for diagnosis keys during the night, and low energy mode might have prevented to sucessfully check for exposures in the background. In that thecase, you run into Ursache 3: API 39508", because after opening CWA manually, CWA is not allowed anymore to call the ENF api...
Another reason could be, that you received an ENF update, and possibly due to initialization there were 2 unsuccessfull calls to the API in the background.

Could you provide your ENF version, like described here: https://www.coronawarn.app/de/faq/?search=enf#ENF_version
And could you maybe have a look into the Covid-19-Benachrichtigungen (phone's settings > Google > Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen) how was the timeline for the checks. Was there a check last night with excactly 20 queries? Or a check with 14 queries? Or none for last night?

In any case, I'd recommend to turn off low energy for the next night, to be sure, you get over the 39508 error, and automtic exposures checks work fine in the background.

[stevie21]

Hi @vaubaehn
My ENF Version of my handy is 16203302004. That means: Smartphone has version 1.5 (as described in your link from above)
I checked the number of queries: On 19.08 i had 20 queries at 12:42.
Then at 18.08 i had also 20 queries: 17 at 10:44 and 3 at 10:42
I will keep my handy in normal energy mode and will see if it runs well on tomorrow. I will inform you.

[stevie21]

Hi @vaubaehn
I opened my cwa app at about 10:55 on today. I immediateley hat green screen with actualization info at 02:27 :

Also when i switch in cwa app to other screen: No error message.
I also checked the number of queries: On 20.08 i had 14 queries at 02:28.
Now it runs as it shall run. I will run my handy now (like yesterday) during the day in low energy mode and will switch to normal mode at 23:00 (so like yesterday). But if you have other proposal or you want some additional testings: just let me know.

[vaubaehn]

Hi @stevie21 ,

My ENF Version of my handy is 16203302004. That means: Smartphone has version 1.5 (as described in your link from above)

Unfortunately, the FAQ pages are not uptodate yet. The 16xxxxxxxxx means, you already have version 1.6, the latest version :)

I checked the number of queries: On 19.08 i had 20 queries at 12:42.

That is a problem, that many people reported already. I also had a similar issue. My guess is, that this was occuring once for everyone of us, when the latest ENF version had its first initialization. But I don't know for sure.

Then at 18.08 i had also 20 queries: 17 at 10:44 and 3 at 10:42

That is indeed a little bit suspicious. That means, that after 3 trials to match diagnosis keys from server with your exposures, the routine in ENF stopped working. Two minutes later it tried again. If the regular 14 matches would have been successful, then it would have stopped at 10:44, counting 17 checks in all (including the 3 at 10:42). But as it is 20 checks in all, it seems that also the 2nd check had a failure, and even a 3rd checking was started in the same minute. To find out, what actually happened, it would need to dive deeper into the exposure logs, but I think it's not worth the time at this moment, as the last check from this night finished sucesssfully.

Now it runs as it shall run. I will run my handy now (like yesterday) during the day in low energy mode and will switch to normal mode at 23:00 (so like yesterday). But if you have other proposal or you want some additional testings: just let me know.

To find out, if you can reproduce '9002: Timed Out waiting for 60000ms' it would now make sense, to repeat the experimental scenario once again: during the night, switching to low energy mode, keeping wifi on. In the morning, before switching anything or opening CWA, you could check, if the automatic background update and exposure checking worked like it should by looking at the number of queries (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen), if they were actually checked.
After that you could switch energy to normal mode and immediately opening CWA, and see, what happens. Would it be ok for you? In worst case, as a side effect, you would not be informed for tomorrow, if there was a risk exposure, as you would run again into the API 39508 then... Just see, if you're comfortable with it.
Regards, V.

(By the way, I also tried to reproduce that problem with my own device, but it was not possiblem, because even in low energy mode, it's consuming much power. But that's about the design of my device, I can be happy, if I don't need to charge within 12 hours...)

[stevie21]

Hi @vaubaehn
In low energy mode i have also limited access to my handy. So in low energy mode i am not able to go to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen). I have 2 options:

1. In the night i run low energy mode with WLAN on. Then in the morning i switch to normal energy mode. Then i go to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen) and then i open my CWA app. What i did not understand:
   In case number of queries is not 20: i will open CWA app. And in case number of queries is not 20 i do not open CWA? And i will open it then at next day?

2. Other option: If i run my handy in the night with low energy mode and keep WLAN unactive, then actualization can not be done. When i switch my handy in the morning from low energy mode to normal energy mode, my WLAN will be active and then opening cwa to see if cwa wants to make actualization in online mode.

If i hear nothing from you, i will go this night by first of above 2 options.

[stevie21]

Hi @vaubaehn
For some other reason i had to run my handy today (i think since 11:00) in online mode. Then i checked at about 15:15 (no other time before) my handy and i have green screen:

Also when i checked number of queries: today i had 15 queries at 12:24.
On tomorrow i will proceed with item 1 from above (see my last message).

[stevie21]

Hi @vaubaehn,
Last night i run my handy in low energy mode with WLAN actice. Today i switched at 11:25 from low energy mode to normal energy mode. My first action was: I went to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen). As i mentioned already yesterday: To call this function is not possible for me in low energy mode, so i made it in normal energy mode as first action. Result: There was no entry for today 22.08.
Then i went back and immediateley opened my cwa app. Actualization was done on yesterday. I saw this on the first screen and then i switched to screen "X Ihr Risikostatus". There you can see the last actualization time. Yesterday at 12:24:

This time information was also visible on the first start screen. But i did not make a foto.
Then i went back from screen "X Ihr Risikostatus" to start screen. This was done immediateley without any signal to a user that something will be processed. Then i got the following screen:

So the actualization must have been done in this minute at 11:26 on today. Next action from me: I left cwa app and went again to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen). Result now: 16 items for today at 11:26

So it seems to me, that in this version 1.2.0 of cwa a online actualization (as i know it from last version 1.1.1) is not executed and that it is somehow also in the background, even if you have cwa opened or not.

[vaubaehn]

Hi @stevie21 ,

sorry for coming back late to you - I needed to work and had some family time.

In low energy mode i have also limited access to my handy. So in low energy mode i am not able to go to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen). I have 2 options:

Can you maybe describe more concretely, what are you able to do in low energy mode, and what not? If I enable battery saving on my phone, like you do, I can still use everything, but with a darker display, no visual effects etc. That information might be useful to target this issue even more. What exactly hinders you to go to Covid-19-Benachrichtigungen?

1. In the night i run low energy mode with WLAN on. Then in the morning i switch to normal energy mode. Then i go to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen) and then i open my CWA app. What i did not understand:
   In case number of queries is not 20: i will open CWA app. And in case number of queries is not 20 i do not open CWA? And i will open it then at next day?

I meant, you can open CWA either way, it would just be good to find out, if CWA does the background check if your low energy mode is enabled. And to reproduce the 9002: Timed Out while waiting... you'd first need to check for Covid-19-Benachrichtigungen, turn on normal power, and then immediately open CWA.

2. Other option: If i run my handy in the night with low energy mode and keep WLAN unactive, then actualization can not be done. When i switch my handy in the morning from low energy mode to normal energy mode, my WLAN will be active and then opening cwa to see if cwa wants to make actualization in online mode.

This, indeed, could cause also different errors, for example if internet connection has not been established yet :)

But anyway, you decided for option 1.

Your next day:

For some other reason i had to run my handy today (i think since 11:00) in online mode. Then i checked at about 15:15 (no other time before) my handy and i have green screen.

This looks like the automatic background update didn't take place during low energy mode, as it was updated with a delay of about 10 hours, after you turned on normal power mode.

Also when i checked number of queries: today i had 15 queries at 12:24.
On tomorrow i will proceed with item 1 from above (see my last message).

When there were 15 queries, it looks like, the first call didn't succeed...

Then your next day:

Last night i run my handy in low energy mode with WLAN actice. Today i switched at 11:25 from low energy mode to normal energy mode. My first action was: I went to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen). As i mentioned already yesterday: To call this function is not possible for me in low energy mode, so i made it in normal energy mode as first action. Result: There was no entry for today 22.08.
Then i went back and immediateley opened my cwa app. Actualization was done on yesterday. I saw this on the first screen and then i switched to screen "X Ihr Risikostatus". There you can see the last actualization time. Yesterday at 12:24
This time information was also visible on the first start screen. But i did not make a foto.
Then i went back from screen "X Ihr Risikostatus" to start screen. This was done immediateley without any signal to a user that something will be processed. Then i got the following screen
So the actualization must have been done in this minute at 11:26 on today. Next action from me: I left cwa app and went again to (Covid-19-Benachrichtigungen > Überprüfungen auf mögliche Begegnungen). Result now: 16 items for today at 11:26
So it seems to me, that in this version 1.2.0 of cwa a online actualization (as i know it from last version 1.1.1) is not executed and that it is somehow also in the background, even if you have cwa opened or not.

What I understand from your report is, that again the automatic background update failed because of the low energy mode. In the minute you opened CWA, the update was triggered. There is a display issue, see here -> #1024 that the new update time is actualized only, when you switch to a different screen and back.

By the way, since CWA 1.2.0 screenshots are enabled again :) May be more easy to use.

Ok, I'd really like to see, if with the new versions of CWA and also the Google Exposure Notification Framework (ENF) it is still possible to trigger the 'Time Out waiting for 60000 ms'. As an ENF update is currently being rolled out, that might solve that problem, I'd suggest to wait one week with our experiments, and meet again here after, if you like.
What do you think?

Kind regards, and have a nice Sunday!

[stevie21]

Hi @vaubaehn,
To have same understanding: In low energy mode it is not possible for me to start the cwa app or to open the "Covid-19-Benachrichtigungen" app.
There are 2 possibilities to use the low energy mode. There is version "middle" and version "max" and i am always using version "max". In this mode i have limited access to "Einstellungen" and i can exchange some apps on the start screen. But there are only certain apps, which are possible to be exchanged. And the cwa app is not in that list of usable apps that i can exchange. Also the "Covid-19-Benachrichtigungen" app is not in the list of usable apps
Of course: i can wait a week and we can go on then.
Have a nice week.

[joey1949]

Same problem Ursache:3 Etwas ist schiefgelaufen (39508) on Xiaomi Mi A2 lite (Android 10) since Oct. 3

[daimpi]

@joey1949

Same problem Ursache:3 Etwas ist schiefgelaufen (39508) on Xiaomi Mi A2 lite (Android 10) since Oct. 3

This issue is now tracked over here: #1021

It seems your error doesn't disappear after 24h, is this correct? If so you could try what I suggested here. If you do I'd be interested to hear what you find (let's continue this conversation over at #1021 though).

[birgit-xy]

working for month same procedure every day and now 39508 - Xiaomi Redmi Note 8T :(

[daimpi]

@birgit-xy this issue is now tracked over here: #1021

CWA 1.5 should fix the problem and it should appear in the Google Play store on Monday.

[DanielKroegerPriv]

I do have the same problem - last actualisation was 01.10.2020
Android Version: 6.0.1
Device is: Samsung Galaxy S5 Mini
Modell Number: SM-G800F
App Version: 1.3.1
Google Play Services Version: 20.36.15

[elanfer]

Same problem here, also after updating CWA to version 1.5. ENF is downloading new keys but there seems to be a problem in the communication between CWA and ENF API. Exception is the same that was shown in the screenshot from the first post is this issue.

Android Version: 7
Device is: Moto G4
App Version: 1.5
ENF Version: 17203704005
Play Service Version: 20.36.15

I'm happy to help if you need any further logs or dumps to troubleshoot this issue.

[masema67]

same here - updated to Version 1.5 right now and even after restart the error 39508 persists!

Android Version: 10
Device is: Moto G7plus
App Version: 1.5
ENF Version: 17203704005
Play Service Version: 22.2.13-21

Would be nice if the App worked as planned.
Let me know if you need further information.

[nichu42]

Yes, v1.5 didn't fix it.

Android Version: 6.0.1
Device is: Samsung Galaxy S5 Neo SM-G903F
App Version: 1.5
ENF Version: 17203915000
Play Service Version: 20.39.15 updated 06-Oct-2020

Last signature download was 12-Oct-2020 09:01 - since then I'm getting the error message as mentioned in the OP.
I'm glad the app works on own / private phone.

[daimpi]

This issue is tracked over here: #1021

If your rate limit was already hit today, there is nothing that the CWA update can do to revert this for today. This limit will be reset tomorrow though at 02:00 CEST (00:00 UTC). From then on CWA 1.5 should prevent this problem from occurring again. Please wait at least until then and report back afterwards (over at #1021) whether the problem still exists or disappeared for you 🙂.

[elanfer]

In my case it was the API limit, today the update worked and I've got no error anymore (v1.5).

[svengabr]

Please continue the discussion in our main issue here: #1021