What does this error mean? Not updating risk status >24h. Issue with API? Insufficient storage recently resolved, App up to date.

[Watzefack04]

Avoid duplicates

• Question is not already answered in the FAQ
• Question is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
• Question has not already been asked in another issue

Your Question

• Source File:
• Line(s):
• Question:

---

Internal Tracking ID: EXPOSUREAPP-2241

[Watzefack04]

Text of error notification: CAUSE: 3 Something went wrong [.....] then link to deleted FAQ page (404 error).

[s-martin]

Same error here since yesterday. This is the first error I received, before CWA always worked flawless.

Moto G6 Plus, Android 9, CWA 1.2.1

[kbobrowski]

This seems to be similar issue to #1021 . @Watzefack04 @s-martin I think it would be quite useful if you shared when exposure checks happened, like I did in original issue, just to confirm the same behavior (Settings -> Google -> COVID-19 exposure notifications -> Exposure checks -> three dots in upper-right corner -> Export exposure checks)

[not-a-feature]

Same problem here on a Moto G7 Play, Android 10, CWA 1.2.1

Here the exported exposure checks:
`August 12, 2020 02:18 (key count: 2290)
August 12, 2020 02:18 (key count: 2520)
August 12, 2020 02:18 (key count: 1575)
August 12, 2020 02:18 (key count: 1405)
August 12, 2020 02:18 (key count: 1385)
August 12, 2020 02:18 (key count: 1645)
August 12, 2020 02:18 (key count: 2813)
August 12, 2020 02:18 (key count: 2415)
August 12, 2020 02:18 (key count: 3050)
August 12, 2020 02:18 (key count: 2210)
August 12, 2020 02:18 (key count: 1655)
August 12, 2020 02:18 (key count: 565)

August 13, 2020 02:48 (key count: 2520)
August 13, 2020 02:48 (key count: 1575)
August 13, 2020 02:48 (key count: 1405)
August 13, 2020 02:48 (key count: 1385)
August 13, 2020 02:48 (key count: 1645)
August 13, 2020 02:48 (key count: 2813)
August 13, 2020 02:48 (key count: 2415)
August 13, 2020 02:48 (key count: 3050)
August 13, 2020 02:48 (key count: 2210)
August 13, 2020 02:48 (key count: 1655)
August 13, 2020 02:48 (key count: 565)
August 13, 2020 02:48 (key count: 2380)
August 13, 2020 02:48 (key count: 2285)
August 13, 2020 02:48 (key count: 3800)

August 14, 2020 01:59 (key count: 1575)
August 14, 2020 01:59 (key count: 1405)
August 14, 2020 01:59 (key count: 1385)
August 14, 2020 01:59 (key count: 1645)
August 14, 2020 01:59 (key count: 2813)
August 14, 2020 01:59 (key count: 2415)
August 14, 2020 01:59 (key count: 3050)
August 14, 2020 01:59 (key count: 2210)
August 14, 2020 01:59 (key count: 1655)
August 14, 2020 01:59 (key count: 565)
August 14, 2020 01:59 (key count: 2380)
August 14, 2020 01:59 (key count: 2285)
August 14, 2020 01:59 (key count: 3800)

August 15, 2020 02:34 (key count: 1405)
August 15, 2020 02:34 (key count: 1385)
August 15, 2020 02:34 (key count: 1645)
August 15, 2020 02:34 (key count: 2813)
August 15, 2020 02:34 (key count: 2415)
August 15, 2020 02:34 (key count: 3050)
August 15, 2020 02:34 (key count: 2210)
August 15, 2020 02:34 (key count: 1655)
August 15, 2020 02:34 (key count: 565)
August 15, 2020 02:34 (key count: 2380)
August 15, 2020 02:34 (key count: 2285)
August 15, 2020 02:34 (key count: 3800)
August 15, 2020 02:34 (key count: 3940)
August 15, 2020 02:34 (key count: 3020)

August 16, 2020 03:37 (key count: 1385)
August 16, 2020 03:37 (key count: 1645)
August 16, 2020 03:37 (key count: 2813)
August 16, 2020 03:37 (key count: 2415)
August 16, 2020 03:37 (key count: 3050)
August 16, 2020 03:37 (key count: 2210)
August 16, 2020 03:37 (key count: 1655)
August 16, 2020 03:37 (key count: 565)
August 16, 2020 03:37 (key count: 2380)
August 16, 2020 03:37 (key count: 2285)
August 16, 2020 03:37 (key count: 3800)
August 16, 2020 03:37 (key count: 3940)
August 16, 2020 03:37 (key count: 3020)
August 16, 2020 03:37 (key count: 2675)

August 17, 2020 02:00 (key count: 1645)
August 17, 2020 02:00 (key count: 2813)
August 17, 2020 02:00 (key count: 2415)
August 17, 2020 02:00 (key count: 3050)
August 17, 2020 02:00 (key count: 2210)
August 17, 2020 02:00 (key count: 1655)
August 17, 2020 02:00 (key count: 565)
August 17, 2020 02:00 (key count: 2380)
August 17, 2020 02:00 (key count: 2285)
August 17, 2020 02:00 (key count: 3800)
August 17, 2020 02:00 (key count: 3940)
August 17, 2020 02:00 (key count: 3020)
August 17, 2020 02:00 (key count: 2675)

August 18, 2020 02:31 (key count: 2813)
August 18, 2020 02:31 (key count: 2415)
August 18, 2020 02:31 (key count: 3050)
August 18, 2020 02:31 (key count: 2210)
August 18, 2020 02:31 (key count: 1655)
August 18, 2020 02:31 (key count: 565)
August 18, 2020 02:31 (key count: 2380)
August 18, 2020 02:31 (key count: 2285)
August 18, 2020 02:31 (key count: 3800)

August 18, 2020 02:33 (key count: 2813)
August 18, 2020 02:33 (key count: 2415)
August 18, 2020 02:33 (key count: 3050)
August 18, 2020 02:33 (key count: 2210)
August 18, 2020 02:33 (key count: 1655)
August 18, 2020 02:33 (key count: 565)
August 18, 2020 02:33 (key count: 2380)
August 18, 2020 02:33 (key count: 2285)
August 18, 2020 02:33 (key count: 3800)
August 18, 2020 02:33 (key count: 3940)
August 18, 2020 02:33 (key count: 3020)`

Cheers,

[kbobrowski]

@not-a-feature thanks, I've posted reformatted log and some comment here in the original issue: #1021 (comment)

[MikeMcC399]

Hi @Watzefack04

What version of the Google Exposure Notification System is running on your mobile device?
Settings > Google > COVID-19 exposure notifications, then scroll to bottom of page.

What Android version and which mobile device do you have?

It looks like the Google Play services might have been reset to an early factory installed version.

[not-a-feature]

Follow-up to previous comment:
#1030 (comment)

As mentioned about 24h ago I had the same issue. On todays exposure check everything seems fine. The app says "Aktualisiert Heute 2:04".
Yesterday I opened the app several times and killed the process once.

If needed I'll provide the log,
Cheers

[ghost]

Hello @Watzefack04,

thank you for reaching out. Please, as @MikeMcC399 asked you, share the Android version as well as the ENF version with us. I also kindly like to ask you, if you please could share the steps to reproduce the issue. If there are no specific steps, please just describe what you did right before this error did occur, even if it is just that you have opened the app. @not-a-feature and @s-martin , can you also please share your steps to reproduce?

In the meantime, I will get in touch with our development team.

thanks,
LMM

Corona-Warn-App Open Source Team

[not-a-feature]

Hi @GPclips ,
the steps to reproduce were straight forward,
System: Moto G7 Play, Android 10, CWA: 1.2.1

1. App was installed since day 1 without any errors and was opened almost every day at least once
2. Open the App –> Green panel says: „Aktualisiert: Gestern 02:00“
3. Tap on the green panel –> Error Message pops ups „Cause 3“
4. Close the App
5. Reopen, immediately the error message pops up
6. Killed the app
7. Reopen, immediately the error message pops up
8. After 24h the error seems to be resolved

[MikeMcC399]

Hi @not-a-feature

Did you have the same stack trace as @Watzefack04 ? If not, then the root cause is probably different.

The play-services-base@@17.3.0:2 made me suspicious about the Google Play services version installed.

[not-a-feature]

Due to the magic disappearance of the bug and the blocking of screenshots i can't recall that. Sorry for that.

I have the Google Play Services Version 20.26.14 installed which is the newest version (for my device at least)

[vaubaehn]

Hi @MikeMcC399 ,

The play-services-base@@17.3.0:2 made me suspicious about the Google Play services version installed.

they're quite new -> here

Hi @not-a-feature ,
if you at last could provide your ENF-version, like discribed -> here , could be helpful to find out, if maybe the initialization of a new ENF-version could have caused that error (in the latest days, there were at least 2 different new versions rolled out, shortly one after the other).

Hi @GPclips ,
i think Jira ID: EXPOSUREAPP-2241 is duplicate of ID: EXPOSUREAPP-2213.

[not-a-feature]

Sure: ENF Version: 16203302004

[MikeMcC399]

Hi @vaubaehn

The play-services-base@@17.3.0:2 made me suspicious about the Google Play services version installed.

they're quite new -> Google API release June 1, 2020

Thank you very much for your correction. My mistake! I was confusing the play-services-base version with the Google Play services version. Not the same thing!

[MikeMcC399]

We haven't heard back from @Watzefack04 but just by coincidence I think I just had exactly the same error. I left a secondary mobile device at home whilst I was away for 5 days. The device was switched on, not connected to a charger. Also coincidentally my WLAN router wasn't connecting to the internet correctly. When I returned, the battery of the mobile device was flat, so I connected it to a charger and switched it on. I also restarted my WLAN router which cleared the WiFi issues.
The Android mobile device Settings > Google > COVID-19 Exposure Notifications showed that it had tried 13 times at 12:48 and 7 times at 06:57 (total of 20 times) today to do an exposure check.

The first error screen said
CAUSE: 3
Something went wrong.
"The Corona-Warn-App is running correctly, but we cannot update your current risk status. Exposure logging remains active and is working correctly. For further information, please see our FAQ page: https://www.coronawarn.app/en/faq/(39508)"

The FAQ page explains that it is due to the API being called too often and it should resolve itself in 24 hours.

The detail stack trace in #1030 (comment) shows the ApiException 39508, so this is exactly the case covered by the FAQs. I had a stack trace on my device which looked very, very similar.

@not-a-feature
Your detailed exposure checks you listed in #1030 (comment) show that there were 20 checks on Aug 18, 2020, so it seems that your device also exceeded the quota for number of checks.

(Sorry to all for my false alarm about the version of play-services-base! I was not at my home base for several days and I didn't have access to my usual reference and test resources.)

Update
The FAQ was right. This morning the error has cleared itself and all is working again.

[pathmapper]

Just reported a similar case in #1065

[svengabr]

Hello everyone,

thank you all for your feedback so far. Since there are currently several issues with exactly the same problem, I need to close this issue to move the discussion to a central place.

Please continue the discussion here: #1021

I will link the existing findings in Jira so the information on this ticket wont get lost.

Best regards,
SG

Corona-Warn-App Open Source Team

[svengabr]

Duplicate of #1021