Error 39508 / Limit already reached

UPDATE 16.01.2021

• See https://www.coronawarn.app/en/faq/#API39508:

Limit already reached (Previously: Error when communicating with Google API (39508))

UPDATE 16.01.2021:

The notification reads now:

Limit already reached

No more exposure checks possible today, as you have reached the maximum number of checks per day defined by your operating system. Please check your risk status again tomorrow.

The whole exposure checking went through a major update with the release of 1.9.1, see also the blog post from Dec 16, 2020, and since the release 1.9.1 no more reports on this issue have been submitted.

However, should you experience an issue related to this error notification, please submit your report here: corona-warn-app/cwa-app-android#1459.

---

IMPORTANT / WICHTIG 23.10.2020

Please update your CWA App to version 1.5+ and wait up to 24 hours before you post a bug report here.

Bitte aktualisieren Sie Ihre Corona Warn App auf Version 1.5+ und warten Sie 24 Stunden bevor Sie einen Fehlerbericht schreiben.

This is a follow-up topic

Prior to CWA release 1.5 there was a bug “CAUSE: 3 Something went wrong. ApiException: 39508”. There was a fix for this issue delivered with the CWA update 1.5. We are currently in the effort in contacting many android users that reported the bug in the past and ask them to update to the latest version.

If you still receiving the error 39508 after updating to 1.5 and waiting 24 hours, please report your issue here.

Please report:

• Mobile device
• Android version
• App Version
• ENF Version
• Play Services version

There is also an FAQ entry available in english and german:

• English: https://www.coronawarn.app/en/faq/#API39508
• German: https://www.coronawarn.app/de/faq/#API39508

---

Internal Tracking ID: EXPOSUREAPP-3435 Old Tracking ID prior to 1.5: EXPOSUREAPP-2389

[d4rken]

@MikeMcC399 While not designed as fix for this, #1550 will have a positive effect on this issue, due to stricter download behavior and decision regarding submission to the ENF in error cases. Were are also looking into background scheduling behavior but have not yet identified a connection between this issue and the scheduling.

[codejus]

I just wanted to create the bug report, but suddenly CWA made the first risk calculation two days after setting it up. But as I connected my phone via usb to my PC to use adb for the bug report the phone has had the optimal condtions regarding power and connection for the fetching and calculation process. So any issues which are maybe connected to these two areas can’t be ruled out really.

Will report back if it happens again.