The app also displays "Updated: Yesterday, 07:46", so it did not register properly the check that was made today (14.08) at 07:36

kbobrowski on 14 Aug 2020

Hi @kbobrowski , according to the wrong link to the faq, maybe it had been introduced by #864 (CWA v1.2.0) ?
Maybe #1007 after #996 may solve it? (CWA v1.3.0)

CWA displays yesterday's date - what do the Google Exposure Notifications ("COVID-19-Benachrichtigungen") display (update date in main screen)?

Can you provide a screenshot of the error message, if error is reproducable (would be only for my own curiosity, tbh)

vaubaehn on 14 Aug 2020

@kbobrowski , some additional questions:
were both matchings on August 14 performed as a background task (CWA not in foreground)? Or was first background, second foreground?

vaubaehn on 14 Aug 2020

Hi @vaubaehn , Google EN just displays the last date from the logs I posted, so "Last checked for potential exposure on today at 09:36". 39508 error happens every time I open the app now as the app holds "last time diagnosis keys were provided" at "yesterday, 07:36", so it will exceed limit of 20 calls every time. Will check tomorrow if the issue repeats again.

Not sure if it was background / foreground, I guess first could be background and second foreground.

kbobrowski on 14 Aug 2020

👍1

@kbobrowski , one feature request for the ENF, that our devs here might direct to Google, could be that ProvideDiagnosisKeys() creates an object with some statistics about some technical results of that task, e. g., if the task had been completed successfully, time of last API-call, remaining count of API-calls. That would support the EN-apps (CWA) to validate if they may call ProvideDiagnosisKeys() without running into an exception.
Do you think that could be useful?

vaubaehn on 14 Aug 2020

At the expense of making my app useless for the next couple of days I was shifting the date forward which was resetting internal GMS count and forcing update of diagnosis keys, and was not able to reproduce this error.

@vaubaehn that's a good idea to have some more information about whether the call to provideDiagnosisKeys was successful, but I think the implementation of CWA can be improved even without the action on Google side. Probably better implementation would be to just mirror the same mechanism that GMS is using to count the calls to provideDiagnosisKeys, and update this count before the call to provideDiagnosisKeys. This way it would be impossible to ever exceed quota limit. The GMS's algorithm is simply:

public class Quota {

  private long day = 0;
  private int count = 0;

  public void updateCount() {
    long currentDay = System.currentTimeMillis() / TimeUnit.HOURS.toMillis(24);
    if (currentDay > day) {
      day = currentDay;
      count = 0;
    }
    if (count < 20) {
      count += 1;
    }
  }

  public boolean canCallProvideDiagnosisKeys() {
    return count < 20;
  }
}

But right now CWA is only executing executeFetchDateUpdate(currentDate) after all 14 calls were successful, otherwise it is not executed at all which leads to exceeded quota.

kbobrowski on 14 Aug 2020

👍2

@kbobrowski , right, CWA could improve here, but I suspect ENF to fail matching keys under some conditions (https://github.com/corona-warn-app/cwa-app-android/issues/774#issuecomment-674021759) , but counting the call though. In that case, CWA couldn't do anything about it...

vaubaehn on 14 Aug 2020

@vaubaehn right, EN may fail to match keys and still count the call, we have seen it e.g. with error 10 - these kind of bugs have to be fixed by Google. But the disadvantage of current CWA implementation is that in this situation it is practically guaranteed that 39508 error will follow as CWA is not maintaining any count of calls to provideDiagnosisKeys. This 39508 error will appear every time the app is launched, which leads to bad UX.

I think CWA should maintain internal count of calls and simply not attempt to call if the quota is already exceeded. What would be very useful is to instead display the information about it (perhaps in another UI section), together with information about original error, which is currently not displayed to the user if it has happened in the background.

kbobrowski on 14 Aug 2020

👍3

By the way, I found us often handling with the rate limit/quota of ProvideDiagnosisKeys(), but I still couldn't find any information on why Apple and Google actually set a quota.
As the diagnosis keys are downloaded by the app without control of ENF, it's not about preventing DOS of server.
Only reasons I could imagine is either preventing some kind of brute force against TEKs (information disclosure), or preventing high CPU load (load through cryptography while matching; intentionally or accidently DOS against device). Is there any information released, why a quota is introduced here?

vaubaehn on 14 Aug 2020

👍1

I don't know why the quota is here, I can only speculate that the reason is "privacy" (there are some theoretically possible scenarios which may lead to some privacy implications if there is no quota at all) or "battery"

kbobrowski on 14 Aug 2020

I hope it's not the latter ("battery")... because that might underline the CPU load caused by cryptography, In that case, I don't know where this all might lead to, when a) amount of users of CWA should increase significantly one day, b) reported positive cases are drastically increasing (2nd wave * more users), c) big events are planned/more using of public transport in cold weather (much more collected RPIs)...
If ENFs WakeUpService can also ensure full CPU power (not only ensuring to start the scheduled task once per day) for ProvideDiagnosisKeys() as a background service while the system dozes to be completed successfully without time out, then everything will be fine. If not...

Anyway, have a nice week-end!

vaubaehn on 14 Aug 2020

People are also reporting this error on twitter: https://twitter.com/elliwir/status/1294262706762063873

@vaubaehn Have a nice weekend as well!

kbobrowski on 14 Aug 2020

I couldn't resist to have one more look here...
If you follow the twitter-link, and follow the whole conversation of @daimpi, there is a screenshot providing the user's version of ENF - version 16203016000 is obviously being rolled out! https://github.com/corona-warn-app/cwa-app-android/issues/933#issuecomment-673570624
@kbobrowski maybe you already got the update, but your cached version number is still showing v1.5? You may check later, if it changed...
And thanks :), now I'm gone

vaubaehn on 14 Aug 2020

@vaubaehn it's still v1.5 for me

kbobrowski on 14 Aug 2020

There definitely more people with this problem. Here is just one other recent example: https://twitter.com/DieterKlinkner/status/1294588826908753920

One thing that caught my attention is that this person seemingly also has a quite intensive routine to try and get the app going.

daimpi on 15 Aug 2020

I got another user reporting this problem and for them not opening the app for 24h doesn't seem to have solved the issue.

Device: Samsung Galaxy A6
CWA 1.2.1

Any ideas?

daimpi on 17 Aug 2020

My working assumption is the timeout - if fetching diagnosis keys and submitting them to API is not finished within 60 seconds then the transaction is terminated, and if some diagnosis keys were already submitted in this terminated transaction, then next retry may lead to exceeded quota.

While testing this with artificial delay in the transaction it also happened very rarely (only once in many tries) that transaction hanged without completing a single call to provideDiagnosisKeys, which lead to the timeout.

One possibly important thing here is that CWA already operates with very thin timeout margin - without introducing any artificial delay and on the fast wifi network (100 Mbps) the whole process of fetching 14 diagnosis keys and submitting all of them to the API takes about 45 seconds on a slow Android 6 device, which is 75% of available timeout. Interestingly the description while fetching keys says that it may take "couple of minutes", but after 1 minute there is hard termination.

The only counter argument to this is that in my case (logs from the first post in this issue) on Android 10 all 14 diagnosis keys have been submitted, and then transaction was repeated, so it's quite unlikely that timeout happened while API was processing 14th key and just before updating last-fetch-date, still possible though.

kbobrowski on 17 Aug 2020

👍2

One possibly important thing here is that CWA already operates with very thin timeout margin - without introducing any artificial delay and on the fast wifi network (100 Mbps) the whole process of fetching 14 diagnosis keys and submitting all of them to the API takes about 45 seconds on a slow Android 6 device, which is 75% of available timeout.

Wow… that's much longer than I'd have thought this process takes… I've always assumed that this is done in a few seconds max. I guess the limiting factor in this case is not the bandwidth but the (cryptography-) performance of the SoC, right?

What would speak for this hypothesis is the fact that the Galaxy A6 mentioned above is certainly not the most potent device… On which device did you observe the 45s sync time?

daimpi on 18 Aug 2020

@daimpi I guess slow device (Motorola G2) plays a role here, but it seems that just downloading keys takes significant portion of this timeout limit (if it has to download all 14 of them).

Similar issue reported in #1030 , if it is the same pattern as in my case (all 14 keys successfully submitted, but then CWA retried the same day), then I think timeout hypothesis would be less likely

kbobrowski on 18 Aug 2020

Same here.

Moto G6 Plus
Android 9
CWA 1.2.1
Google Play Services 20.30.19

s-martin on 18 Aug 2020

Another exposure log provided by @not-a-feature (https://github.com/corona-warn-app/cwa-app-android/issues/1030#issuecomment-675318432):

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)

so this time CWA only submitted 9 keys on 18.08 02:31, and then retried submitting 11 keys 18.08 02:33. So I guess the timeout hypothesis is still possible, perhaps new Play Services is taking a bit more time to process provideDiagnosisKeys call, or fails sometimes by hanging indefinitely or there is another error.

Would be great if CWA allowed for exporting logs for the last 48 hours or so, just storing them in a text file and allowing user to export it from the app, otherwise there is no easy way to know what was the first error that happened, 39508 is just a consequence of it.

kbobrowski on 18 Aug 2020

👍2

Same here today.

LG-H815 (LG G4)
Android 6.0
CWA 1.2.1 (since 3 days)
ENF 16203019000 in the morning. now: 16203302004
GPS 20.30.19

Usually background update worked like a charm for me (usually around 8:23am, +- 3 minutes).
After updating CWA to 1.2.1, the day before yesterday manual check (before expected update) at 7:00am.
Yesterday, manual check (before expected update) at 5:21am.
Today, no automatic update until 8:30 (checked via COVID-19-notifications) with telephone plugged to charge. Then reading news in internet. phone still plugged to charge.
Checking again for update via Covid-19-notifications at 9:08am -> update was done at 08:53am but 20 checks all within the same minute! First 14 + 6 duplicate of the first. Then opening CWA: API 39508.

=> "Cause 9002 Timed Out while waiting for 60000 ms" highly unlikely.

vaubaehn on 18 Aug 2020

I was trying to reproduce something by calling provideDiagnosisKeys over 3000 times in one hour but it always worked (in the foreground). @vaubaehn if you had all the 20 calls in the same minute then indeed timeout error is unlikely. Would be good to stress-test API in the background mode to see what is failing here, perhaps some issues with background job

kbobrowski on 18 Aug 2020

👍2

I got another user reporting this problem and for them not opening the app for 24h doesn't seem to have solved the issue.

Device: Samsung Galaxy A6
CWA 1.2.1

The user reported back today that after not opening CWA for another 24h the problem seems to have finally disappeared for them 🙂.

daimpi on 18 Aug 2020

Same issue here - interestingly started to appear right on first check after updating CWA to 1.2.1. Wife has the very exact same phone, no issue though. Moto G5 Plus, Android 8.0.1, CWA 1.2.1.

sosstuttgart on 19 Aug 2020

I could not reproduce this issue so far, but there are numerous recent Play Store reviews mentioning 39508, interestingly it started happening roughly the same time (last couple of days) for everyone. So it's either connected to the possibly higher volume of Diagnosis Keys uploaded or it was triggered by CWA / Play Services update

kbobrowski on 19 Aug 2020

The 404 is now mitigated and people should reach the right FAQ entry even when being directed to https://www.coronawarn.app/en/faq/(39508) or https://www.coronawarn.app/de/faq/(39508). Of course, this is just a mitigation and needs to be fixed within the app.

tkowark on 19 Aug 2020

👍1

Can confirm, issue is gone after 24hours.

s-martin on 19 Aug 2020

👍1

@tkowark thanks for resolving 404, do you have some plan on resolving 39508 in this case? it's difficult to find the root cause, but following implementation improvements should mitigate it:

count number of calls to provideDiagnosisKeys before each call
keep track of which files were submitted successfully, and in case of unexpected transaction termination - retry only with not-submitted files
record logs of any errors and make them available to the user, to eliminate root cause of issues
try to submit most relevant (most recent) files first

With these features implemented the worst case scenario is that the call to provideDiagnosisKeys may fail with GMS still counting this call towards the quota. But it will not lead to 39508 since we are counting all the calls before executing (first point). In the worst case it may result it not all the 14 files submitted in one day, but there are 6 extra tries available, so almost certainly it won't be the problem. And even if transaction would fail 6 times in a day, files are submitted from most relevant to least relevant, so it would have insignificant impact on quality of predicted exposure status.

I think that basically transaction should be designed with the assumption that it can abruptly terminate at any stage. Right now there is an assumption that once transaction starts (and successfully downloads all files) it will successfully submit all files to ENF and then successfully update "time of last transaction execution" value, which as we can see now might not be the case.

kbobrowski on 20 Aug 2020

👍2

I've raised your proposal with the app dev team and linked the comment in all Jira issues that somehow concern 39508.

tkowark on 20 Aug 2020

👍2

I believe this is the same problem my phone is having.
No problems until the day after the update to vers 1.2.1. Last check at 19. Aug 08:26 after that came error 3: #39508.
Keys appear to have been exchanged as there is a non-zero number of keys for days after the 19th.
Not opening CWA for 24h does not resolve the issue.
I never turned off "Risiko-Ermittlung" so I don't know why it's asking me to activate it. When I tap it it shows that the slider is in the active position.
Xperia Z3 compact, Android 6.0.1

Screenshot_20200822-182121
Screenshot_20200822-184558
Screenshot_20200822-184605
Screenshot_20200822-182114

jmbaldwin on 22 Aug 2020

Just reported a similar case in https://github.com/corona-warn-app/cwa-app-android/issues/1065

pathmapper on 23 Aug 2020

This is definitely widespread as I already experienced this independently on both Android 6 and Android 10 devices. I think that timeout may still play a role here, as I noticed that sometimes it just takes a long time to loop over all 14 calls to provideDiagnosisKeys.

@ developers: Would you consider increasing timeout limit from 60 seconds to maybe 2-3 times more? Is there a reason it is set to just 60 seconds?

kbobrowski on 23 Aug 2020

@tkowark thanks for forwarding my suggestion, it is actually very similar to the way Swiss app handles calling EN framework

We are only allowed to call provideDiagnosisKeys() 20 times per UTC day. Because we check for every of the past 10 days individually, this allows us to check for exposure at most twice per day. These checks happen after 6am and 6pm (swiss time) when the SyncWorker is scheduled the next time or the app is opened. All 10 days are checked individually and if one fails it is retried on the next run. No checks are made between midnight UTC and 6am (swiss time) to prevent exceeding the rate limit per UTC day.

Perhaps this implementation could be even copied over to CWA: https://github.com/DP-3T/dp3t-sdk-android/blob/739bf165b0d47c8ccdea6f3dbbd2252cb521aef4/dp3t-sdk/sdk/src/main/java/org/dpppt/android/sdk/internal/SyncWorker.java#L215

kbobrowski on 24 Aug 2020

👍2

Hi @harambasicluka I think this issue was not precisely linked to #1074 - this pull request should not be closing this issue. This issue is mainly about 39508 which is still not resolved. Perhaps I should have created two separate issues, one for 39508 and one for the wrong link in the error message ;)

kbobrowski on 26 Aug 2020

👍2

Duplicate of #1065

svengabr on 26 Aug 2020

Duplicate of #1030

svengabr on 26 Aug 2020

Hello everyone,

thank you all for your feedback so far. I needed to close 2 other issues that were created for exactly the same problem. Let's continue our discussion here.

Best regards,
SG

Corona-Warn-App Open Source Team

svengabr on 26 Aug 2020

My issue described in this comment resolved itself today. A minute ago, I have opened the app again, and everything has returned to normal 🤷‍♂️

NKarolak on 26 Aug 2020

👍3

@kbobrowski I've removed the [wrong link to FAQ] part from the issue title. I hope that's ok with you and we avoid that this issue gets closed by accident in the future.

tkowark on 26 Aug 2020

👍2

2 days later the connect to the API works again. ENF version 16203302004 App 1.2.1

marcohabeck on 27 Aug 2020

Follow-up on https://github.com/corona-warn-app/cwa-app-android/issues/1065#issuecomment-680736574:

Left the phone switched on during the night and this morning the error is gone again.

Looks like under some circumstances the error could be triggered by switching the phone off during the night.

pathmapper on 27 Aug 2020

👀1

Same here, keeping the phone active over night resolved the issue in two stages, but looks just partly.

First: Error 39508 popup and risk status staying white, "cannot be caluculated". Keeping the phone active overnight lead to popup for 39508 still appearing, but status now green with sync state two days back. Another day later: no popup, green box, calculated status with sync on the very same day. Perfect.

Still about every third day the phone is not syncing the IDs and reporting green state with downloaded IDs of a day before. That has not been noticed before update to latest CWD version.

sosstuttgart on 27 Aug 2020

My issue has fixed itself although I continued shutting my phone down every night 🤷

NKarolak on 27 Aug 2020

After 13 days this issue reappeared on my Android 10 device today, so unfortunately today the app won't be updated with DKs. Last time it synchronized yesterday at 03:33

kbobrowski on 27 Aug 2020

My girlfriend has the same bug with:

Android 9
Huawei P10 lite
CWA 1.2.1
Play Services 20.30.19

Unfortunately this appeared shortly after she registered the QR-Code of a Corona test.
We wanted to get the test result from the app as the weekend is coming up and the doctors office is closed.
Until then we are obviously staying inside.

Will the test results still be fetched?

And how am I able to create/find these exposure logs to provide some details?

schneeemensch on 28 Aug 2020

Unfortunately this appeared shortly after she registered the QR-Code of a Corona test.
We wanted to get the test result from the app as the weekend is coming up and the doctors office is closed.
Until then we are obviously staying inside.

This is o/c quite a tricky situation: the usual recommendation I give to ppl with this error: close the app -> wait 24h -> open the app again & check whether the problem has disappeared, but given that you just scanned a test you might be anxious to get the results which I o/c understand.

Will the test results still be fetched?

I'm not sure on this… My guess (which is really just a guess) would be that test results are still fetched, as this doesn't really require interaction with the ENF where the rate-limiting problem occurs afaik… but I could be wrong on that.

And how am I able to create/find these exposure logs to provide some details?

The exposure logs can be found and exported in the following way:
On your phone -> Settings -> Google ->Covid-19 Notifications -> checks for possible contacts -> burger menu in the upper right corner -> export

If you want to share the file here, just put it in a zip file it or rename the ending to .txt 🙂

daimpi on 28 Aug 2020

We have just received test result (and it's negative :-) ). That means what you (and I) guessed is correct and the bug does not hinder fetching the test results.

Thanks for showing me how to extract the exposure logs.
I looked through them and found the same pattern. Tonight the app fetched 10 times at 2:38am and afterwards fetched 14 times at 5:48am. This could support the timeout theory.

schneeemensch on 28 Aug 2020

👍3

Here a log from a friend.
You can see 296 checks in 14 days.
Starting from 15.08 the key-check often does not compleate.
At the last days not all available key-files have been checked.
On 23.08 the log shows a compleat scan as 09:19 but does another scan at 16:19 that does not compleat (>20 files per day).
So you can see, if the first scan fails and more than 6 files have been scaned then the 2 must fail du to the 20 file limit.

1    2020-07-29 { "timestamp": "12. August 2020, 15:09", "keyCount": 2290, "matchesCount": 0, "appName": "Corona-Warn", "hash": "dCtVfMM0AnZYHNokm\/MpdNohanNgipPHynGvZ4De27E=" },
2    2020-07-30 { "timestamp": "12. August 2020, 15:09", "keyCount": 2520, "matchesCount": 0, "appName": "Corona-Warn", "hash": "8JD364tR2WBkyNBCZ7D03SUYhLqI4vYCdYo3E8WXujY=" },
3    2020-07-31 { "timestamp": "12. August 2020, 15:09", "keyCount": 1575, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Icn\/SxaXPAydSKjbN9coAU9Bgn\/nRVEeAfrmg1ic3\/4=" },
4    2020-08-01 { "timestamp": "12. August 2020, 15:09", "keyCount": 1405, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Vq9k1G0xEzO4zuBDCgt++HygT8Q2mqcZZ0972\/6MMKo=" },
5    2020-08-02 { "timestamp": "12. August 2020, 15:09", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
6    2020-08-03 { "timestamp": "12. August 2020, 15:09", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
7    2020-08-04 { "timestamp": "12. August 2020, 15:09", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
8    2020-08-05 { "timestamp": "12. August 2020, 15:09", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
9    2020-08-06 { "timestamp": "12. August 2020, 15:09", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
A    2020-08-07 { "timestamp": "12. August 2020, 15:09", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
B    2020-08-08 { "timestamp": "12. August 2020, 15:09", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
C    2020-08-09 { "timestamp": "12. August 2020, 15:09", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
D    2020-08-10 { "timestamp": "12. August 2020, 15:09", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
E    2020-08-11 { "timestamp": "12. August 2020, 15:09", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-07-30 { "timestamp": "13. August 2020, 15:13", "keyCount": 2520, "matchesCount": 0, "appName": "Corona-Warn", "hash": "8JD364tR2WBkyNBCZ7D03SUYhLqI4vYCdYo3E8WXujY=" },
2    2020-07-31 { "timestamp": "13. August 2020, 15:13", "keyCount": 1575, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Icn\/SxaXPAydSKjbN9coAU9Bgn\/nRVEeAfrmg1ic3\/4=" },
3    2020-08-01 { "timestamp": "13. August 2020, 15:13", "keyCount": 1405, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Vq9k1G0xEzO4zuBDCgt++HygT8Q2mqcZZ0972\/6MMKo=" },
4    2020-08-02 { "timestamp": "13. August 2020, 15:13", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
5    2020-08-03 { "timestamp": "13. August 2020, 15:13", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
6    2020-08-04 { "timestamp": "13. August 2020, 15:13", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
7    2020-08-05 { "timestamp": "13. August 2020, 15:13", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
8    2020-08-06 { "timestamp": "13. August 2020, 15:13", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
9    2020-08-07 { "timestamp": "13. August 2020, 15:13", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
A    2020-08-08 { "timestamp": "13. August 2020, 15:13", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
B    2020-08-09 { "timestamp": "13. August 2020, 15:13", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
C    2020-08-10 { "timestamp": "13. August 2020, 15:13", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
D    2020-08-11 { "timestamp": "13. August 2020, 15:13", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
E    2020-08-12 { "timestamp": "13. August 2020, 15:13", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-07-31 { "timestamp": "14. August 2020, 15:15", "keyCount": 1575, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Icn\/SxaXPAydSKjbN9coAU9Bgn\/nRVEeAfrmg1ic3\/4=" },
2    2020-08-01 { "timestamp": "14. August 2020, 15:15", "keyCount": 1405, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Vq9k1G0xEzO4zuBDCgt++HygT8Q2mqcZZ0972\/6MMKo=" },
3    2020-08-02 { "timestamp": "14. August 2020, 15:15", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
4    2020-08-03 { "timestamp": "14. August 2020, 15:15", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
5    2020-08-04 { "timestamp": "14. August 2020, 15:15", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
6    2020-08-05 { "timestamp": "14. August 2020, 15:15", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
7    2020-08-06 { "timestamp": "14. August 2020, 15:15", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
8    2020-08-07 { "timestamp": "14. August 2020, 15:15", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
9    2020-08-08 { "timestamp": "14. August 2020, 15:15", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
A    2020-08-09 { "timestamp": "14. August 2020, 15:15", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
B    2020-08-10 { "timestamp": "14. August 2020, 15:15", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
C    2020-08-11 { "timestamp": "14. August 2020, 15:15", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
D    2020-08-12 { "timestamp": "14. August 2020, 15:15", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
E    2020-08-13 { "timestamp": "14. August 2020, 15:15", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

     2020-08-01 { "timestamp": "15. August 2020, 09:57", "keyCount": 1405, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Vq9k1G0xEzO4zuBDCgt++HygT8Q2mqcZZ0972\/6MMKo=" },
     2020-08-02 { "timestamp": "15. August 2020, 09:57", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
     2020-08-03 { "timestamp": "15. August 2020, 09:57", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
     2020-08-04 { "timestamp": "15. August 2020, 09:57", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
     2020-08-05 { "timestamp": "15. August 2020, 09:57", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
     2020-08-06 { "timestamp": "15. August 2020, 09:57", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },

1    2020-08-01 { "timestamp": "15. August 2020, 15:29", "keyCount": 1405, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Vq9k1G0xEzO4zuBDCgt++HygT8Q2mqcZZ0972\/6MMKo=" },
2    2020-08-02 { "timestamp": "15. August 2020, 15:29", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
3    2020-08-03 { "timestamp": "15. August 2020, 15:29", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
4    2020-08-04 { "timestamp": "15. August 2020, 15:29", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
5    2020-08-05 { "timestamp": "15. August 2020, 15:29", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
6    2020-08-06 { "timestamp": "15. August 2020, 15:29", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
7    2020-08-07 { "timestamp": "15. August 2020, 15:29", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
8    2020-08-08 { "timestamp": "15. August 2020, 15:29", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
9    2020-08-09 { "timestamp": "15. August 2020, 15:29", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
A    2020-08-10 { "timestamp": "15. August 2020, 15:29", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
B    2020-08-11 { "timestamp": "15. August 2020, 15:29", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
C    2020-08-12 { "timestamp": "15. August 2020, 15:29", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
D    2020-08-13 { "timestamp": "15. August 2020, 15:29", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
E    2020-08-14 { "timestamp": "15. August 2020, 15:29", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

     2020-08-02 { "timestamp": "16. August 2020, 09:18", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
     2020-08-03 { "timestamp": "16. August 2020, 09:18", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
     2020-08-04 { "timestamp": "16. August 2020, 09:18", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
     2020-08-05 { "timestamp": "16. August 2020, 09:18", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
     2020-08-06 { "timestamp": "16. August 2020, 09:18", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
     2020-08-07 { "timestamp": "16. August 2020, 09:18", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },

1    2020-08-02 { "timestamp": "16. August 2020, 15:31", "keyCount": 1385, "matchesCount": 0, "appName": "Corona-Warn", "hash": "pzl9NwNk1xYSGCEOme6sAQNolM7lVSxdkr5kTDPToN0=" },
2    2020-08-03 { "timestamp": "16. August 2020, 15:31", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
3    2020-08-04 { "timestamp": "16. August 2020, 15:31", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
4    2020-08-05 { "timestamp": "16. August 2020, 15:31", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
5    2020-08-06 { "timestamp": "16. August 2020, 15:31", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
6    2020-08-07 { "timestamp": "16. August 2020, 15:31", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
7    2020-08-08 { "timestamp": "16. August 2020, 15:31", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
8    2020-08-09 { "timestamp": "16. August 2020, 15:31", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
9    2020-08-10 { "timestamp": "16. August 2020, 15:31", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
A    2020-08-11 { "timestamp": "16. August 2020, 15:31", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
B    2020-08-12 { "timestamp": "16. August 2020, 15:31", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
C    2020-08-13 { "timestamp": "16. August 2020, 15:31", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
D    2020-08-14 { "timestamp": "16. August 2020, 15:31", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
E    2020-08-15 { "timestamp": "16. August 2020, 15:31", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-03 { "timestamp": "17. August 2020, 13:00", "keyCount": 1645, "matchesCount": 0, "appName": "Corona-Warn", "hash": "gzYWx\/BxpliMJ8q1WoF\/X\/+CekMv6VFdn5LMdGgkE3E=" },
2    2020-08-04 { "timestamp": "17. August 2020, 13:00", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
3    2020-08-05 { "timestamp": "17. August 2020, 13:00", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
4    2020-08-06 { "timestamp": "17. August 2020, 13:00", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
5    2020-08-07 { "timestamp": "17. August 2020, 13:00", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
6    2020-08-08 { "timestamp": "17. August 2020, 13:00", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
7    2020-08-09 { "timestamp": "17. August 2020, 13:00", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
8    2020-08-10 { "timestamp": "17. August 2020, 13:00", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
9    2020-08-11 { "timestamp": "17. August 2020, 13:00", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
A    2020-08-12 { "timestamp": "17. August 2020, 13:02", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
B    2020-08-13 { "timestamp": "17. August 2020, 13:02", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
C    2020-08-14 { "timestamp": "17. August 2020, 13:02", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
D    2020-08-15 { "timestamp": "17. August 2020, 13:02", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
E    2020-08-16 { "timestamp": "17. August 2020, 13:02", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

     2020-08-04 { "timestamp": "18. August 2020, 09:28", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
     2020-08-05 { "timestamp": "18. August 2020, 09:28", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
     2020-08-06 { "timestamp": "18. August 2020, 09:28", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
     2020-08-07 { "timestamp": "18. August 2020, 09:28", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
     2020-08-08 { "timestamp": "18. August 2020, 09:28", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
     2020-08-09 { "timestamp": "18. August 2020, 09:28", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
     2020-08-10 { "timestamp": "18. August 2020, 09:28", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
     2020-08-11 { "timestamp": "18. August 2020, 09:28", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },

1    2020-08-04 { "timestamp": "18. August 2020, 15:33", "keyCount": 2813, "matchesCount": 0, "appName": "Corona-Warn", "hash": "\/BGlkC6K9rDVU\/o+\/hd\/5Y8nTIucL4zYWZznMdPZQDM=" },
2    2020-08-05 { "timestamp": "18. August 2020, 15:33", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
3    2020-08-06 { "timestamp": "18. August 2020, 15:33", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
4    2020-08-07 { "timestamp": "18. August 2020, 15:33", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
5    2020-08-08 { "timestamp": "18. August 2020, 15:33", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
6    2020-08-09 { "timestamp": "18. August 2020, 15:33", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
7    2020-08-10 { "timestamp": "18. August 2020, 15:33", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
8    2020-08-11 { "timestamp": "18. August 2020, 15:33", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
9    2020-08-12 { "timestamp": "18. August 2020, 15:33", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
A    2020-08-13 { "timestamp": "18. August 2020, 15:33", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
B    2020-08-14 { "timestamp": "18. August 2020, 15:33", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
C    2020-08-15 { "timestamp": "18. August 2020, 15:33", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
     2020-08-16 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<   

     ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-05 { "timestamp": "19. August 2020, 08:46", "keyCount": 2415, "matchesCount": 0, "appName": "Corona-Warn", "hash": "jJsXULhBwEOPWd6KJKdXxgcpPhQ1E4lbLevrI2X1\/8A=" },
2    2020-08-06 { "timestamp": "19. August 2020, 08:46", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
3    2020-08-07 { "timestamp": "19. August 2020, 08:46", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
4    2020-08-08 { "timestamp": "19. August 2020, 08:46", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
5    2020-08-09 { "timestamp": "19. August 2020, 08:46", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
6    2020-08-10 { "timestamp": "19. August 2020, 08:46", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
7    2020-08-11 { "timestamp": "19. August 2020, 08:46", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
8    2020-08-12 { "timestamp": "19. August 2020, 08:46", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
9    2020-08-13 { "timestamp": "19. August 2020, 08:46", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
A    2020-08-14 { "timestamp": "19. August 2020, 08:46", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
B    2020-08-15 { "timestamp": "19. August 2020, 08:46", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
C    2020-08-16 { "timestamp": "19. August 2020, 08:46", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
D    2020-08-17 { "timestamp": "19. August 2020, 08:46", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
E    2020-08-18 { "timestamp": "19. August 2020, 08:46", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-06 { "timestamp": "20. August 2020, 16:16", "keyCount": 3050, "matchesCount": 0, "appName": "Corona-Warn", "hash": "00VFOX48zqpjJBvjRtVdg6s\/XIuEFGSncBE4s+Azt1Y=" },
2    2020-08-07 { "timestamp": "20. August 2020, 16:16", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
3    2020-08-08 { "timestamp": "20. August 2020, 16:16", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
4    2020-08-09 { "timestamp": "20. August 2020, 16:16", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
5    2020-08-10 { "timestamp": "20. August 2020, 16:16", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
6    2020-08-11 { "timestamp": "20. August 2020, 16:16", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
7    2020-08-12 { "timestamp": "20. August 2020, 16:16", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
8    2020-08-13 { "timestamp": "20. August 2020, 16:16", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
9    2020-08-14 { "timestamp": "20. August 2020, 16:16", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
A    2020-08-15 { "timestamp": "20. August 2020, 16:16", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
B    2020-08-16 { "timestamp": "20. August 2020, 16:16", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
C    2020-08-17 { "timestamp": "20. August 2020, 16:16", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
D    2020-08-18 { "timestamp": "20. August 2020, 16:16", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
E    2020-08-19 { "timestamp": "20. August 2020, 16:18", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

     2020-08-07 { "timestamp": "21. August 2020, 09:00", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
     2020-08-08 { "timestamp": "21. August 2020, 09:00", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
     2020-08-09 { "timestamp": "21. August 2020, 09:00", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
     2020-08-10 { "timestamp": "21. August 2020, 09:00", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
     2020-08-11 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-12 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-13 { "timestamp": "21. August 2020, 09:00", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
     2020-08-14 { "timestamp": "21. August 2020, 09:00", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
     2020-08-15 { "timestamp": "21. August 2020, 09:00", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
     2020-08-16 { "timestamp": "21. August 2020, 09:00", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
     2020-08-17 { "timestamp": "21. August 2020, 09:00", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
     2020-08-18 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-19 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<   
     2020-08-20 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<   

1    2020-08-07 { "timestamp": "21. August 2020, 16:20", "keyCount": 2210, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Zqlj9HPKYuSuJywVkrLEX3re9Hobn+gs1321mIeIqiM=" },
2    2020-08-08 { "timestamp": "21. August 2020, 16:20", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
3    2020-08-09 { "timestamp": "21. August 2020, 16:20", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
4    2020-08-10 { "timestamp": "21. August 2020, 16:20", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
5    2020-08-11 { "timestamp": "21. August 2020, 16:20", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
6    2020-08-12 { "timestamp": "21. August 2020, 16:20", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
7    2020-08-13 { "timestamp": "21. August 2020, 16:20", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
8    2020-08-14 { "timestamp": "21. August 2020, 16:20", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
9    2020-08-15 { "timestamp": "21. August 2020, 16:20", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
A    2020-08-16 { "timestamp": "21. August 2020, 16:20", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
B    2020-08-17 { "timestamp": "21. August 2020, 16:20", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
     2020-08-18 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-19 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<   
     2020-08-20 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<   

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-08 { "timestamp": "22. August 2020, 16:19", "keyCount": 1655, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JsjhbWbw\/BZ5vPmpcYMzev2FTNcr9JOOxDst9M6u5fI=" },
2    2020-08-09 { "timestamp": "22. August 2020, 16:19", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
3    2020-08-10 { "timestamp": "22. August 2020, 16:19", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
4    2020-08-11 { "timestamp": "22. August 2020, 16:19", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
5    2020-08-12 { "timestamp": "22. August 2020, 16:19", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
6    2020-08-13 { "timestamp": "22. August 2020, 16:19", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
7    2020-08-14 { "timestamp": "22. August 2020, 16:19", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
8    2020-08-15 { "timestamp": "22. August 2020, 16:19", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
9    2020-08-16 { "timestamp": "22. August 2020, 16:19", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
A    2020-08-17 { "timestamp": "22. August 2020, 16:19", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
B    2020-08-18 { "timestamp": "22. August 2020, 16:19", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
C    2020-08-19 { "timestamp": "22. August 2020, 16:19", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
D    2020-08-20 { "timestamp": "22. August 2020, 16:19", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
E    2020-08-21 { "timestamp": "22. August 2020, 16:19", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-09 { "timestamp": "23. August 2020, 09:19", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
2    2020-08-10 { "timestamp": "23. August 2020, 09:19", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
3    2020-08-11 { "timestamp": "23. August 2020, 09:19", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
4    2020-08-12 { "timestamp": "23. August 2020, 09:19", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
5    2020-08-13 { "timestamp": "23. August 2020, 09:19", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
6    2020-08-14 { "timestamp": "23. August 2020, 09:19", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
7    2020-08-15 { "timestamp": "23. August 2020, 09:19", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
8    2020-08-16 { "timestamp": "23. August 2020, 09:19", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
9    2020-08-17 { "timestamp": "23. August 2020, 09:19", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
A    2020-08-18 { "timestamp": "23. August 2020, 09:19", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
B    2020-08-19 { "timestamp": "23. August 2020, 09:19", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
C    2020-08-20 { "timestamp": "23. August 2020, 09:19", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
D    2020-08-21 { "timestamp": "23. August 2020, 09:19", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
E    2020-08-22 { "timestamp": "23. August 2020, 09:19", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },

?    2020-08-09 { "timestamp": "23. August 2020, 16:19", "keyCount": 0565, "matchesCount": 0, "appName": "Corona-Warn", "hash": "9ySZZ6kFhIpBqlbEuZvvxaR2P4hjX\/qJyXJWdSGH\/ow=" },
?    2020-08-12 { "timestamp": "23. August 2020, 16:19", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
?    2020-08-13 { "timestamp": "23. August 2020, 16:19", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
?    2020-08-15 { "timestamp": "23. August 2020, 16:19", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
?    2020-08-19 { "timestamp": "23. August 2020, 16:19", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
?    2020-08-21 { "timestamp": "23. August 2020, 16:19", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-10 { "timestamp": "24. August 2020, 09:32", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
2    2020-08-11 { "timestamp": "24. August 2020, 09:32", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
3    2020-08-12 { "timestamp": "24. August 2020, 09:32", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
4    2020-08-13 { "timestamp": "24. August 2020, 09:32", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
5    2020-08-14 { "timestamp": "24. August 2020, 09:32", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
6    2020-08-15 { "timestamp": "24. August 2020, 09:32", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
     2020-08-16 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
9    2020-08-18 { "timestamp": "24. August 2020, 09:32", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
     2020-08-19 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
B    2020-08-20 { "timestamp": "24. August 2020, 09:32", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
C    2020-08-21 { "timestamp": "24. August 2020, 09:32", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
D    2020-08-22 { "timestamp": "24. August 2020, 09:32", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
E    2020-08-23 { "timestamp": "24. August 2020, 09:32", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },

1    2020-08-10 { "timestamp": "24. August 2020, 16:23", "keyCount": 2380, "matchesCount": 0, "appName": "Corona-Warn", "hash": "JUqtJgYkSpsO6UjX9SnO+C6w1518Rna9Ay1y1HeQtcQ=" },
2    2020-08-11 { "timestamp": "24. August 2020, 16:23", "keyCount": 2285, "matchesCount": 0, "appName": "Corona-Warn", "hash": "oY6Abxzv9ZQ6k6GtQFcoYgnlm3swzWJ9v2ldXeXqW8I=" },
3    2020-08-12 { "timestamp": "24. August 2020, 16:23", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
4    2020-08-13 { "timestamp": "24. August 2020, 16:23", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
5    2020-08-14 { "timestamp": "24. August 2020, 16:23", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
     2020-08-15 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-16 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
9    2020-08-18 { "timestamp": "24. August 2020, 16:23", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
     2020-08-19 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
B    2020-08-20 { "timestamp": "24. August 2020, 16:23", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
C    2020-08-21 { "timestamp": "24. August 2020, 16:23", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
D    2020-08-22 { "timestamp": "24. August 2020, 16:23", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
     2020-08-23 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

     2020-08-11 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-12 { "timestamp": "25. August 2020, 09:29", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
     2020-08-13 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-14 { "timestamp": "25. August 2020, 09:29", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
     2020-08-15 { "timestamp": "25. August 2020, 09:29", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
     2020-08-16 { "timestamp": "25. August 2020, 09:29", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
     2020-08-17 { "timestamp": "25. August 2020, 09:29", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
     2020-08-18 { "timestamp": "25. August 2020, 09:29", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
     2020-08-19 { "timestamp": "25. August 2020, 09:29", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
     2020-08-20 { "timestamp": "25. August 2020, 09:29", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
     2020-08-21 { "timestamp": "25. August 2020, 09:29", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
     2020-08-22 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-23 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-24 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<

     2020-08-11 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
2    2020-08-12 { "timestamp": "25. August 2020, 12:33", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
3    2020-08-13 { "timestamp": "25. August 2020, 12:33", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
4    2020-08-14 { "timestamp": "25. August 2020, 12:33", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
5    2020-08-15 { "timestamp": "25. August 2020, 12:33", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
6    2020-08-16 { "timestamp": "25. August 2020, 12:33", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
7    2020-08-17 { "timestamp": "25. August 2020, 12:33", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
8    2020-08-18 { "timestamp": "25. August 2020, 12:33", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
9    2020-08-19 { "timestamp": "25. August 2020, 12:33", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
A    2020-08-20 { "timestamp": "25. August 2020, 12:33", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
B    2020-08-21 { "timestamp": "25. August 2020, 12:33", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
     2020-08-22 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-23 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
E    2020-08-24 { "timestamp": "25. August 2020, 12:33", "keyCount": 3165, "matchesCount": 1, "appName": "Corona-Warn", "hash": "E9\/3fPP1VumROWc8ld+ekBISji7vVM4Fa8tUsZVVOmg=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-12 { "timestamp": "26. August 2020, 09:53", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
2    2020-08-13 { "timestamp": "26. August 2020, 09:53", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
3    2020-08-14 { "timestamp": "26. August 2020, 09:53", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" }
4    2020-08-15 { "timestamp": "26. August 2020, 09:53", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
5    2020-08-16 { "timestamp": "26. August 2020, 09:53", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
6    2020-08-17 { "timestamp": "26. August 2020, 09:53", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
     2020-08-18 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
8    2020-08-19 { "timestamp": "26. August 2020, 09:53", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
     2020-08-20 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
A    2020-08-21 { "timestamp": "26. August 2020, 09:53", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
B    2020-08-22 { "timestamp": "26. August 2020, 09:53", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
C    2020-08-23 { "timestamp": "26. August 2020, 09:53", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },
D    2020-08-24 { "timestamp": "26. August 2020, 09:53", "keyCount": 3165, "matchesCount": 1, "appName": "Corona-Warn", "hash": "E9\/3fPP1VumROWc8ld+ekBISji7vVM4Fa8tUsZVVOmg=" },
E    2020-08-25 { "timestamp": "26. August 2020, 09:53", "keyCount": 4156, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Jewqu2GeA+rVtTyAJjqaUE+8qYCBf+0avAxPWRNzFMc=" },

1    2020-08-12 { "timestamp": "26. August 2020, 09:55", "keyCount": 3800, "matchesCount": 0, "appName": "Corona-Warn", "hash": "O9EDIHgcHnHYRK14fHtfO\/NPyawZ7k3bhav2c2ss++s=" },
2    2020-08-13 { "timestamp": "26. August 2020, 09:55", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
     2020-08-14 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-15 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
5    2020-08-16 { "timestamp": "26. August 2020, 09:55", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-18 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
8    2020-08-19 { "timestamp": "26. August 2020, 09:55", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
9    2020-08-20 { "timestamp": "26. August 2020, 09:55", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
A    2020-08-21 { "timestamp": "26. August 2020, 09:55", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
B    2020-08-22 { "timestamp": "26. August 2020, 09:55", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
C    2020-08-23 { "timestamp": "26. August 2020, 09:55", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },
     2020-08-24 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-25 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

     2020-08-13 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-14 { "timestamp": "27. August 2020, 08:54", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
     2020-08-15 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-16 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-18 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-19 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-20 { "timestamp": "27. August 2020, 08:54", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
     2020-08-21 { "timestamp": "27. August 2020, 08:54", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
     2020-08-22 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-23 { "timestamp": "27. August 2020, 08:54", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },
     2020-08-24 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-25 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-26 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<


1    2020-08-13 { "timestamp": "27. August 2020, 08:54", "keyCount": 3940, "matchesCount": 0, "appName": "Corona-Warn", "hash": "mDTgBack7CLecOLMQ+Oi1Km47u++WBnbgQbbwoLjF0c=" },
2    2020-08-14 { "timestamp": "27. August 2020, 08:54", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
3    2020-08-15 { "timestamp": "27. August 2020, 08:54", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
4    2020-08-16 { "timestamp": "27. August 2020, 08:54", "keyCount": 1790, "matchesCount": 0, "appName": "Corona-Warn", "hash": "booypFvg7FHjJaXzqOe1uaSzp2byyy33MnRqvb3\/A\/A=" },
5    2020-08-17 { "timestamp": "27. August 2020, 08:54", "keyCount": 2785, "matchesCount": 0, "appName": "Corona-Warn", "hash": "PME9jnNe74+zeEXwwhL6lHIwA0LgI3CtiyH7cgDw8KI=" },
6    2020-08-18 { "timestamp": "27. August 2020, 08:54", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
7    2020-08-19 { "timestamp": "27. August 2020, 08:54", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
8    2020-08-20 { "timestamp": "27. August 2020, 08:54", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
9    2020-08-21 { "timestamp": "27. August 2020, 08:54", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
A    2020-08-22 { "timestamp": "27. August 2020, 08:54", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
B    2020-08-23 { "timestamp": "27. August 2020, 08:54", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },
C    2020-08-24 { "timestamp": "27. August 2020, 08:54", "keyCount": 3165, "matchesCount": 1, "appName": "Corona-Warn", "hash": "E9\/3fPP1VumROWc8ld+ekBISji7vVM4Fa8tUsZVVOmg=" },
D    2020-08-25 { "timestamp": "27. August 2020, 08:54", "keyCount": 4156, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Jewqu2GeA+rVtTyAJjqaUE+8qYCBf+0avAxPWRNzFMc=" },
E    2020-08-26 { "timestamp": "27. August 2020, 08:54", "keyCount": 4410, "matchesCount": 0, "appName": "Corona-Warn", "hash": "TG79SmqoROuKhHWCKocEOoqUGylj3YX+JVcaef\/oH58=" },

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1    2020-08-14 { "timestamp": "28. August 2020, 09:20", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
2    2020-08-15 { "timestamp": "28. August 2020, 09:20", "keyCount": 2675, "matchesCount": 0, "appName": "Corona-Warn", "hash": "GBcCZg9QMzBbNuNPAUMi0dduyGzzeOrx9uNqrdiJLYk=" },
     2020-08-16 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
5    2020-08-18 { "timestamp": "28. August 2020, 09:20", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
9    2020-08-19 { "timestamp": "28. August 2020, 09:20", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
7    2020-08-20 { "timestamp": "28. August 2020, 09:20", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
8    2020-08-21 { "timestamp": "28. August 2020, 09:20", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
9    2020-08-22 { "timestamp": "28. August 2020, 09:20", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
A    2020-08-23 { "timestamp": "28. August 2020, 09:20", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },
B    2020-08-24 { "timestamp": "28. August 2020, 09:20", "keyCount": 3165, "matchesCount": 1, "appName": "Corona-Warn", "hash": "E9\/3fPP1VumROWc8ld+ekBISji7vVM4Fa8tUsZVVOmg=" },
C    2020-08-25 { "timestamp": "28. August 2020, 09:20", "keyCount": 4156, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Jewqu2GeA+rVtTyAJjqaUE+8qYCBf+0avAxPWRNzFMc=" },
D    2020-08-26 { "timestamp": "28. August 2020, 09:20", "keyCount": 4410, "matchesCount": 0, "appName": "Corona-Warn", "hash": "TG79SmqoROuKhHWCKocEOoqUGylj3YX+JVcaef\/oH58=" },
     2020-08-27 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<

     2020-08-14 { "timestamp": "28. August 2020, 09:20", "keyCount": 3020, "matchesCount": 0, "appName": "Corona-Warn", "hash": "wqu9Lt\/gthQrJ2dy3HgnlwvafRxdsKKbs7kyQWjK\/aI=" },
     2020-08-15 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-16 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-17 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-18 { "timestamp": "28. August 2020, 09:20", "keyCount": 3749, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Q71tl1xX2vOOpXCXXD4Nbb59n3UOoyQ6+EqlUgMaLYE=" },
     2020-08-19 { "timestamp": "28. August 2020, 09:20", "keyCount": 3970, "matchesCount": 0, "appName": "Corona-Warn", "hash": "j5X5KZl49Z6TjPij64zo33ZRiDWkXubkMlD5wg6Ga90=" },
     2020-08-20 { "timestamp": "28. August 2020, 09:20", "keyCount": 4740, "matchesCount": 0, "appName": "Corona-Warn", "hash": "MyxqsqBxRQqp7KXS1jP\/Xfr40hbcFhkb7ssAnlUIA5s=" },
     2020-08-21 { "timestamp": "28. August 2020, 09:20", "keyCount": 3550, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Dn2IhRyGtT+QVK7pqXiojVhDnmOM2G17NLw9VZi7Ovw=" },
     2020-08-22 { "timestamp": "28. August 2020, 09:20", "keyCount": 3393, "matchesCount": 0, "appName": "Corona-Warn", "hash": "fXS+VRiOZt9yK5fnwYIqpomT6sy\/Wx+FJvdq5NAyBpY=" },
     2020-08-23 { "timestamp": "28. August 2020, 09:20", "keyCount": 2535, "matchesCount": 0, "appName": "Corona-Warn", "hash": "tJ5DISc2xYrTCEEWjGyMDZ\/4\/OD7kcsEEcE0j66uwHs=" },
     2020-08-24 { "timestamp": "28. August 2020, 09:20", "keyCount": 3165, "matchesCount": 1, "appName": "Corona-Warn", "hash": "E9\/3fPP1VumROWc8ld+ekBISji7vVM4Fa8tUsZVVOmg=" },
     2020-08-25 { "timestamp": "28. August 2020, 09:20", "keyCount": 4156, "matchesCount": 0, "appName": "Corona-Warn", "hash": "Jewqu2GeA+rVtTyAJjqaUE+8qYCBf+0avAxPWRNzFMc=" },
     2020-08-26 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<
     2020-08-27 <<<<<<<<<<<<<<<<<<<<<<<<< missing <<<<<<<

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Tho-Mat on 29 Aug 2020

👀1

Hi,

same bug here. Appears every 3 or 4 days at the latest.

Android 9
Cat S61
CWA 1.2.1

I normally switch off my phone during the night and I normally switch off Bluetooth and GPS when not outside my flat.
If any details would help you solving the problem, please tell me. And tell me how to do it, because I am quite clueless offside the paths of a UI.

Neuwessi11 on 29 Aug 2020

My issue described in this comment resolved itself today. A minute ago, I have opened the app again, and everything has returned to normal 🤷‍♂️

The error came back for me today :-(
I didn't detect it first because my status is still "green".
grafik
But when I saw that the today's update was missing, I tapped on the right-arrow on the top right corner, and it returned a cause 3 / 39508 pop-up.
Since then, the error pop-up shows up immediately whenever I open the app.

Edit: fixed itself the next day.

NKarolak on 30 Aug 2020

👀1

@Tho-Mat & @NKarolak
Same for me on
Samsung Galaxy A5 (2017) SM-A520F
Android 8.0.0
ENF 16203314000
CWA 1.2.1

ApiException: 39508

CWA first showed
Updated: Yesterday, 5:46 AM
then CAUSE: 3 Something went wrong

The device was unattended and not connected to a charger until I unlocked it and opened CWA at around 11:30 today.
Looking at the .json file all-exposure-checks 2020 08 30.zip from "Export exposure checks" there are 9 records from 07:43 today, followed by 11 records from 11:36 today. 9+11 = 20 which is the quota limit for provideDiagnosisKeys in V1 mode listed in the Architecture section of the Exposure Notification system documentation.

All 9 hashes which were used in the first attempt at 07:43 were repeated in the second attempt at 11:36, plus another 2, making 11 which reached the quota of 20.

It's not clear why only 9 attempts were made at the first attempt at 07:43 instead of 14. I suspect doze mode interference but I have no proof of that.
The question is why on the second attempt at 11:36 the 9 results from 07:43 were not cached and used in the risk calculation. CWA could have just submitted the missing 5 (14-9) hashes to get the complete 14 days without exceeding the quota.

Is this a change which could be made to CWA so that it doesn't try to repeat calls related to the same hash value which have already been used on that day?

MikeMcC399 on 30 Aug 2020

👍4

I just got some insights from the development team.

Due to the watchdog implementation from Google, it could happen that the key retrieval was called twice, normally the function startWithConstraints should catch this and execute it only the first time. But due to some unclarity regarding the timezones, the constraints were wrong and so a second call was executed which caused in the 39508 error as the rate limit was reached (14 packages + 14 packages > 20 API limit). That was fixed in #1041.

To be more reliable we also changed the approach of how we submit the packages to the API, instead of submitting 14 packages we now only submit one file containing all 14 packages. That's only possible in version 1.5 of the Google ENF so we had to wait until this was rolled out to all users. That means if the transaction will be executed twice a day (which shouldn't happen due to the change in #1041) you would have 20 tries instead of 1,4.

See the following pull requests that address the issues:
Pull request: https://github.com/corona-warn-app/cwa-app-android/pull/1088
Pull request: https://github.com/corona-warn-app/cwa-app-android/pull/1041

Best regards,
SG

Corona-Warn-App Open Source Team

svengabr on 31 Aug 2020

❤2 👍2 🚀1

@svengabr thanks for the update, but how it had to do anything with the timezones? There might be some ambiguity between 22.00 and 02.00 (22.00 UTC is midnight local time, and 02.00 local time is midnight UTC), but errors reported here were happening at times when there is no ambiguity, so both previous and fixed implementation from #1041 return exactly the same results.

As an example from the first post here: call to provideDiagnosisKeys happened at 07:36 and then 09:36 local time. This corresponds to 05:36 and 07:36 UTC. startWithConstraints should prevent this, even with the implementation assuming UTC time, as this is the same UTC day.

I think we still don't know what is the root cause here, but agree that #1088 will alleviate this problem, as background job would have to fail 20 times to produce 39508 error, instead of only once.

kbobrowski on 31 Aug 2020

👍2

@svengabr thanks for the detailed feedback 🙂

That's only possible in version 1.5 of the Google ENF so we had to wait until this was rolled out to all users.

Does this mean you're fully switching (Android) CWA over to use ENF 1.5 (ExposureWindow mode)? If so: maybe you could give some updates what this switch entails over in this issue? 🙂

Btw: is this currently targeted for the next CWA release (1.3) or for later?

daimpi on 31 Aug 2020

some v1.5 features are also available in v1 mode (as passing multiple batches), so this change could be done independently from switching to exposure window mode

kbobrowski on 31 Aug 2020

👍2

Android 6, CWA 1.3.0, ENF 16203302004, no "Priorisierte Hintergrundaktivität"

When I opened the CWA today it said "Prüfung läuft ..." and "Aktualisiert: Gestern ..." as in Issue 1024.
When I came back after some minutes the display had turned dark and after reactivating, the CWA said "Prüfung läuft ..." again and then showed the Error 30508.
In the log there is one successful check at 09:24 and six more entries at 09:27.

{"timestamp":"7. September 2020, 09:27","keyCount":3165,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:27","keyCount":6285,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:27","keyCount":5310,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:27","keyCount":2158,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:27","keyCount":3000,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:27","keyCount":2245,"matchesCount":0,"appName":"Corona-

{"timestamp":"7. September 2020, 09:24","keyCount":3165,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":5310,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":4835,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":4156,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":3000,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":2245,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":4410,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":6285,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":6685,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":3339,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":6095,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":5435,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":4460,"matchesCount":0,"appName":"Corona-
{"timestamp":"7. September 2020, 09:24","keyCount":2158,"matchesCount":0,"appName":"Corona-

all-exposure-checks_20200907.txt

So I guess, the CWA did not know about the successful check and triggered a new one, which lead to the error.

kereng5 on 7 Sep 2020

Hi @kbobrowski , FYI: QuotaCalculator is coming up #1108

@tkowark thanks for resolving 404, do you have some plan on resolving 39508 in this case? it's difficult to find the root cause, but following implementation improvements should mitigate it:
* count number of calls to `provideDiagnosisKeys` before each call

* keep track of which files were submitted successfully, and in case of unexpected transaction termination - retry only with not-submitted files

* record logs of any errors and make them available to the user, to eliminate root cause of issues

* try to submit most relevant (most recent) files first
With these features implemented the worst case scenario is that the call to provideDiagnosisKeys may fail with GMS still counting this call towards the quota. But it will not lead to 39508 since we are counting all the calls before executing (first point). In the worst case it may result it not all the 14 files submitted in one day, but there are 6 extra tries available, so almost certainly it won't be the problem. And even if transaction would fail 6 times in a day, files are submitted from most relevant to least relevant, so it would have insignificant impact on quality of predicted exposure status.

I think that basically transaction should be designed with the assumption that it can abruptly terminate at any stage. Right now there is an assumption that once transaction starts (and successfully downloads all files) it will successfully submit all files to ENF and then successfully update "time of last transaction execution" value, which as we can see now might not be the case.

vaubaehn on 7 Sep 2020

👍2

Did the same today as yesterday but no error message this time. So I have no idea way the exposure check was restarted yesterday at 9:27 after it had written 14 lines into the log at 9:24.

kereng5 on 8 Sep 2020

I also had this issue (CAUSE: 3 Something went wrong. ApiException: 39508) for the first time today (11.09) at around 01:30. When opening CWA I was greeted with the familiar error screen

And after dismissing this message the main screen was showing that the last check performed happened two days ago

while my ENF log shows that CWA tried to perform checks one day ago:

Which is exactly what happened:

CWA tried to perform checks on Sept 10th first at 02:32 (9 checks performed) and then again at 03:03 (11 checks performed) at which point it must have hit the rate limit of 20. It could be that my phone was on battery saving mode at those times b/c my battery might have been low and I've otherwise manually disabled all battery savings in my phone, but I'm not sure tbh.

When I checked CWA again approx 1h later today (11th September, 02:30) the error was gone and a successful sync was performed at 02:03 . The limit was probably reset at 00:00 UTC/02:00 CEST.

My device:
Samsung Galaxy S8 (Android 9)
CWA 1.3.0
ENF v. 16203315000

My ENF log: me-11.zip

daimpi on 11 Sep 2020

The issue came back for me today after I switched off the phone during night.

@svengabr in https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-683748329 you wrote:

See the following pull requests that address the issues:
Pull request: #1088
Pull request: #1041

1088 is listed in the changelog for `1.4.0-SNAPSHOT-RC1`, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA `1.4.0` ?

pathmapper on 13 Sep 2020

Just a short update from my side: the issue seems to be solved since having updated to version 1.3.0.

NKarolak on 13 Sep 2020

Today data update worked out without doing anything. No app update, no restart of phone...
The error disappeared.

DK1979 on 13 Sep 2020

@pathmapper

1088 is listed in the changelog for 1.4.0-SNAPSHOT-RC1, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA 1.4.0 ?

1041 has been reverted (in #1107) b/c there seemingly has been miscommunication by Google. It turns out, the correct time to use is UTC after all. This has since been rectified in the Google documentation as well:

grafik

daimpi on 13 Sep 2020

👍1

@DK1979

Today data update worked out without doing anything. No app update, no restart of phone...
The error disappeared.

Yes, that makes sense as the limits are reset at 00:00 UTC. The same happened to me:

When I checked CWA again approx 1h later today (11th September, 02:30) the error was gone and a successful sync was performed at 02:03 . The limit was probably reset at 00:00 UTC/02:00 CEST.

daimpi on 13 Sep 2020

Risiko-Ermittlung nicht möglich
Aktualisiert: 13. Sep., 02:19

URSACHE: 3
Etwas ist schiefgelaufen.
[...] (39508)

Wenn die App mehr als drei Tage lang den Risikostatus nicht ermitteln kann, verliert sie für mich irgendwann ihre Funktionalität, auf deutsch: ist sinnlos.

Gibt es denn für das Problem inzwischen Lösungsansätze? Wird seitens Telekom oder SAP dran gearbeitet?

Neuwessi11 on 16 Sep 2020

Wir werden in den nächsten Tag die Version 1.3.1 veröffentlichen die das Problem für die meisten lösen wird.

thomasaugsten on 16 Sep 2020

Das klingt toll!
Guter Hoffnung vielen Dank für die schnelle Antwort!

Neuwessi11 on 16 Sep 2020

@Neuwessi11
Was für ein Gerät hast du denn und mit welcher Android und CWA Version?

Dieser Fehler ist ein rate-limiting Error, also im Endeffekt hat die App heute bereits zu häufig versucht auf ein bestimmte API Funktion zuzugreifen. Was da normalerweise hilft: App beenden -> 24h warten -> App wieder öffnen, das limit wird nämlich jeden Tag wieder zurückgesetzt.

(Streng genommen musst du keine 24h warten, da das Limit jeden Tag um 02:00 Uhr CEST (=0 Uhr UTC) zurückgesetzt wird, sollte es reichen bis zu dem Zeitpunkt zu warten.)

Zu den fixes: Es sieht danach aus, dass wir mit Version 1.4 einen nachhaltigen fix bekommen: https://github.com/corona-warn-app/cwa-app-android/pull/1150 🙂.

daimpi on 16 Sep 2020

CAT S61
Android 9
CWA 1.3.0

Vielleicht ist ein Teil des Problems, dass mein Telefon oftmals um 2.00 Uhr ausgeschaltet ist. Ist es möglich, dass dann der Zähler nicht zurückgesetzt wird?

Aber ich werde jetzt erst einmal hoffnungsvoll gestimmt auf das nächste Update warten und sehen, was passiert.

Neuwessi11 on 16 Sep 2020

@Neuwessi11 thanks für die Info 🙂.

Vielleicht ist ein Teil des Problems, dass mein Telefon oftmals um 2.00 Uhr ausgeschaltet ist. Ist es möglich, dass dann der Zähler nicht zurückgesetzt wird?

Das mit dem Ausschalten könnte tatsächlich ein Problem sein, ich glaube ich habe das in dem Zusammenhang schon mal gelesen. Aber ich wüsste ehrlich gesagt nicht genau wie das vonstatten geht… denn eigentlich sollte der reset ja trotzdem stattfinden…

Vll. kannst du heute Nacht dein Gerät mal an lassen und schauen ob der Fehler morgen verschwunden ist?

daimpi on 16 Sep 2020

@thomasaugsten

Wir werden in den nächsten Tag die Version 1.3.1 veröffentlichen die das Problem für die meisten lösen wird.

Ich weiß nicht, ob der 1.3.1 fix tatsächlich @Neuwessi11's Problem beheben wird, da es bei ihm ja scheinbar nicht nur darum geht, dass der 39508 Fehler angezeigt wird, sondern dass die App scheinbar selbst an den darauffolgenden Tagen aus irgendwelchen Gründen das rate limit erreicht und abbricht und der Risikostatus deswegen nicht aktualisiert wird:

Wenn die App mehr als drei Tage lang den Risikostatus nicht ermitteln kann, verliert sie für mich irgendwann ihre Funktionalität, auf deutsch: ist sinnlos.

@vaubaehn hat das hier ja bereits ganz gut zusammengefasst:

The much more severe current problem is, that ProvideDiagnosisKeys() may also fail, most likely because of internal timeout for an unknown reason (slow phone, too much file operation when shifting data from app to ENF when performing 14 single calls, concurrent processes, i.e. during reboot/start-up of the phone, etc...). Most of the people, who experienced API39508 will have had a problem with timeout in any way. While the hotfix in version 1.3.1 will take account of it, in the way, that ProvideDiagnosisKeys() won't be called again by CWA in the same day after a file batch has been sent, background updates may still fail.
[…]

daimpi on 16 Sep 2020

👍1

Hi @Neuwessi11 ,

Vielleicht ist ein Teil des Problems, dass mein Telefon oftmals um 2.00 Uhr ausgeschaltet ist. Ist es möglich, dass dann der Zähler nicht zurückgesetzt wird?

ich bin mir ziemlich sicher, dass das ein Teil des Problems ist, aber etwas anders als gedacht...

Klar, wenn das Telefon ausgeschaltet ist, kann der Zähler nicht zurück gesetzt werden. Das Zurücksetzen passiert dann aber, sobald das Telefon wieder seine Arbeit aufnimmt, morgens beim Einschalten.
Ich glaube, dass mit dem Einschalten das Problem beginnt: Sobald die Google Play Services (da steckt ja Googles Exposure Notification Framework drin) ihre Arbeit aufnehmen, schicken sie auch an die Corona-Warn-App das Signal, wieder aufzuwachen, und auf mögliche Risiko-Begegnungen zu prüfen.
In diesem Augenblick fährt das Telefon aber immer noch hoch, viele Datei-Operationen werden ausgeführt, viele Prozesse gestartet - das kostet alles Rechenleistung und Geschwindigkeit. Wenn in diesem Tumult nun die Corona-Warn-App auch noch anfängt, die Daten für die Risiko-Ermittlung vom Telekom-Server herunter zu laden, und danach an die Google Play Services zur Überprüfung zu übergeben, kann es sein, dass es hier zu einem Timeout (einer zu langen Verzögerung bei der Bearbeitung) kommt, und die Risiko-Ermittlung stumm abgebrochen wird.
In der Regel kann man das daran erkennen, dass in dem Überprüfungsprotokoll (Android > Einstellungen > Google > Covid-19-Benachrichtigunen > Überprüfungen auf mögliche Begegnungen) für den betreffenden Tag für die Uhrzeit des Einschaltens des Telefons nur wenige Einträge (weniger als 14) zu finden sind. Wird die Risiko-Ermittlung zu einem späteren Zeitpunkt am Tag erneut gestartet, schlägt sie erneut fehl, weil nicht mehr erneut für 14 Tage an die Google-Schnittstelle Daten übergeben werden dürfen (Google API rate limit). Wenn die Corona-Warn-App dabei von dir geöffnet wurde, erscheint dann die Fehlermeldung API39508.

Mit der Version 1.4.0 der Warn-App können wir hoffen, dass eine veränderte Funktion eingeführt wird, wie die Daten an die Google-Schnittstelle übergeben werden. Das senkt zumindest das Risiko, dass es hierbei zu einem Timeout kommt. Ob die neue Weise der Daten-Übergabe den Timeout künftig ganz verhindern kann, ist abzuwarten.

Für mich ist recht deutlich, dass Google hier nochmal nacharbeiten müsste, um einen Timeout innerhalb des Exposure Notification Framework (ENF) zu verhindern (=> @thomasaugsten ), falls das nicht bereits geschehen ist, und wir einen Fix mit einer neuen Version des ENF bald erhalten.
Wo ich mir unsicher bin, ist, ob die Warn-App so programmiert werden kann, dass sie, nachdem sie für die Risiko-Ermittlung im Hintergrund 'geweckt' wurde, lieber noch etwas abwartet (z. B. 120 Sekunden), bevor sie mit der Datenübergabe an die Google-Schnittstelle beginnt, damit sich das Telefon nach einem Neustart erst wieder ein bisschen beruhigen kann, und die Bahn für die rechenleistungsintensiven Prozesse der Risiko-Ermittlung frei ist (=> @thomasaugsten ). Wenn die Warn-App zulange wartet, besteht nämlich wieder die Gefahr, dass sie von der Akku-Optimierung des Telefons einfach wieder geschlossen wird.
Es ist nicht einfach...

Allgemeine Tipps, bis wir Verbesserungen der Corona-Warn-App und des Exposure Notification Frameworks erhalten:

Überprüfen, wann normalerweise die automatische Aktualisierung im Hintergrund stattfindet, z. B. durch Überprüfung der Protokolle der Begegnungsüberprüfung: Android > Einstellungen > Google > Covid-19-Benachrichtigunen > Überprüfungen auf mögliche Begegnungen
Zu der Zeit, wenn die Hintergrundaktualisierung stattfindet, das Telefon möglichst am Ladegerät haben. Bei mir ist das nachts.
Falls das Telefon eingeschaltet wird, lieber ein paar Minuten abwarten, bevor die Corona-Warn-App geöffnet wird.
Auch wenn die Hintergrundaktualisierung zunächst regelmäßig und gut funktioniert, macht es Sinn, die App alle 1-2 Tage zu öffnen. Wird sie nämlich längere Zeit nicht geöffnet, kann es sein, dass sie vom Betriebssystem automatisch als weniger wichtig eingestuft wird (rare bucket => @thomasaugsten ), und Hintergrundprozesse nur noch sehr selten oder gar nicht mehr ausgeführt werden können, selbst wenn sie eigentlich von Google's Weck-Service (wake up service) geweckt wurde.

Hoffe, das hilft ein bisschen.

vaubaehn on 17 Sep 2020

👍2

Oh ja, vielen Dank, das hilft schon mal sehr, denke ich!

Überprüfen, wann normalerweise die automatische Aktualisierung im Hintergrund stattfindet,

Wenn ich lange wach bin oder das Telefon über Nacht an lasse, zwischen 2 und 3 Uhr. Sonst beim Anschalten.

Zu der Zeit, wenn die Hintergrundaktualisierung stattfindet, das Telefon möglichst am Ladegerät haben.

Das bringt doch aber nur etwas, wenn es dann nicht ausgeschaltet ist, richtig? Würde mir, der ich es ganz altmodisch gerne ausschalten möchte, nicht so viel bringen?

Falls das Telefon eingeschaltet wird, lieber ein paar Minuten abwarten, bevor die Corona-Warn-App geöffnet wird.

Das habe ich schon probiert. Hat nichts oder nicht immer etwas gebracht.

Neuwessi11 on 17 Sep 2020

Wenn in diesem Tumult nun die Corona-Warn-App auch noch anfängt, die Daten für die Risiko-Ermittlung vom
Telekom-Server herunter zu laden, und danach an die Google Play Services zur Überprüfung zu übergeben, kann es sein, dass
es hier zu einem Timeout (einer zu langen Verzögerung bei der Bearbeitung) kommt, und die Risiko-Ermittlung stumm
abgebrochen wird.
In der Regel kann man das daran erkennen, dass in dem Überprüfungsprotokoll (Android > Einstellungen > Google >
Covid-19-Benachrichtigunen > Überprüfungen auf mögliche Begegnungen) für den betreffenden Tag für die Uhrzeit des
Einschaltens des Telefons nur wenige Einträge (weniger als 14) zu finden sind.

Da habe ich gerade mal nachgesehen. Für die letzten drei Tage (an denen der Fehler aufgetreten ist) waren da jeweils 20 Einträge. Wenn ich auf die Details gehe, wird mir die Uhrzeit, die Anzahl der Schlüssel (einige tausend), die Anzahl der Treffer, die App und ein Hash angezeigt.

Neuwessi11 on 17 Sep 2020

Oh ja, vielen Dank, das hilft schon mal sehr, denke ich!

Das ist schon mal schön! :+1:

Überprüfen, wann normalerweise die automatische Aktualisierung im Hintergrund stattfindet,

Wenn ich lange wach bin oder das Telefon über Nacht an lasse, zwischen 2 und 3 Uhr. Sonst beim Anschalten.

Das heißt, wenn das Telefon angeschaltet (und am Ladegerät) ist, funktioniert die automatische Aktualisierung zuverlässig.
Wenn das Gerät angeschaltet wird, könnten die oben erwähnten Probleme auftreten: Die Corona-Warn-App (CWA) wird für die Aktualisierung geweckt, aber das Gerät ist noch zu sehr mit dem Start beschäftigt, dass die Risiko-Ermittlung nicht erfolgreich abgeschlossen werden kann.

Zu der Zeit, wenn die Hintergrundaktualisierung stattfindet, das Telefon möglichst am Ladegerät haben.

Das bringt doch aber nur etwas, wenn es dann nicht ausgeschaltet ist, richtig? Würde mir, der ich es ganz altmodisch gerne ausschalten möchte, nicht so viel bringen?

Richtig, genau.

Falls das Telefon eingeschaltet wird, lieber ein paar Minuten abwarten, bevor die Corona-Warn-App geöffnet wird.

Das habe ich schon probiert. Hat nichts oder nicht immer etwas gebracht.

Wenn die automatische Aktualisierung normalerweise nachts erfolgt, dann versucht CWA beim Start des Telefons die Aktualisierung so schnell wie möglich nachzuholen. Dann kommt es zu dem oben beschriebenen Problem. Stimmt, dann kann es leider auch nichts bringen. Wäre die Uhrzeit für die automatische Aktualisierung während des Tages, könnte man mit dieser Maßnahme (Warten mit dem Öffnen) etwas erreichen.

Wenn in diesem Tumult nun die Corona-Warn-App auch noch anfängt, die Daten für die Risiko-Ermittlung vom
Telekom-Server herunter zu laden, und danach an die Google Play Services zur Überprüfung zu übergeben, kann es sein, dass
es hier zu einem Timeout (einer zu langen Verzögerung bei der Bearbeitung) kommt, und die Risiko-Ermittlung stumm
abgebrochen wird.
In der Regel kann man das daran erkennen, dass in dem Überprüfungsprotokoll (Android > Einstellungen > Google >
Covid-19-Benachrichtigunen > Überprüfungen auf mögliche Begegnungen) für den betreffenden Tag für die Uhrzeit des
Einschaltens des Telefons nur wenige Einträge (weniger als 14) zu finden sind.

Da habe ich gerade mal nachgesehen. Für die letzten drei Tage (an denen der Fehler aufgetreten ist) waren da jeweils 20 Einträge. Wenn ich auf die Details gehe, wird mir die Uhrzeit, die Anzahl der Schlüssel (einige tausend), die Anzahl der Treffer, die App und ein Hash angezeigt.

Das scheint meine Vermutung mit dem Timeout zu belegen: Vermutlich wurden nach dem Start des Telefons zunächst irgendwo zwischen 7 und 11 einzelne Dateien mit Diagnosedaten auf eine Begegnung überprüft. Normalerweise sollten aber 14 Dateien überprüft werden, für jeden der letzten 14 Tage eine. Die Überprüfung ist dann aber wohl innerhalb des Exposure Notification Sytems fehlgeschlagen. CWA hat dann nach ein paar Sekunden oder Minuten oder Stunden erneut versucht, die Diagnosedaten der 14 Dateien an die Google-Schnittstelle zu übergeben. Diesmal ist es aber nach 13 bis 9 Dateien fehlgeschlagen, weil dann nämlich das Limit an gültigen Aufrufen der Google-Schnittstelle erreicht wurde. Nur 20 Aufrufe pro Tag sind in der jetzigen Version von Google zugelassen. Warum es dieses Limit gibt, darüber kann ich nur spekulieren, weil ich noch kein offizielles Dokument dazu gefunden habe, das eine Aussage zu dem Grund des Limits macht. In der Diskussion mit anderen Mitgliedern der Community hier hat sich aber herauskristallisiert, dass das Limit vermutlich dazu da ist, um den Akku des Telefons zu schützen, da der Prozess der Risiko-Ermittlung ziemlich rechenintensiv ist.
Mit der Version 1.4.0 von CWA wird es aber vermutlich besser, da CWA dann eine neue Funktion der Google-Schnittstelle nutzen kann, die es ermöglicht, alle 14 Dateien auf einmal an die Schnittstelle zu senden. Das zählt dann nur als ein einziger Aufruf. Falls dann etwas schief läuft (Timeout), kann CWA noch 19 weitere Versuche unternehmen, die Risiko-Ermittlung erfolgreich durchzuführen.

Für diesen Moment, und in dem von dir geschilderten Fall, dass wohl ein Timeout in der Hintergrundaktualisierung beim Einschalten auftritt, ist es schwierig, etwas zu raten...
Hängt das Telefon am Ladegerät, wenn es eingeschaltet wird? Dann könnte man versuchen, es vor dem Einschalten vom Ladegerät zu nehmen, und zu hoffen, dass CWA im Doze-Mode war, bevor das Telefon ausgeschaltet wurde. Dann würde CWA beim Einschalten zwar geweckt, kann aber erst aktiv werden, wenn das Betriebssystem CWA eine Zeitspanne zuordnet, in der es wieder aktiv werden darf - vermutlich erst einige Zeit nach dem Einschalten. Ob das aber klappt, weiß ich nicht.

Am einfachsten wäre es aber sicherlich, das Telefon über Nacht eingeschaltet am Ladegrät zu lassen - dann wird der Fehler sehr wahrscheinlich nicht mehr oder nur noch sehr selten auftreten.

vaubaehn on 17 Sep 2020

👍1

Eine Sache ist mir noch eingefallen:
~Es besteht natürlich auch die Möglichkeit, dass sich im Protokoll der Begegnungsüberprüfungen Einträge finden lassen, dass zunächst 14 Dateien an die Google-Schnittstelle übergeben wurden, und danach dann nochmal 6.
Ich hatte so etwas mal bei mir, alle 20 Überprüfungen waren innerhalb von einer Minute. Da aber keine Sekundenangaben enthalten sind, ist nicht klar, ob zuerst 14 und dann 6 Dateien übergeben wurden, oder zuerst 6 und dann 14.
Falls zuerst 14 Dateien übergeben wurden, und dann 6, gäbe es eigentlich nur die Erklärungsmöglichkeit dafür, dass CWA aufgerufen wurde, bevor die Routine zur Zurücksetzung des API call counters innerhalb des ENF das erste Mal nach dem Telefonstart durchgelaufen ist.
Das müsste mal systematisch getestet werden, und wenn das tatsächlich passieren kann, müsste Google hier eine Lösung erarbeiten (=> @thomasaugsten ).~

So, von mir jetzt wieder weiter auf English...
See you later

~[Edit: dass es auch tatsächlich 14 Dateien waren, zeigte sich an den Hashs]~
[Edit 2: zweite Erklärungsmöglichkeit: ausgrechnet bei der letzten, 14. Übermittlung der timeout...]

@thomasaugsten => sorry, jetzt war ich wohl doch etwas schnell und habe ich hier wahrscheinlich einen Fehlalarm produziert. Hier => https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-674059696 hatte Kamil dargestellt, wie der Counter hochgezählt und auch zurückgesetzt wird. Das Datum wird also auf jeden Fall beim API Call in betracht gezogen, nur so macht es Sinn. Eine race condition, wie oben dargestellt, ist daher äußerst unwahrscheinlich.

vaubaehn on 17 Sep 2020

👍1

Ich verstehe das meiste Technikzeug oben nicht wirklich.

Aber ich habe das Problem ebenfalls. Weiterhin. Trotz dem alles aktuell ist und ich mehrfach versucht habe die App 24 Stunden zu schließen.

Manchmal lief es dann für einen Tag bevor das gleiche Problem wieder kam, manchmal kam die Fehlermeldung direkt beim Einschalten der App.

Habe keine Ahnung mehr was ich noch tun kann.

Das Telefon war die gesamte Zeit eingeschaltet.

Gigglebug on 18 Sep 2020

@Gigglebug was für ein Gerät hast du und mit welcher Android Version?
Hast du "Priorisierte Hintergrundaktivität" in den CWA Einstellungen aktiviert?

daimpi on 18 Sep 2020

Have the same Error since 3 days. "Priorisierte Hintergrundaktivität" is enable, smartphone is always turned on.
My "Risiko-Ermittlung" is not available (last refresh was on 15th of Sep. 2:11 a.m.). I download the new version of the app on 16 th of Sep..
I use a Blackview A5 with Android 6.0.

dukleinekkmaus on 18 Sep 2020

Alles ist an und das System sowie alle Apps auf dem neuesten Stand. Und es ist ein Samsung J510

Gigglebug on 18 Sep 2020

Mir fällt aber ein, dass es vielleicht genau die Tage funktioniert hatte wo ich es über Nacht am Ladekabel hatte. Dann hat es sich nämlich irgendwie um kurz nach 2 oder 3 von selber aktualisiert. Also ohne dass ich die App in den Vordergrund gepackt habe. Und auch wenn ich die App trotz der Fehlermeldung im Hintergrund habe laufen lassen.

Wie gesagt ich steige bei dem meisten was da oben steht nicht wirklich durch, aber da hatte gleube ich wenn ich es richtig verstanden habe auch jemand gemeldet es hätte sich am Ladekabel dann irgendwie nachts selbstständig aktualisiert?

Ich kann das gerne mal die kommende Nacht versuchen. Ich bin mir gerade nämlich nicht sicher, aber ich glaube dass es an einigen Tagen geklappt hatte wo ich es Nachts auf dem Tisch hatte wo auch das Ladekabel hängt. Nur ob es auch angeschlossen war weiß ich gerade nicht.

Gigglebug on 18 Sep 2020

Hallo @Gigglebug , ich denke, das Telefon in der Nacht angeschaltet an das Ladekabel zu hängen, ist eine gute Idee.
Bitte berichte doch danach, ob es dann funktioniert hat.
Vielen Dank!

vaubaehn on 18 Sep 2020

👍1

Have the same Error since 3 days. "Priorisierte Hintergrundaktivität" is enable, smartphone is always turned on.
My "Risiko-Ermittlung" is not available (last refresh was on 15th of Sep. 2:11 a.m.). I download the new version of the app on 16 th of Sep..
I use a Blackview A5 with Android 6.0.

Hi @dukleinekkmaus , was the telephone connected to the charge during the night?

vaubaehn on 18 Sep 2020

Hi @dukleinekkmaus , was the telephone connected to the charge during the night?

No, I don't charge the phone in the night, because I'm afraid of damage in the battery. My last battery was discharge in one hour. So I try to be very carefull with the New one...but for tonight I will make an exception.

I try it, but unfortunately it does not work.

dukleinekkmaus on 18 Sep 2020

👍1

@dukleinekkmaus

I try it, but unfortunately it does not work.

Does this mean, leaving your phone turned on and plugged in overnight, didn't resolve the problem for you?

daimpi on 19 Sep 2020

@dukleinekkmaus

I try it, but unfortunately it does not work.

Does this mean, leaving your phone turned on and plugged in overnight, didn't resolve the problem for you?

Yes, it mean that the problem is still there. When I open the APP in the morning the Error message 39508 was shown and the Risiko-Ermittlung was not refreshed.

dukleinekkmaus on 19 Sep 2020

I see… can you share your ENF log, then we could see at which time the checks are usually performed.

daimpi on 19 Sep 2020

I see… can you share your ENF log, then we could see at which time the checks are usually performed.

These are Screenshots From the last days. They are not complete, because I have no idea how to Export this in a Text file vor Text form.

Screenshot_20200920-002225
Screenshot_20200920-002152

dukleinekkmaus on 20 Sep 2020

@dukleinekkmaus you can export them by clicking on the burger menu (upper right corner) -> "export checks"

You can then upload them here after you pack them into a .zip file or rename the file ending from .json to .txt 🙂.

daimpi on 20 Sep 2020

@dukleinekkmaus are you still awake currently and for the next ~30 min? If so you could try something: given that your checks are usually performed between 2 and 3 am and that the rate limit is reset at 2 am (CEST) you could try to plug your phone into the charger and deliberately open CWA shortly after 2 am while making sure that your phone is not in any type of power saving mode. It should then try to perform an update, but this time CWA will run in the foreground, which might alleviate some potential problems stemming from insufficient processing power allocation 🙂.

daimpi on 20 Sep 2020

👍1

Okay usually I Fall asleep bevor 2am. Maybe I can set next weekend the alarm so I can try it. All energy saving options are disable at the phone since I try to delete the error.

dukleinekkmaus on 20 Sep 2020

The screenshots in https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-695362395 show at least 4 trials to ProvideDiagnosisKeys() at September 18. This _could_ be related to #1187 . Having a deeper look into the exposure check history, like @daimpi suggested, could support that assumption.

vaubaehn on 20 Sep 2020

Hi @thomasaugsten ,
in comment https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-694109193 I had referenced following part to you for your consideration:

Für mich ist recht deutlich, dass Google hier nochmal nacharbeiten müsste, um einen Timeout innerhalb des Exposure Notification Framework (ENF) zu verhindern (=> @thomasaugsten ), falls das nicht bereits geschehen ist, und wir einen Fix mit einer neuen Version des ENF bald erhalten.

I completely forgot about the transaction timeouts that can be handled by CWA. In #1138 they're prolonged to 3 minutes. If ProvideDiagnosisKeys() itself is not the problem, changing timeout like in#1138 could help solving the problem.
However, delays of transaction start due to CWA being in doze mode or being inside the rare bucket still need to be taken into account when exposure checks are not performed at all.

Thanks for all your support here.

vaubaehn on 20 Sep 2020

@dukleinekkmaus

Okay usually I Fall asleep bevor 2am. Maybe I can set next weekend the alarm so I can try it.

No need to stay up late, I think I've found a better way:

Before you go to bed tonight, de-activate "Exposure-Logging" in CWA
When you wake up tomorrow, make sure that your phone is plugged into a charger
Open CWA and activate "Exposure-Logging" while being plugged into a charger
CWA should now try to perform an update, keep it for at least ~1 min in the foreground for this update to conclude
Check whether the error has disappeared

The basic idea is the same as in my post above: we're trying to get CWA to perform the update while having optimal conditions (power plugged in, no battery savings, foreground task) and then check whether the problem disappears.

To be clear: I'm not very confident that this is a sustainable solution, which will fix the error permanently. It's more of a test to isolate the problem, but it might help nevertheless 🙂.

daimpi on 20 Sep 2020

👍2

Okay I followed the list above.
WEhen CWA refreshed the status I got the 9002 timeout message: for the Detais look at the Screenshots.
After that again I bot the Error 39508. The ENF logs from Yesterday and today are Attached.

Screenshot_20200921-071807

Screenshot_20200921-071815

all-exposure-checks.txt

all-exposure-checks2.txt

dukleinekkmaus on 21 Sep 2020

👍1

In the logs of dukleinekkmaus there are 14 lines with "21. September 2020, 07:16" and six with 07:19.
Why ist the exposure check continued or restarted when there are already 14 lines with different keyCounts? Isn't it complete then?
Same with "20. September 2020, 02:35": after 14 lines it goes on with six lines at 02:37. The days before that are different.

kereng5 on 21 Sep 2020

👍1

@dukleinekkmaus thanks for testing this and providing your logs, this helps a lot 🙂.

It seems like you're now encountering https://github.com/corona-warn-app/cwa-app-android/issues/1187. When checking your ENF log (all-exposure-checks2.txt) I found that all packets for the last 14 days were already listed in first check today (21. September 2020, 07:16), even the most recent package which just became available today was listed there, which I take as an indication that the download of the packages went without problems.
My guess is that the 60s timeout occurs when your phone tries to compare the diagnosis keys (DKs) it downloaded from the server with the rolling proximity identifiers (RPIs) your phone recorded. Maye the process of expanding the DKs to compare them with the RPIs takes takes so long that you're hitting the 60s time limit? This will probably improve with https://github.com/corona-warn-app/cwa-app-android/pull/1138 which extends this time-limit to 3min and is currently targeted for CWA 1.4.
@kbobrowski @vaubaehn does this sound plausible to you, what do you think?

This is a really interesting issue which brings up the question of how much performance this process needs and how close we are on different devices to the timeout limits. And this will probably just become more relevant as the number of infections (and therefore DKs) increases, as well as when it comes to European interoperability, as this means even more DKs will have to be processed by each device.

If my suspicion is correct, one thing the devs could do to improve the situation (besides increasing timeout limits in #1138) would be to lower the padding multiplier on the server: currently for every real DK uploaded, 4 fake DKs are inserted as well (see the "ratio between fictitious and legitimate diagnosis keys" here) and those also have to be expanded/decrypted by your phone. Having less fake DKs could lower the load on the devices significantly and imho the current padding implementation doesn't really improve privacy anyway (this is a whole separate discussion but if you're interested, https://github.com/corona-warn-app/cwa-server/issues/620 is a good starting point). Given that this is something that could be done on the server side w/o requiring any updates to the clients I think reducing the padding multiplier, or even getting rid of the padding entirely would be a good idea. This wouldn't immediately fix the problem, as the old packages are still huge and only drop out of the 14 day window one day at a time but the sooner this is changed the better imho.

daimpi on 21 Sep 2020

👍1

@daimpi

It seems like you're now encountering #1187.
[...]My guess is that the 60s timeout occurs when your phone tries to compare the diagnosis keys (DKs) it downloaded from the server with the rolling proximity identifiers (RPIs) your phone recorded.
[...] @kbobrowski @vaubaehn does this sound plausible to you, what do you think?

I completely agree. Nice support :+1:

I had some thoughts, why there might be 14 checks at one point in time, and later the other (rate limited) 6 checks.
In the current implementation of CWA, all 14 files are sent to ENF within a for-each-loop, each file a single API call. I guess/assume, that API takes over the call, and for each file starting a single instance/thread, processing them all asynchronously. This process might take > 60s, but are finished successfully inside ENF, hence the exposure check history shows all 14 file checks. But the timeout of the transaction occured before, transaction aborted as failed (if you just waited some seconds more, dear transaction!). Thus, a new try is begun later, running into API rate limit.
In cases where less than 14 files have been checked, the transaction also timed out, but less files could have been delivered to API.
But this is only a guess without any testing, not sure, if this matches reality.

This is a really interesting issue which brings up the question of how much performance this process needs and how close we are on different devices to the timeout limits. And this will probably just become more relevant as the number of infections (and therefore DKs) increases, as well as when it comes to European interoperability, as this means even more DKs will have to be processed by each device.

Exactly. Like you suggested, lowering the padding multiplier is a nice way to mitigate problems here. Another suggestion would be to switch to 3-hourly packages as soon as possible. As far as I remember, with newer ENF versions they should now accumulate for the daily risk assessment, since tokens (to bind diagnosis keys to batches) are now deprecated. Checking more often during the day with different but smaller packages might also take some load off.

@JoachimFritsch
I want to push forward @daimpi 's nice analysis and suggestion to you:

If my suspicion is correct, one thing the devs could do to improve the situation (besides increasing timeout limits in #1138) would be to lower the padding multiplier on the server

I agree, and I think it's the most elegant and fastest solution to "9002: timed out while waiting for 60000ms" , until #1138 is deployed. Like @daimpi , I don't see a big privacy concern.
Thank you for your consideration, @JoachimFritsch .

vaubaehn on 21 Sep 2020

👍1

@vaubaehn thanks for the additional Information 🙂.

One thing I was wondering about:

Another suggestion would be to switch to 3-hourly packages as soon as possible. As far as I remember, with newer ENF versions they should now accumulate for the daily risk assessment, since tokens (to bind diagnosis keys to batches) are now deprecated. Checking more often during the day with different but smaller packages might also take some load off.

Is the scenario you're envisioning one which utilizes ExposureWindow mode in ENF v1.5+? Does this really decrease the load on the phone? I was under the impression that even in this case every time a check is performed all DKs of the past 14 days will be expanded and compared to the RPIs. Wouldn't this rather increase the load per day (while keeping the load per check constant)?

daimpi on 21 Sep 2020

Same Problem here:
After update to the latest Version CWA 1.3.1
I got the same Error.

koehleru on 25 Sep 2020

There is an entry from @thomasaugsten in this thread which says:

Wir werden in den nächsten Tag die Version 1.3.1 veröffentlichen die das Problem für die meisten lösen wird.

and I believe this information is outdated.

Perhaps the Open Source Team (@svengabr ?) could confirm if https://github.com/corona-warn-app/cwa-app-android/pull/1150 shown in https://github.com/corona-warn-app/cwa-app-android/releases/tag/1.4.0-SNAPSHOT-RC3 will fix the issue? Or are there other changes necessary?

I'm looking at "Version Checker with Branching for Checks on provideDiagnosisKeys below v16 of ENF (EXPOSUREAPP-2213)" https://github.com/corona-warn-app/cwa-app-android/pull/1150 which has the same reference (EXPOSUREAPP-2213) as this issue #1021.

MikeMcC399 on 25 Sep 2020

👍1

Yes the change to mitigate the rate limit is unfortunately in 1.4. But the release of 1.4 is in beginning of October.

thomasaugsten on 25 Sep 2020

👍2

@dukleinekkmaus

Okay usually I Fall asleep bevor 2am. Maybe I can set next weekend the alarm so I can try it.

No need to stay up late, I think I've found a better way:

Before you go to bed tonight, de-activate "Exposure-Logging" in CWA

When you wake up tomorrow, make sure that your phone is plugged into a charger

Open CWA and activate "Exposure-Logging" while being plugged into a charger

CWA should now try to perform an update, keep it for at least ~1 min in the foreground for this update to conclude

Check whether the error has disappeared

The basic idea is the same as in my post above: we're trying to get CWA to perform the update while having optimal conditions (power plugged in, no battery savings, foreground task) and then check whether the problem disappears.

To be clear: I'm not very confident that this is a sustainable solution, which will fix the error permanently. It's more of a test to isolate the problem, but it might help nevertheless 🙂.

I deactivate bluetooth every night and reactivate in the morning with Macrodroid. Also I tried to update during night or early morning, but the error kept.

I try to deactivate exposure logging also at night.

Oneplus 5t
Android 10 (CrDroid Custom Rom)
CWA 1.3.1

Not updating since 2020-08-19.
Device was turned off for several days during holidays but the issue kept.

BR
Martin

Matzgitz on 26 Sep 2020

👍1

Das Problem besteht auch nach 1 Woche probieren mit und ohne Ladekabel noch.

Gigglebug on 27 Sep 2020

@Gigglebug kannst du mal bei dir ausprobieren was passiert wenn du das was ich oben geschrieben habe machst?

No need to stay up late, I think I've found a better way:

Before you go to bed tonight, de-activate "Exposure-Logging" in CWA

When you wake up tomorrow, make sure that your phone is plugged into a charger

Open CWA and activate "Exposure-Logging" while being plugged into a charger

CWA should now try to perform an update, keep it for at least ~1 min in the foreground for this update to conclude

Check whether the error has disappeared

The basic idea is the same as in my post above: we're trying to get CWA to perform the update while having optimal conditions (power plugged in, no battery savings, foreground task) and then check whether the problem disappears.

To be clear: I'm not very confident that this is a sustainable solution, which will fix the error permanently. It's more of a test to isolate the problem, but it might help nevertheless 🙂.

@Matzgitz did you try it and if so, what was the result? Could you share your ENF log here?

daimpi on 27 Sep 2020

Nee, hab auch nur 1 aus 5 Worten in dem Text verstanden.

Gigglebug on 27 Sep 2020

@Gigglebug

Nee, hab auch nur 1 aus 5 Worten in dem Text verstanden.

Ok kein Problem, hier ist die deutsche Version:

Es ist nicht nötig, lange aufzubleiben, ich glaube, ich habe einen besseren Weg gefunden:

Deaktiviere "Risiko-Ermittlung" in CWA, bevor du heute Abend ins Bett gehst
Wenn du morgen aufwachst, stell sicher, dass dein Telefon an ein Ladegerät angeschlossen ist
Öffne die CWA und aktiviere "Risiko-Ermittlung", während du an ein Ladegerät angeschlossen bist
CWA sollte nun versuchen, ein Update durchzuführen. Sorge dafür, dass sie mindestens ~ 1 Minute im Vordergrund bleibt, damit dieses Update abgeschlossen wird
Überprüfe, ob der Fehler verschwunden ist

Die Grundidee ist die gleiche wie in meinem obigen Beitrag: Wir versuchen, CWA dazu zu bringen, das Update unter optimalen Bedingungen durchzuführen (an das Netzteil angeschlossen, keine Energiesparmaßnahmen, Task im Vordergrund) um dann zu sehen, ob das Problem verschwindet.

Um es klar auszudrücken: Ich bin nicht sehr zuversichtlich, dass dies eine nachhaltige Lösung ist, die den Fehler dauerhaft behebt. Es ist eher ein Test, um das Problem zu isolieren, aber es könnte trotzdem helfen 🙂.

daimpi on 27 Sep 2020

Screenshot_20200928-002907
Screenshot_20200928-002923
Screenshot_20200928-002911
Screenshot_20200928-003253

I also encounter issues here since yesterday. Tried it multiple times, also with high battery / plugged in and via WiFi...

yorickreum on 28 Sep 2020

@yorickreum you could also try what I suggested above: https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-695778752

If you do: could you report back tomorrow whether it worked and share your ENF log here?

daimpi on 28 Sep 2020

Also meine App scheint irgendwann gestern ein Update ausgeführt zu haben. Denn heute hat es auch ohne die obigen Schritte funktioniert.

Ich beobachte mal ob das jetzt so bleibt oder nicht.

Ich war die vergangene Woche ja nicht zuhause, und es kann sein, dass ich mal (Kostenvermeidung) angewählt hatte dass das Telefon Apps nur aktualisieren soll wenn es im W-Lan ist. Da ich aber am Arm der Welt war gabs sowas da halt nicht. Ich hatte ja gedacht dass dieses Update noch vor dem Urlaub kommt (hieß ja irgendwie Mitte September "in ein paar Tagen").

Gigglebug on 28 Sep 2020

👍1

I tried it some days without switching off the phone at night --> no error.
After that I had a couple of days no problem even if the phone was switched off.
But yesterday when starting the phone, the error was back. So today I tried the suggested routine and had no problem again.
But - in order to try to share my ENF logs, I didn't find them. In the burger menu I only have "Überblick", "App-Informationen" and "Einstellungen" and nothing else. Even when tapping on each point, there is no point that sounds like "Share ENF".

App version is now 1.3.1, but the whole last week (with v. 1.3) I didn't find the right point.

By the way, thanks a lot for the German support last time!!!

Neuwessi11 on 28 Sep 2020

@Neuwessi11

But - in order to try to share my ENF logs, I didn't find them. In the burger menu I only have "Überblick", "App-Informationen" and "Einstellungen" and nothing else. Even when tapping on each point, there is no point that sounds like "Share ENF".

"Überblick", "App-Informationen" and "Einstellungen" are in the menu for the Corona-Warn-App. You need to go to the Google user interface.
(Android) Einstellungen > Google > COVID-19-Benachrichtigungen > Überprüfung auf mögliche Begegnungen
Menu (three dots) now shows Überprüfungen exportieren and Überprüfungen löschen.
Choose Überprüfungen exportieren.

MikeMcC399 on 28 Sep 2020

👍1

"Überblick", "App-Informationen" and "Einstellungen" are in the menu for the Corona-Warn-App. You need to go to the Google
user interface.

Thank you! So much for the difference between 'developer's logic' and 'user's logic' ...

all-exposure-checks[1].txt

Neuwessi11 on 28 Sep 2020

😄1 👍1

Ok, I see that my version looks quite different to the versions I have seen before. What was my mistake?

I want to make clear, that this is no bug reporting, because my plan is now to wait for the 1.4 update and to look if it's getting better.
I only reported the ENF log file, because I got the impression it might help you solving the problem.

Neuwessi11 on 28 Sep 2020

@Neuwessi11

I want to make clear, that this is no bug reporting, because my plan is now to wait for the 1.4 update and to look if it's getting better.
I only reported the ENF log file, because I got the impression it might help you solving the problem.

I analysed your file through an Excel pivot table, but I can't read much out of it regarding root causes. We don't know why for instance it tried 20 times on Sep 27, 2020. Maybe @daimpi will be able to infer more? I tend to agree that waiting for the 1.4 is the best short-term tactic.

MikeMcC399 on 28 Sep 2020

👍1

When the timestamp is between 2 and 3 am, I either left the phone switched on or got to bed so late, that CWA already refreshed.
When the timestamp is later, I switched the phone off during night.

That's why vaubaehn thougt already (11 days ago) that it has something to do with the starting routine of the phone coming together with the algorithm of CWA.

But because of the support here I have now two good strategies which I can use while waiting for the 1.4.
But, like more or less expected, 1.3.1 didn't solve my problem (yesterday's proof).

I think I will report the results some days after getting 1.4.

Neuwessi11 on 28 Sep 2020

👍1

Also bei mir scheint es das Update gerichtet zu haben.

Ich habe jetzt seit 2 Tagen in Folge keine Probleme mehr. Falls nochmal was kommt schreibe ich hier nochmal.

Gigglebug on 29 Sep 2020

@Gigglebug

Also bei mir scheint es das Update gerichtet zu haben.

Das ist eher Zufall, dass gerade das Problem nach dem Update auf 1.3.1 nicht mehr vorkommt. :wink:

MikeMcC399 on 29 Sep 2020

👍1

Hello community,

this thread has been closed by mistake, therefore I will go on and reopen it.
We will close the issue when we have confirmation of the fix for the next version.
If you have additional questions, please feel free to reach out.

Thanks,
LMM

Corona-Warn-App Open Source Team

GPclips on 29 Sep 2020

@GPclips

this thread has been closed by mistake, therefore I will go on and reopen it.

I think you might have forgotten to reopen the thread 😉.

daimpi on 29 Sep 2020

👍2 ❤1

I see the same issue since two days ago (last update was on Oct 10, 12:04), with CWA 1.1.3. on a Samsung A3, Android 6.0.1.

PalminX on 12 Oct 2020

@PalminX I'm not too surprised that we start seeing this issue on more and more devices, now that the number of cases is going up significantly. You could try my instructions from above and see whether this allows an update to fully go through on your device the next time. Hopefully we see a lowering of the padding multiplier as soon as possible (@thomasaugsten you mentioned that dropping the multiplier to one is planned, could you ask the server team to implement this asap? 🙏). Other than that we can only wait for CWA 1.5 to be released at the end of October to really improve the situation.

daimpi on 12 Oct 2020

@daimpi Yes, I will try this.

I must say that this is really a terrible user experience, the error message is extremely confusing for the end user, and the fact that the FAQ is not updated definitely makes things worse...

PalminX on 12 Oct 2020

👍4

Hi @daimpi ,
according to https://github.com/corona-warn-app/cwa-app-android/issues/1081#issuecomment-702536816 and to https://github.com/corona-warn-app/cwa-app-android/releases/tag/1.4.0-SNAPSHOT-RC5 it looks like, that quite a lot of problems should be addressed in CWA 1.4.0 that should be expected around 9th of October. We did not hear anything official yet here, when we can expect the next release of CWA.

Dear @svengabr , could you please clarify? Thank you! :heart:

vaubaehn on 12 Oct 2020

😄1

Maybe 1.4.0 is a bit delayed? ;-)

(Edit)

PalminX on 12 Oct 2020

😄2

Maybe?

(Edit)

vaubaehn on 12 Oct 2020

😄2

Today I got a 39508 error on my test phone Samsung Galaxy A5 (2017) SM-A520F. It was not connected to a charger overnight, and at 03:36 it made 8 exposure checks, followed by 12 exposure checks when I opened CWA manually at 08:48. The Exposure Notification System version is 17203704005. This device doesn't normally show this error, so I guess it may randomly happen to other devices as well.

I also have seen the 39508 error occur on an emulated Pixel 3a device running Android 11.
(OT: Google released Android Studio V4.1 yesterday which includes support for Android 11. Surprisingly it is possible to install CWA from the Google Play Store on an emulated Android 11 device, although for previous Android versions you can't install it directly from Google Play Store and it doesn't work on older versions either.)

Apart from the bad user experience, it also delays delivering a risk result until the next day. Potentially if somebody has had an encounter with an infected individual, this could delay informing the user about their increased risk as well. This does need fixing as soon as possible.

MikeMcC399 on 13 Oct 2020

👍4

Same here, phone on charge, 20 checks within one minute around 3:40, now API39508.
LG G4, Android 6
CWA 1.3.1 (ready for 1.4.0+)
ENF 17203704005

vaubaehn on 13 Oct 2020

I see the same issue since two days ago (last update was on Oct 10, 12:04), with CWA 1.1.3. on a Samsung A3, Android 6.0.1.

Today, after following the recipe, when I enabled the app again, it started to update, but after some time, I first got the error
"Cause 9002 Timed Out while waiting for 60000 ms"

Afterwards, the original error (Cause 3, ApiException: 39508) is back again.

So the workaround did not work for me...

PalminX on 13 Oct 2020

@PalminX looks like you're running into resource limitations which can't even be mitigated by providing optimal conditions (cf. @vaubaehn's and my comments above). Unfortunately I don't think there is anything that can be done from the users side to fix this in this case 🙁.

daimpi on 13 Oct 2020

Unfortunately I don't think there is anything that can be done from the users side to fix this in this case slightly_frowning_face.

Yes, nothing we can do anymore, as COVID cases are increasing and the prolongued checking time for exposures runs into the timeout.
But, there is hope! The timeout problem is addressed in #1138 which was already finished one month ago (10th of September)! It will be released with CWA 1,4.0, which was already addressed for 9th of October.
So, only after one month of unnescessary delay, we will receive a fix soon!

vaubaehn on 13 Oct 2020

😄1

Die Corona-App zeigt zwei Probleme bei mir.

der eingetragene, negative Test brachte ein Ergebnis und als ich den Test nicht löschte, dreht nun ein Rad und bringt kein Ergebnis mehr. Damit könnte ich wohl auch keinen Test mehr eintragen.
Der Datenabruf funktioniert nicht mehr korret und die Meldung 39508 erscheint.
Es werden aber immer wieder akatualisierungen zugelassen.

App Version 1.3.1
CAT S60, Android 6.0.1
danke für Hilfe...

MPhilipp1974 on 13 Oct 2020

Hallo @MPhilipp1974 ,

der eingetragene, negative Test brachte ein Ergebnis und als ich den Test nicht löschte, dreht nun ein Rad und bringt kein Ergebnis mehr. Damit könnte ich wohl auch keinen Test mehr eintragen.

Um einen neuen Test eintragen zu können, musst du die App-Daten löschen: öffne dazu die App, tippe auf die drei Punkte oben rechts, und gehe zu "Einstellungen". Dort tippst du auf "Anwendung zurücksetzen". Danach zeigt dir die App an, dass sie 0 Tage aktiv war, und auch die Einträge im Logbuch der Covid-19-Benachrichtigungen (Android > Einstellungen > Google > Covid-19-Benachrichtigungen) sind dann wohl gelöscht. Das sind aber nur kosmetische Probleme, die wichtigen Daten sind alle erhalten geblieben - du kannst gewarnt werden und warnen.
Wenn ich mich richtig erinnere, wird es dazu einen Fix mit dem nächsten Release der App geben.

Der Datenabruf funktioniert nicht mehr korret und die Meldung 39508 erscheint.
Es werden aber immer wieder akatualisierungen zugelassen.

Hier ist das Problem, dass mittlerweile so viele Menschen ihre positiven Diagnosen geteilt haben, dass der Abgleich, ob du eine positiv getestete Person getroffen hattest, recht lange dauert. Falls der Abgleich länger als 60 Sekunden dauert, bricht die App den Abgleich ab, und versucht es später noch einmal. Da aber Google nur eine beschränkte Anzahl von Abgleichen pro Tag zulässt, bedeutet der Fehler 39508, dass die maximale Anzahl von Abgleichen für diesen Tag bereits überschritten ist.
Hier wurde bereits am 10.09.2020 ein Fix erarbeitet (#1138), der die App nun 3 Minuten statt 60 Sekunden den Abgleich machen lässt.
Leider wurde dieser Fix, aus mir nicht nachvollziehbaren Gründen, noch nicht bereit gestellt.
Stattdessen kannst du nach der Anleitung von @daimpi folgendes versuchen:

Bevor du schlafen gehst, stelle den Schiebeschalter der Risiko-Ermittlung in der App auf "aus".
Wenn du dann morgen aufwachst, stelle sicher, dass dein Telefon an einem Ladegerät hängt.
Öffne am besten kurz einen Internet-Browser, und lese ein paar Nachrichten im Internet (das soll sicherstellen, dass dein Telefon möglichst vollständig aufgewacht und mit dem Internet verbunden ist).
Öffne nun die Corona-Warn-App, und schalte die Risiko-Ermittlung wieder auf "ein".
Mit ein bisschen Glück wird nun dein Risiko wieder ermittelt. Mit ein bisschen Pech aber leider auch nicht, da die Dauer des Abgleichs auch davon abhängig ist, wie viele Menschen ihre Zufalls-IDs geteilt haben. Und da die Infektionszahlen nun immer drastischer ansteigen, werden es immer mehr.
Aber tröste dich, du bist mit dem Problem der nicht funktionierenden Risiko-Ermittlung nicht allein. Durch die ansteigenden Infektionszahlen sind immer mehr Benutzer von der Fehlfunktion betroffen.

Viele Grüße und bleib gesund!

vaubaehn on 13 Oct 2020

👍4

@MPhilipp1974

der eingetragene, negative Test brachte ein Ergebnis und als ich den Test nicht löschte, dreht nun ein Rad und bringt kein Ergebnis mehr. Damit könnte ich wohl auch keinen Test mehr eintragen.

@vaubaehn hat ja schon alles beantwortet, nur als kleine Ergänzung: Dieses Problem wird hier getrackt: https://github.com/corona-warn-app/cwa-app-android/issues/1084

daimpi on 13 Oct 2020

For the people who have that problem somewhat longer (so that the increasing numbers of Corona cases are not the reason of the error), I want to report my experiences with the helping routine, that one vaubaehn wrote two comments ago.

In my case it is not necessary to charge the phone, but this may depend on my other phone settings.

What is really helpful in my case: to disable the Risiko-Ermittlung in the app and to enable it next morning in the app.
If I do that, the error didn't appear again.

Auf Deutsch: Wenn ich die Risiko-Ermittlung abends in der App (und nicht in den Telefon- oder Google-Einstellungen) beende und am nächsten Morgen irgendwann ein paar Minuten nach dem Einschalten des Telefons die Risiko-Ermittlung in der App wieder starte, kam der Fehler bei mir bisher nicht wieder.

Neuwessi11 on 14 Oct 2020

👍3

I've been having the problem (39508) since weeks, some days (like one a week) it will work... also when I open the app it's saying "exposure logging is not possible" even though I had it activated since I downloaded the app and if I go to "activate" it's saying it's active and has been so for 14 days. Then after a few seconds it's showing the 39508-notification.
Came here from the coronawarnapp-FAQ because waiting 24 hours until opening the app again has not proven successful in my case... (like it described on the website as a forst thing to try)
My device is a Xiaomi Redmi 3s, Android Version 6.0.1, CWA Version 1.3.1
Any help from one of you? :)
(Otherwise I will try the described method of deactivating the exposure logging this evening and reactivating tomorrow morning while the charger is plugged in still.)

ruja90 on 14 Oct 2020

@ruja90

Otherwise I will try the described method of deactivating the exposure logging this evening and reactivating tomorrow morning while the charger is plugged in still.

That's a good idea, even though it's an annoying workaround which isn't guaranteed to work.
Unfortunately there is not much else that can be done from the users side, we have to wait for the CWA team to release an update and/or the server team to lower the padding multiplier.

daimpi on 14 Oct 2020

Hallo,
Die corona warn app hat bei mir einen Fehler (39508), schon seid Tagen. Ausschalten, warten - bringt alles nix.
Device name : Samsung A3
Android version : 6.0.1
cwa : 1.3.1
Viele Gruesse,
Robert

Das werde ich einmal ausprobieren:
Auf Deutsch: Wenn ich die Risiko-Ermittlung abends in der App (und nicht in den Telefon- oder Google-Einstellungen) beende und am nächsten Morgen irgendwann ein paar Minuten nach dem Einschalten des Telefons die Risiko-Ermittlung in der App wieder starte, kam der Fehler bei mir bisher nicht wieder.

bluerobert on 14 Oct 2020

Könnte es sein, dass dieses Probelm entsteht wenn das Gerät über die Nacht ausgeschaltet ist?
Ich werde heute Nacht auch testen ob es fubktioniert die Risiko-ermittlung zu deaktivieren.

Andere Frage am Rande: muss hier alles in englischer Sprache kommuniziert werden?

Nils6852 on 14 Oct 2020

@Nils6852

Andere Frage am Rande: muss hier alles in englischer Sprache kommuniziert werden?

Die Projektsprache ist Englisch und daher die bevorzugte Sprache. Wie man aber in diesem Thread sieht, wird Deutsch auch verwendet. Die FAQs findest Du sowohl auf Englisch als auch auf Deutsch. Ich denke, die meisten User haben ihr Handy auf deutsch eingestellt, andere aber auch englisch, daher gibt es oft eine Sprachmischung in den Fehlermeldungen und Beschreibungen dazu.

MikeMcC399 on 14 Oct 2020

Ich krieg die Fehlermeldung seit über 10 tagen, auch wenn ich die app regelmäßig für ein paar tage nicht öffne oder irgendwie aktiv betrachte.
Gerät: LG X Power
Android: 6.0.1
CWA: 1.3.1

HlneWeb on 15 Oct 2020

Bei mir hat das Funktioniert:

Auf Deutsch: Wenn ich die Risiko-Ermittlung abends in der App (und nicht in den Telefon- oder Google-Einstellungen) beende und am nächsten Morgen irgendwann ein paar Minuten nach dem Einschalten des Telefons die Risiko-Ermittlung in der App wieder starte, kam der Fehler bei mir bisher nicht wieder.

Nils6852 on 15 Oct 2020

👍1

Hi,

I'm facing this issue since last week. My data:

Moto g 6
Android Version 9, PPSS29.55-37-7-10
CWA Version 1.3.1

Closing the app and opening it again after 24 hours does not help. I shut down my smartphone over night. Today I'll test if keeping it on over night helps..

Alberto189000 on 15 Oct 2020

Hi,
I seem to have run in this problem with my phone too.

OnePlus X
Android Version 6.0.1
CWA Version 1.3.1

Not opening the app for 24h didn't help to solve the problem.

LukasE93 on 15 Oct 2020

Same issue - not opening the app for 24 hours didn't help. I usually turn my phone off over night, but this night I didn't and the issue persists... (since 10/10):

Device name: Oppo A57
Android version: 6.0.1
CWA App version: 1.3.1

bulegila on 15 Oct 2020

I tried the workaround now for two days in a row, and it always results in "Cause 9002 Timed Out while waiting for 60000 ms"

PalminX on 15 Oct 2020

Same issue since some weeks.
Device : Galaxy S5 mini
Android : 6.0.1
App : 1.3.1

HansHabenicht on 15 Oct 2020

Könnte es sein, dass dieses Probelm entsteht wenn das Gerät über die Nacht ausgeschaltet ist?
Ich werde heute Nacht auch testen ob es fubktioniert die Risiko-ermittlung zu deaktivieren.

Nein. Meines ist eingeschaltet und ich lasse nachts mittlerweile auch das W-Lan eingeschaltet, damit ein Check mitten in der Nacht nicht am fehlenden Netz fehlschlägt.

Es tut sich aber erst ein Update, wenn ich die App direkt anstupse.

Heute morgen hatte ich den gleichen Fehler, obwohl Handy am Ladegerät hing.

Wenn ich ins Log schaue, dann werden ein paar Datensätze verarbeitet und dann ist Schluß. Die Minute ist um.

Angesichts der aktuell steigenden Infektionszahlen wird sich das Problem auch nicht von selbst beheben. Die App läuft erst dann wieder, wenn man sie nicht mehr braucht.

Ich verstehe nicht, wieso hier nicht längst eine neue Version mit einem Fix veröffentlich wurde.

AnOtherMuenchner on 15 Oct 2020

Hi @Nils6852 und @AnOtherMuenchner

Könnte es sein, dass dieses Probelm entsteht wenn das Gerät über die Nacht ausgeschaltet ist?
Ich werde heute Nacht auch testen ob es fubktioniert die Risiko-ermittlung zu deaktivieren.

Nein. Meines ist eingeschaltet und ich lasse nachts mittlerweile auch das W-Lan eingeschaltet, damit ein Check mitten in der Nacht nicht am fehlenden Netz fehlschlägt.

Tatsächlich kann es sich verschlimmern, wenn das Gerät über Nacht ausgeschaltet ist. Das liegt daran, dass beim Systemstart ((Re-)boot des Telefons) ziemlich viel Prozessorzeit auf viele unterschiedliche Aufgaben verteilt werden muss (hier und da muss was initialisiert werden, dort müssen ein paar Einstellungen gelesen werden, usw.). Beim Start des Telefons möchte die CWA nämlich auch gleich gerne mal die Risiko-Ermittlung starten, und konkurriert hier mit vielen anderen (System-)Anwendungen. Ähnliches gilt, wenn das Telefon über Nacht zwar an, aber nicht in der Steckdose war, und morgens dann ans Ladegerät gehängt wird: Dann war das Telefon nämlich im Doze mode. Um möglichst viel Energie zu sparen, werden die meisten Anwendungen dann nur ab und an für eine sehr kurze Laufzeit mal kurz gestartet. Wenn das Telefon dann morgens ans Ladegerät gehängt wird, wacht es aus dem Doze mode auf, und diverse Anwendungen fangen gleichzeitig wieder an zu laufen, hungrig nach Prozessorzeit lechzend. CWA kann trotz aller Tricks und Vorsichtsmaßnahmen auch im Doze mode sein, und konkurriert hier beim Aufwachen wieder mit anderen Apps.
Daher: am besten über Nacht angeschaltet am Ladegerät lassen (evtl. mit ausgeschalteter Risiko-Ermittlung).

@PalminX
Wo arbeitest du denn? Auf dem Hauptbahnhof? Hast du zufällig besonders viele RPIs sammeln können? Dann dauert der Abgleich ja umso länger...

Edit: habe gerade gelernt, dass die Anzahl der RPIs kaum zur Prozessorlast beiträgt. Daher sind Ratschläge zur Minimierung von RPIs nicht zweckmäßig.

Was ich versuchen würde: alles an Apps force stoppen, was ich nicht unbedingt brauche. ALLES. Dein Phone ist ja gerootet, evtl. kann dir jemand (hüstel) zeigen, wie du Einträge aus der RPI-Datenbank löschst (falls das möglich ist)? Das könnte schon einiges bringen... Falls hier kein CWA'ler helfen kann, ich glaube bei microG hatten sich mal ein paar Leute damit beschäftigt.

vaubaehn on 15 Oct 2020

@svengabr @heinezen @abro1i and all other CMs:
are you aware of the increasing amount of bug reports? CWA is not working anymore for more and more people.
Could you provide/estimate any release date for 1.5?
Thanks a lot

vaubaehn on 15 Oct 2020

👍4

Same issue since 4th of October.
Device : Galaxy S5 mini /SM-G800F
Android : 6.0.1
App : 1.3.1

Tried mentioned shutting down of the risk checking, didnt't help.
First the app runs into a timeout, and then the error 39508 is persistent.
Annoying, as my town is a corona hotspot, and it would be great to know about exposures.

Emilie1959 on 15 Oct 2020

Device : Galaxy S5 mini
Android : 6.0.1
App : 1.3.1
I receive this error message everytime I open the app. I haven't been able to do a risk checking since 15.09.2020. I have no idea what to do and consider deinstalling the app.

BN72 on 15 Oct 2020

I get this error each time I open the app. Last risk checking was done at 30. Sept.
Closing the App for 24 hours didnt change anything
Device: SM-J500FN
Android: 6.0.1
App: 1.3.1

MartinLD01 on 15 Oct 2020

Hi @Alberto189000 , @LukasE93 , @bulegila , @HansHabenicht , @Emilie1959 und @BN72 ,

Bitte versucht, was hier: https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-707879303 im zweiten Abschnitt beschrieben ist (Risiko-Ermittlung vor dem Schlafen ausschalten usw.) Es gibt keine Garantie, dass das klappt, aber die Chancen stehen gut, dass ihr damit einen Risikostatus bekommt.
Bitte die App nicht deinstallieren! Das hilft nicht, und ihr verliert die Möglichkeit, über Risiko-Begegnungen der letzten 2 Wochen informiert zu werden.

Eine nachhaltige Lösung ist in Aussicht, möglicherweise schon in der nächsten Woche - auch wenn sich keiner der Offiziellen hier festlegen möchte.

vaubaehn on 15 Oct 2020

👍5

Ursache 3 (39508)
Device: SM-A300FU
Android: 6.0.1
App: 1.3.1 updated on 24.09.2020
Last risk checking was done at 8.OCT 6:17
Closing the App for more than 24 hours didn't help.

dieLouisa on 16 Oct 2020

Ursache 3 (39508)
Device: Gigaset GS160
Android: 6.0
App: 1.3.1
Last risk checking was done at 2.OCT 2:05

HeHigigaset on 16 Oct 2020

@vaubaehn We are aware of the increasing reports here. The reason that there are more reports is probably because we changed the 39508 FAQ entry that now recommends people to directly comment in this issue instead of opening a new one. Therefore, the threshold to report the bug is much lower, but the amount of people who are affected should (hopefully) be the same. The extend of the problem just becomes more visible.

Corona-Warn-App Open Source Team

heinezen on 16 Oct 2020

I'm also affected by this bug since several weeks and can't check my risk status.

Until now I was waiting for the CWA 1.4.0 release with https://github.com/corona-warn-app/cwa-app-android/pull/1088, because it was announced that this should fix the bug, see @svengabr 's comment in https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-683748329 (#1041 was reverted, see https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-691653482)

Now CWA 1.5.0 is released https://github.com/corona-warn-app/cwa-app-android/releases/tag/1.5.0, but there is no CWA 1.4.0 release.

Can someone please give an update of the current status:

Is the fix ready or not?
Is #1088 still the relevant fix or are there also others?
When will 1.5.0 be available in the App Store?
Out of curiosity: What happened with CWA 1.4.0? Is it skipped?

@heinezen

Therefore, the threshold to report the bug is much lower, but the amount of people who are affected should (hopefully) be the same.

The threshold to report the bug here is still very high - there's a need for a GitHub account. So I would assume that a lot more people are affected by this bug additionally to the people reporting here (and these are a lot as you can see).

I would appreciate a clear communication regarding the status of this issue. https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-683748329 was such a clear statement, but it's not up-to-date anymore and there was no update from the CWA team since then as far as I can see.

pathmapper on 17 Oct 2020

👍5

Hallo,
die Corona warn app zeigt den Fehler 39508 seit dem 3.10. Gerät ausschalten - einschalten bringt nix. Risikoermittlung über Nacht ausschalten, Gerät mit Strom und Internet verbinden und am nächsten Morgen die Risikoermittlung wieder einschalten zur Aktualisierung bringt auch nix , nur einen weiteren Fehler : 9002 Time out waiting for 60000ms.
Device: Samsung A3
Android 6.01
CWA: 1.3.1
Letzte Risikoermittlung : 3.10. 4:33
Was nun?

Laura392 on 17 Oct 2020

Bei mir ist es genauso wie bei Laura 392.

BN72 on 17 Oct 2020

Auch bei mir heute 9002 und 39508. Ebenfalls Android 6.0.1
Als die App das Timeout 9002 zeigte, wechselte ich zum Google-Teil und sah 14 saubere Zeilen im Protokoll, alle mit demselben Timestamp. Zurück zur App: Fehler 39508, und im Protokoll waren sechs Zeilen hinzugekommen.
Gewissermaßen ist alles ok: Die Vergleiche der Serverdaten mit den gesammelten Schlüsseln wurden alle durchgeführt, und an "Anzahl der Treffer"=0 kann ich sehen, dass keine Risikobegegnung dabei war.

@heinezen
Es wird offenbar immer schwerer für alte Smartphones (Android 6) die Prüfungen in einer Minute durchzubekommen. Bei mir ging es gestern und heute nicht mehr.

kereng5 on 17 Oct 2020

Ich habe die komplette Prozedur durchprobiert.

Dann bekomm ich auch wie @kereng5 den Fehler 9002 und die Meldung, dass der Timeout von 60000ms abgelaufen war. Im Protokoll waren 11 Einträge. Der nächste Versuch schlug dann natürlich mit Fehler 39508 fehl. Das Protokoll hatte danach nun 20 Einträge.

AnOtherMuenchner on 17 Oct 2020

Auch bei mir heute zum ersten mal 9002: timed out while waiting 60000 ms bei App im Vordergrund.

Komischerweise war ich nicht überrascht.
Danach auch bei mir 39508.

vaubaehn on 17 Oct 2020

@pathmapper

Can someone please give an update of the current status:

Is the fix ready or not?

Yes, the fix is ready and included in CWA 1.5.

Is #1088 still the relevant fix or are there also others?

1088 has been superseded by https://github.com/corona-warn-app/cwa-app-android/pull/1150 which does the same, but additionally implements a branching logic to catch older ENF versions afaiu.

Another relevant fix coming with 1.5 is https://github.com/corona-warn-app/cwa-app-android/pull/1138 which increases the timeout limits and therefore should help with the (silent) 9002 timeout errors which often lead to the 39508 issue discussed here.

When will 1.5.0 be available in the App Store?

Currently it's announced for the coming Monday: 2020-10-19 🤞

Out of curiosity: What happened with CWA 1.4.0? Is it skipped?

Yes, 1.4 was skipped.

daimpi on 17 Oct 2020

👍5 🚀2

Ich habe auch schon seit Ende September immer mal wieder undin immer länger den Fehler 39508. Workaround mit Risikoermittlung über Nacht ausschalten hat erst funktioniert, aber jetzt bekomme ich auch immer den 9002.

Huawei P8 lite
Android 6.01

JoFriede on 17 Oct 2020

App-Version 1.3.1
Android 6.0.1
Handy Samsung SM-J500FN

Seit nummehr 47 Tagen immer wieder Fehler 39508.
In dieser Zeit waren nur 4 Aktauliserungen des Risikostatus möglich Die ersten 3 nur nach Öffnen der App. Die letzte erfolgte am 08.10., nachdem ich alle auf https://www.coronawarn.app/de/faq/ angegebenen Schritte 2 mal erledigt habe. Seitdem tut sich gar nichts mehr! Selbst 4 Tage am Stück die App geschlossen halten hat nichts bewirkt. Also seit 9 Tagen völlige Unkenntnis meines Risikostatus.
Da dieser Fehler offensichtlich bei sehr vielen Handys auftritt, ist in diesem Zustand die App keine Hilfe sondern eine Gefahr!!! Normale Handynutzer ohne Vorkennrtnisse sind schon mit dem Anstoßen von Updates ihrer Apps überfordert geschweige denn mit dem Eröffnen eines Githubs und laufen womöglich tagelang ungewarnt als Superspreader herum.

arniechem on 17 Oct 2020

No more updates since 07.10. Daily error 39508
Model: SM-G903F
Android: 6.0.1
CWA: 1.3.1
GPS was updated to 20.39.15 on 06.10 , i.e. on the day before last successfull update

DieterHelmutGreiner on 17 Oct 2020

No updates since October 8. Restarting the app or the phone does nothing
CWA: 1.3.1
Android 6.0.1
Samsung GT-i9195

anApeThrummingAViola on 17 Oct 2020

Seit dem 7.10. (letzte erfolgreiche Aktualisierung) kann die Corona-Warn-App den Risikostatus nicht mehr aktualisieren. Trotzdem finde ich nach dem Aufruf der Corona-Warn-App gleich darauf unter (Android 9.0) Einstellungen -> Google -> Covid-19-Benachrichtigungen die Meldung, dass zur Uhrzeit des Aufrufs der Corona-Warn-App die letzte Überprüfung auf eine mögliche Begegnung mit einer infizierten Person stattgefunden habe. Es wird auch täglich von den Covid-19-Benachrichtigungen eine neue Zahl (derzeit so um die 300) gemeldet, wieviele Überprüfungen die letzten 14 Tage stattgefunden hätten. Von der Corona-Warn-App (Version 1.3.1) bekomme ich dagegen nur die timeout-Meldung und die Fehlermeldung 39508. Handy: XGODY Mate30

ghost on 17 Oct 2020

No more updates since 09. October / Daily error 39508
Model: Samsung Galaxy S5 Neo (G903F)
Android: 6.0.1
CWA: 1.3.1

ThBexx on 17 Oct 2020

Same issue - not opening the app for 24 hours didn't help, the issue persists. (since 12/10):

Device name: HTC One M8
Android version: 6.0.1
CWA App version: 1.3.1

Spring2010 on 17 Oct 2020

Fehlermeldung seit einigen Tagen.
Daraufhin neuer Download der App.
Weiter Fehlermeldung.
LG X screen
Android 6.0.1
CWA 1.3.1

appdummy on 18 Oct 2020

Dear ladies and gents,
it is pretty inconvenient to report this bug here, if you are not a member of the IT-family.
Ordinary people will just give up reporting this bug, because you need an account here and have to be familiar with commenting etc..
Funny idea to place the link to github in the CWA faq. Instead please write there, that the update on Oct 19th should help (if this is true). And if not, it should get easier for users to report their bugs...
Living and working within Risikogebiete means, we rely on CWA. This implies that bug fixing needs to be quick, transparent, and bugs easy to report...
Thanks!

appdummy on 18 Oct 2020

👍4 ❤3

Fehler 39508:
Device: ALE-L21
Android: 6.0
Corona App. 1.3.1
Ein Aufrufen der App ist auch über Tage hinweg nicht möglich. letzter Versuch: 18.10.2020 ca. 10:30.

blauewildblume on 18 Oct 2020

Auch bei mir gibt es Probleme mit der Google API. Nach 20 Versuchen mit unterschiedlichen Anzahlung von Schlüsseln wird abgebrochen.
Samsung Galaxie S5 minni SM-G800f
Andrid 6.0.1
CWA 1.3.1

Ich kann generell nicht verstehen, warum eine solche Kommunikation aufgebaut wird. Warum schickt man nicht seine gesammelten Schlüssel zu einem Server. Dieser kontrolliert und stellt ein Ergebnis zur Verfügung.
Als erste Hilfe sollte schon mal ein Button zur erneuten Abfrage reichen.

Schönen Gruß

schneik1 on 18 Oct 2020

Living and working within Risikogebiete means, we rely on CWA. This implies that bug fixing needs to be quick, transparent, and bugs easy to report...

It is not only a question of living in "Risikogebiete" because the app does not work anywhere in Germany. Although of course, a correct functionality in these areas would be more important that on a village far from everything.

I still do not understand why a serious bug which is known since august isn't solved about 2 months later in october or at least why the fix is not already delivered to the user. For me, this is "grob fahrlässig". Also in front of that the situation which shall be improved by the app is getting worse and worse every day since all the time.

AnOtherMuenchner on 18 Oct 2020

Ich habe die Fehlermeldung seit einigen Wochen. Erst hat die CWA dann wieder funktioniert, jetzt ist es entgültig aus. Auch die 24 Stunden Pause hat nichts gebracht:
Samsung S5, SM-G901F
Android 6.0.1
CWA 1.3.1

Martine-J on 18 Oct 2020

👍1

@AnOtherMuenchner Please read #1021(comment).

When will 1.5.0 be available in the App Store?

Currently it's announced for the coming Monday: 2020-10-19 🤞

Just wait...

Nils6852 on 18 Oct 2020

👍1

I'm joining the queue.
Error 39508, Risiko-Ermittlung zuletzt aktualisiert 15 Okt.
24h pause did not solve the problem this time, the last time it did.

Device: Xperia Z3 compact
Android: 6.0.1
Corona App. 1.3.1

jmbaldwin on 18 Oct 2020

Same Problem with my wife's and mine: "Etwas ist schiefgelaufen ... Excepotion 39508"
Samsung Galaxy S5neo SM-G903F
Android: 6.0.1 with latest updates / Kernel Version 3.10.61-14252124
CWA 1.3.1
"Letzte Risiko-Ermittlung" on Oct 11 and Oct 15 respectively

HaraldHajen on 18 Oct 2020

Ich habe die Fehlermeldung seit dem 9. Oktober 2020
Device: LG-K520
Android: 6.0.1
CAW: 1.3.1

mercartor on 19 Oct 2020

After initial problems, the app has been working without problems since installing version 1.3 in July or so.
Now "something went wrong" again, issue 39508 popping up, last successful risk assessment was on Oct. 8th.
24h "rest" didn't help.
Android 6.0.1
Samsung S5 neo SM G903F
App Version 1.3.1

cedei on 19 Oct 2020

Same issue at my phone since 9.10.2020:
Android 6.0.1
Samsung S5 neo SM G903F
App Version 1.3.1

webhoernchen on 19 Oct 2020

Android 6.0.1
OnePlus X (ONE E1003)
App Version 1.3.1

ChrWBlack on 19 Oct 2020

Hello everyone and thank you very much for your feedback.
This issue is about to be fixed in our new app release 1.5 which will be rolled out today.

Looking at this issue with over 180 comments I am closing the conversation right now.

Once 1.5 is available in the App Stores and we have the first results, I will re-open conversation here.

Best regards,
SG

Corona-Warn-App Open Source Team

svengabr on 19 Oct 2020

The new App version 1.5 is now officially available in the App Store / Play Store. Please update to the latest version.

I have re-opened the conversation here.

svengabr on 19 Oct 2020

👍1

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

Let me know if you need further information.

masema67 on 19 Oct 2020

@masema67 can you share the exposure checks log (like in the opening post) of the past ~3 days?

mlenkeit on 19 Oct 2020

@mlenkeit here you go:

{"timestamp":"19. Oktober 2020, 07:54","keyCount":11260,"matchesCount":0,"appName":"Corona-Warn","hash":"SdTEZwNHt0UO5ZrALV8cOLaktD8y7Jps+R5uZeMfPZI="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":16120,"matchesCount":0,"appName":"Corona-Warn","hash":"Y02bprOCbn0iF2mWuNxB7fHgr7TB3QVMavXuORKgjPw="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":21527,"matchesCount":0,"appName":"Corona-Warn","hash":"O1U95vn3KkRXQNUNAu3gUK8zlSDgXu2\/H9uIqa4ynHI="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":23618,"matchesCount":0,"appName":"Corona-Warn","hash":"VOq6FAOxQ1LW\/qlvvIuMC0MqCyzRAmLMYzJOxWM8yL0="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":26284,"matchesCount":0,"appName":"Corona-Warn","hash":"wwFDWRHe3jEWIhnREZnrIeedXYGqmo6V4cLB6LcrPOA="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":23657,"matchesCount":0,"appName":"Corona-Warn","hash":"FmksVqcKrN8X72caj6d58AoIbGv7R9aGOE+46lxx+4M="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":14649,"matchesCount":0,"appName":"Corona-Warn","hash":"OqxTm1BUzkIuVVkkJQ0s6ei9tDZSSjNmRW7nKa1MUbE="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":18134,"matchesCount":0,"appName":"Corona-Warn","hash":"qBoEuZ\/jjM\/tUO4eljKiHDNQx9+goBrxAT9uR6NtCZE="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":28218,"matchesCount":0,"appName":"Corona-Warn","hash":"61qbbpK1q7PO6ggH\/F3caEx80WrENuDNts7vuaAIIlo="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":11260,"matchesCount":0,"appName":"Corona-Warn","hash":"SdTEZwNHt0UO5ZrALV8cOLaktD8y7Jps+R5uZeMfPZI="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":16120,"matchesCount":0,"appName":"Corona-Warn","hash":"Y02bprOCbn0iF2mWuNxB7fHgr7TB3QVMavXuORKgjPw="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":21527,"matchesCount":0,"appName":"Corona-Warn","hash":"O1U95vn3KkRXQNUNAu3gUK8zlSDgXu2\/H9uIqa4ynHI="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":23618,"matchesCount":0,"appName":"Corona-Warn","hash":"VOq6FAOxQ1LW\/qlvvIuMC0MqCyzRAmLMYzJOxWM8yL0="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":26284,"matchesCount":0,"appName":"Corona-Warn","hash":"wwFDWRHe3jEWIhnREZnrIeedXYGqmo6V4cLB6LcrPOA="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":23657,"matchesCount":0,"appName":"Corona-Warn","hash":"FmksVqcKrN8X72caj6d58AoIbGv7R9aGOE+46lxx+4M="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":14649,"matchesCount":0,"appName":"Corona-Warn","hash":"OqxTm1BUzkIuVVkkJQ0s6ei9tDZSSjNmRW7nKa1MUbE="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":18134,"matchesCount":0,"appName":"Corona-Warn","hash":"qBoEuZ\/jjM\/tUO4eljKiHDNQx9+goBrxAT9uR6NtCZE="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":28218,"matchesCount":0,"appName":"Corona-Warn","hash":"61qbbpK1q7PO6ggH\/F3caEx80WrENuDNts7vuaAIIlo="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":34105,"matchesCount":0,"appName":"Corona-Warn","hash":"wnvqLcYE6GlPGoWbAj7A90fhyKkkPxKBImGrk\/8Ap4Y="},
{"timestamp":"19. Oktober 2020, 07:54","keyCount":41646,"matchesCount":0,"appName":"Corona-Warn","hash":"IJcGAZfoXfwKtmVoz7s4C5ZR9RO7nQcK0YuYNOcahpM="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":8845,"matchesCount":0,"appName":"Corona-Warn","hash":"WlPRGOqp9jGP0zru89529scVNEgKzr7Gr77PmWT4KhU="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":11260,"matchesCount":0,"appName":"Corona-Warn","hash":"SdTEZwNHt0UO5ZrALV8cOLaktD8y7Jps+R5uZeMfPZI="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":16120,"matchesCount":0,"appName":"Corona-Warn","hash":"Y02bprOCbn0iF2mWuNxB7fHgr7TB3QVMavXuORKgjPw="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":21527,"matchesCount":0,"appName":"Corona-Warn","hash":"O1U95vn3KkRXQNUNAu3gUK8zlSDgXu2\/H9uIqa4ynHI="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":23618,"matchesCount":0,"appName":"Corona-Warn","hash":"VOq6FAOxQ1LW\/qlvvIuMC0MqCyzRAmLMYzJOxWM8yL0="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":26284,"matchesCount":0,"appName":"Corona-Warn","hash":"wwFDWRHe3jEWIhnREZnrIeedXYGqmo6V4cLB6LcrPOA="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":23657,"matchesCount":0,"appName":"Corona-Warn","hash":"FmksVqcKrN8X72caj6d58AoIbGv7R9aGOE+46lxx+4M="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":14649,"matchesCount":0,"appName":"Corona-Warn","hash":"OqxTm1BUzkIuVVkkJQ0s6ei9tDZSSjNmRW7nKa1MUbE="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":18134,"matchesCount":0,"appName":"Corona-Warn","hash":"qBoEuZ\/jjM\/tUO4eljKiHDNQx9+goBrxAT9uR6NtCZE="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":28218,"matchesCount":0,"appName":"Corona-Warn","hash":"61qbbpK1q7PO6ggH\/F3caEx80WrENuDNts7vuaAIIlo="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":34105,"matchesCount":0,"appName":"Corona-Warn","hash":"wnvqLcYE6GlPGoWbAj7A90fhyKkkPxKBImGrk\/8Ap4Y="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":41646,"matchesCount":0,"appName":"Corona-Warn","hash":"IJcGAZfoXfwKtmVoz7s4C5ZR9RO7nQcK0YuYNOcahpM="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":43934,"matchesCount":0,"appName":"Corona-Warn","hash":"JWrd8IJXHSXZ2yRLhd5SCqiCKtEmE96gQz3Hv3NtIz8="},
{"timestamp":"18. Oktober 2020, 02:59","keyCount":16674,"matchesCount":0,"appName":"Corona-Warn","hash":"JU2g74zppJSAtobW56Jsi5pUcb7ItpT9XPAIZtKerhU="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":12380,"matchesCount":0,"appName":"Corona-Warn","hash":"soVm1mrjy2hY9ooOXUh0BDTg9+MJQ6Sak19WBGnOd18="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":8845,"matchesCount":0,"appName":"Corona-Warn","hash":"WlPRGOqp9jGP0zru89529scVNEgKzr7Gr77PmWT4KhU="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":11260,"matchesCount":0,"appName":"Corona-Warn","hash":"SdTEZwNHt0UO5ZrALV8cOLaktD8y7Jps+R5uZeMfPZI="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":16120,"matchesCount":0,"appName":"Corona-Warn","hash":"Y02bprOCbn0iF2mWuNxB7fHgr7TB3QVMavXuORKgjPw="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":21527,"matchesCount":0,"appName":"Corona-Warn","hash":"O1U95vn3KkRXQNUNAu3gUK8zlSDgXu2\/H9uIqa4ynHI="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":23618,"matchesCount":0,"appName":"Corona-Warn","hash":"VOq6FAOxQ1LW\/qlvvIuMC0MqCyzRAmLMYzJOxWM8yL0="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":26284,"matchesCount":0,"appName":"Corona-Warn","hash":"wwFDWRHe3jEWIhnREZnrIeedXYGqmo6V4cLB6LcrPOA="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":23657,"matchesCount":0,"appName":"Corona-Warn","hash":"FmksVqcKrN8X72caj6d58AoIbGv7R9aGOE+46lxx+4M="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":14649,"matchesCount":0,"appName":"Corona-Warn","hash":"OqxTm1BUzkIuVVkkJQ0s6ei9tDZSSjNmRW7nKa1MUbE="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":18134,"matchesCount":0,"appName":"Corona-Warn","hash":"qBoEuZ\/jjM\/tUO4eljKiHDNQx9+goBrxAT9uR6NtCZE="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":28218,"matchesCount":0,"appName":"Corona-Warn","hash":"61qbbpK1q7PO6ggH\/F3caEx80WrENuDNts7vuaAIIlo="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":34105,"matchesCount":0,"appName":"Corona-Warn","hash":"wnvqLcYE6GlPGoWbAj7A90fhyKkkPxKBImGrk\/8Ap4Y="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":41646,"matchesCount":0,"appName":"Corona-Warn","hash":"IJcGAZfoXfwKtmVoz7s4C5ZR9RO7nQcK0YuYNOcahpM="},
{"timestamp":"17. Oktober 2020, 02:42","keyCount":43934,"matchesCount":0,"appName":"Corona-Warn","hash":"JWrd8IJXHSXZ2yRLhd5SCqiCKtEmE96gQz3Hv3NtIz8="}]

masema67 on 19 Oct 2020

@masema67 thank you for sharing! The log suggests that the app tried to check for exposures already 20 times today (all at 07:54 am), which must have been the 1.3 release of CWA. With that, the quota for how often we can run an exposure check per day was already used up before the upgrade to 1.5.0 (which was available from 12:00 pm). That's most likely the reason why the error is still coming up. It should be gone tomorrow after 2:00 am (which is midnight UTC/GMT). If you still encounter the problem tomorrow, please let us know. If it's gone, we are of course also happy for any confirmation 😉

mlenkeit on 19 Oct 2020

👍2

@mlenkeit - okay I understood - will let you know the result tomorrow (yes today at 07:54 it was the 1.31 release)

masema67 on 19 Oct 2020

👍1

Well done so far!
I just uninstalled CWA 1.3.1. (didn't work properly anyway, so nothing to lose) and installed 1.5.
No worries any more since then 🍀.
LG X screen
Android 6.0.1

appdummy on 19 Oct 2020

😄1 👍1

@appdummy I'm glad to hear that it works for you now 🙂 🎉

I just uninstalled CWA 1.3.1. (didn't work properly anyway, so nothing to lose) and installed 1.5.

I would strongly advise against uninstalling CWA, as CWA will usually be the only Exposure Notification Framework (ENF) app on your phone, this will give ENF the signal to delete all the keys which your phone has recorded and sent over the last 14 days.

Even if you have had continuous 39508 errors, the keys were still recorded/sent by your phone and will be deleted if you un-/re-install CWA.
Instead I would suggest just waiting for the next rate-reset (every day at 02:00 CEST / 00:00 UTC) after updating to CWA 1.5 as suggested by @mlenkeit above.

daimpi on 19 Oct 2020

Thanks for answering, I do understand your recommendation.

It was just my individual decision, as I haven't had the app active often during the last 14 days - due to the message popping up in high frequency.
I decided to uninstall not to risk any complications by only updating and thus have it work properly now after all.
But this will not make sense for many other users, for sure!

It is not part of this issue, but what was going on my nerves in 1.3.1 and was solved by uninstall:
I had a negative test result (for sommer vacation, I was part of a lockdown 2 area...) uploaded and it loaded each and every time I started the app - and loaded soooo slowly that nothing else happened in the GUI. I could not find out how to kick out that test.
It might be helpful to have buttons to turn off tests, load new, actual ones etc. easily. Until now, laboratories do have their own apps. Which was helpful, as they report faster and offer the ability to load several tests (whole family, kids also, not only 1person per smartphone). These are points where I would appreciate enhancement for the CWA.

Thanks & greetings to the developers

appdummy on 19 Oct 2020

Today I installed Version 1.5.0 and got this error after the installation procedure.

willi-winzig on 19 Oct 2020

@willi-winzig could you wait until the rate reset happens at 02:00 CEST (00:00 UTC) and report back afterwards whether the problem persists?

daimpi on 19 Oct 2020

The problem persists after an upgrade.

Device name: Samsung Galaxy S10
Android version: 10
CWA App version: 1.5.0

sloede on 19 Oct 2020

@sloede same as above: could you wait until the rate reset happens at 02:00 CEST (00:00 UTC) and report back afterwards whether the problem persists?

daimpi on 19 Oct 2020

👍1

My suggestion for the next cwa version is that the app itself should suppress that exception in this situation.

willi-winzig on 19 Oct 2020

@willi-winzig
First of all: Congratulations on posting comment No. 200 in this thread 🎉 🥳

Ok kidding aside:

My suggestion for the next cwa version is that the app itself should suppress that exception in this situation.

I'm not sure whether this is actually a good idea. If this error at some later point reappears for whatever reason, we probably would want to know about this, right?

daimpi on 19 Oct 2020

🚀1 🎉1 👍1

Bei mir (S5 mini) funzt es nach dem heutigen Update. 👍

Dauer des Checks lag deutlich über einer Minute. Der Speicher der aufgezeichneten Schlüssel sollte dabei recht leer gewesen sein. Ich hoffe mal, dass im Fall des Falles der neue Timeout ausreichend ist. Auch wenn ich hoffe, dass dieser Test niemals eintritt.

AnOtherMuenchner on 19 Oct 2020

👍2

@appdummy

I had a negative test result (for sommer vacation, I was part of a lockdown 2 area...) uploaded and it loaded each and every time I started the app - and loaded soooo slowly that nothing else happened in the GUI. I could not find out how to kick out that test.
It might be helpful to have buttons to turn off tests, load new, actual ones etc. easily.

Usually you should be able to delete tests in CWA unless you're experiencing https://github.com/corona-warn-app/cwa-app-android/issues/1084? Also: I'm not aware that this would increase the startup time for CWA (I'm having #1084 for a long time already and my app starts very quickly). Were you stuck on a loading screen which looked like this or how exactly did the "slow loading" manifest itself?

Until now, laboratories do have their own apps. Which was helpful, as they report faster and offer the ability to load several tests (whole family, kids also, not only 1person per smartphone). These are points where I would appreciate enhancement for the CWA.

Regarding the ability to register multiple tests: the corresponding wishlist issue can be found here: https://github.com/corona-warn-app/cwa-wishlist/issues/109
Feel free to upvote 🙂

daimpi on 19 Oct 2020

Bei mir (S5 mini) funzt es nach dem heutigen Update. 👍

Dauer des Checks lag deutlich über einer Minute. Der Speicher der aufgezeichneten Schlüssel sollte dabei recht leer gewesen sein. Ich hoffe mal, dass im Fall des Falles der neue Timeout ausreichend ist. Auch wenn ich hoffe, dass dieser Test niemals eintritt.

Same here. After updating, exposure check works again and needed more than one minute.

JoFriede on 19 Oct 2020

@daimpi

Please correct me, if I am wrong: No native english speaker around? Everyone able to speak german?
I will continue in german (or a mix 😉) then.

Danke für den link auf die wishlist.
Kein #1084.
Das obere Fenster "Risikoermittlung" lud und verschluckte sich ständig mit #30598. Das Fenster "Testergebnis" darunter zog sich offenbar bei jedem Öffnen der App neu von irgendeinem Server das alte Testergebnis ("wird geladen" oder so ähnlich). Dieser Prozess dauerte jedes Mal LANGE. Ich habe keinen Button gefunden zum Löschen/reset auf blank oder so (oder habe ihn übersehen?).

So arbeiteten beide Fenster vor sich hin ohne erkennbaren Nutzen und mit #30598 hatte ich als bislang unvorgebildeter User nicht den Eindruck, dass da im Hintergrund noch etwas funktioniert (zudem im Bewusstsein: low budget smartphone, wenig Speicher, also diverse mögliche Fehlergründe meinerseits vermutet).
Ergebnis: Frustrationstoleranz erreicht, App geschlossen, verbleibende Energie lieber in Ansteckungsprävention im echten Leben gelenkt ;-)

appdummy on 19 Oct 2020

verbleibende Energie lieber in Ansteckungsprävention im echten Leben gelenkt ;-)

... und das ist sowieso die bessere und gesündere Variante.
Die App schützt nicht vor Ansteckung.

Alles Gute weitehin.

ndegendogo on 19 Oct 2020

@appdummy

Das Fenster "Testergebnis" darunter zog sich offenbar bei jedem Öffnen der App neu von irgendeinem Server das alte Testergebnis ("wird geladen" oder so ähnlich).

Sah das beim "Testergebnis" etwa so aus? (Datenabruf… das Ergebnis wird aktualisiert)

Dieser Prozess dauerte jedes Mal LANGE. Ich habe keinen Button gefunden zum Löschen/reset auf blank oder so (oder habe ihn übersehen?).

Falls das so aussah: Hat dieses "loading-wheel" sich irgendwann aufgehört zu drehen und dir wurde dein Test angezeigt, oder lief das unendlich lang weiter?

daimpi on 19 Oct 2020

@daimpi
Hat sich irgendwann aufgehört zu drehen und zeigte das Ergebnis.
Dauerte aber so lange, dass ich die App meist wieder geschlossen habe zugunsten anderer Apps, bevor das Testergebnis geladen war. Zusammen mit der anderen exception sah das für mich quasi wie eine App aus, die sich aufgehängt hat.

appdummy on 19 Oct 2020

👍1

@appdummy oh wow, interessant, danke für die Info. Das ist in der Tat ein issue das ich bisher noch nicht gesehen habe… Falls das nochmal auftreten sollte, mach gerne ein issue dafür auf 🙂.

daimpi on 19 Oct 2020

@daimpi
😉 Ich meld mich dann.
...hopefully it won't show up.

appdummy on 20 Oct 2020

👍1

@appdummy

...hopefully it won't show up.

Speaking of which 😈

Kannst du vll. mal testen ob du das Problem reproduzieren kannst, wenn du einen dieser QR codes hinzufügst?

Test1:
grafik

Test2:
grafik

daimpi on 20 Oct 2020

sloede same as above: could you wait until the rate reset happens at 02:00 CEST (00:00 UTC) and report back afterwards whether the problem persists?

I disabled the exposure logging around 01:00 CEST and only learned about the new version after I tried the usual re-activation past 02:00 CEST (I get 39508 since Oct 9th and tried the reset thing for about 4 days now, it never worked). After the failed update tonight I installed 1.5.0 now and tried again, unsuccessfully. Should I wait another day to try again?

Also, maybe I missed it as there are so many comments, how does the new timeout of three minutes handle higher key counts? The initial issue lists about 2-3k keys per check, mine usually reports about 10-30k, averaging 13k last time I checked the numbers. If 1 minute was not enough for 3k keys, do 3-10x as many keys stand a chance in 3 minutes? Or is the issue something else?

shoeffner on 20 Oct 2020

@shoeffner

Should I wait another day to try again?

Yes, that would be the best solution.

Also, maybe I missed it as there are so many comments, how does the new timeout of three minutes handle higher key counts? The initial issue lists about 2-3k keys per check, mine usually reports about 10-30k, averaging 13k last time I checked the numbers. If 1 minute was not enough for 3k keys, do 3-10x as many keys stand a chance in 3 minutes? Or is the issue something else?

The new timeout limit combined with a batched submission (instead of 14 single submissions) seems to be working fine even on lower end devices. There will be an even further extension of this timeout to 8 min coming with CWA 1.6 though.

Edit: I forgot: padding multiplier on the server side has also been dropped to 1, i.e. no unnecessary fake keys anymore 🎉. This will also help with decreasing the load on the whole infrastructure (from smartphones over networks to servers).

daimpi on 20 Oct 2020

Okay, then I will wait for tomorrow night, thank you.

shoeffner on 20 Oct 2020

👍1

mobile device: Pixel 3
Android version: 11 (Build RP1A.201005.004)
Corona App: 1.5.0

I have updated yesterday but the error persists (Cause: 3, 39508)
cwa2

PapaBravo on 20 Oct 2020

@sloede same as above: could you wait until the rate reset happens at 02:00 CEST (00:00 UTC) and report back afterwards whether the problem persists?

@daimpi Yep, I can confirm that the issue has been resolved. Kudos to the fast response time here!

sloede on 20 Oct 2020

🎉1

@willi-winzig could you wait until the rate reset happens at 02:00 CEST (00:00 UTC) and report back afterwards whether the problem persists?

Resolved 👍

willi-winzig on 20 Oct 2020

🎉1

Same issue at my phone since 9.10.2020:
Android 6.0.1
Samsung S5 neo SM G903F
App Version 1.3.1

Well done.
I have updated yesterday.
All fine today.

webhoernchen on 20 Oct 2020

🎉1

@PapaBravo

mobile device: Pixel 3
Android version: 11 (Build RP1A.201005.004)
Corona App: 1.5.0

I have updated yesterday but the error persists (Cause: 3, 39508)

Could you export your exposure check log and post here?
Settings > Google > COVID-19 exposure notifications > Exposure checks > Export exposure checks

MikeMcC399 on 20 Oct 2020

Unfortunately I have none left because I deleted all app data when trouble shooting yesterday.

I had zero exposure checks since then.

PapaBravo on 20 Oct 2020

As already mentioned in https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-712099886

It will take up to 24 hours until the rate limiting error is gone.

svengabr on 20 Oct 2020

👍1

That's why I mentioned "yesterday". I have updated yesterday around 2pm and that means I definitely had this reset time (2am UTC+2) but the error persists.

PapaBravo on 20 Oct 2020

👀1

For me as well: 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

DanielKroegerPriv on 20 Oct 2020

@DanielKroegerPriv there is a new App version available (1.5.0) which should resolve the issue. Please update and then see if it works tomorrow.

shoeffner on 20 Oct 2020

👍1

my suggestion for the next cwa version: You can avoid those questions and postings if you omit these exception-messages to the users within 24 h after an upgrade of cwa. This also help the user not to get confused about this error and/or deinstall the app. Only If these exceptions will occurs later, the message should appear.

willi-winzig on 20 Oct 2020

@PapaBravo could you test the following: set the clock in your device one day forward into the future (and disable automatic clock synchronization) and then open CWA again, to see whether the problem persists.
Please report your observations back to us here, TIA 🙂

daimpi on 20 Oct 2020

Galaxy S5 Neo
Android 6.0.1
App Version 1.5.0
Diese app ist völlig unbrauchbar. Sie ist seit wochen installiert. Auch schon deinstalliert und neu installiert. Irgendwann lief sie mal einige tage.
Dann wieer schluss. Probleme mit den "hilfen bzw ratschlägen". Seit stunden mache ich rum bis ich endlich hier gelandett bin. Und nur über zwischenakt auf pc.
Das ist doch alles nur pipppi kinderkram. Hat da jemand ahnung von algorythmus und k.i..
Wenn ich letzte 2 begriffe lese oder höre habe ichh niicht nur in diesen traurigen coronazeiten immer was zum lachen. Das alles taugt nur für kommerz und digitalkriiminelle. Usw usw.

CoronKnusper on 20 Oct 2020

👎1

@CoronKnusper
Verstehe ich das richtig, dass der Fehler bei dir auch nach dem Update auf CWA 1.5 weiterhin auftritt? Weißt du zufällig wann das Update auf CWA 1.5 bei dir stattgefunden hat?
Falls das update auf 1.5 erst heute war: Kannst du noch bis heute Nacht um 02:00 CEST (00:00 UTC) warten und dich danach nochmal melden ob das Problem dann behoben ist? Zu diesem Zeitpunkt sollte das rate-limit nämlich wieder zurückgesetzt werden.

daimpi on 20 Oct 2020

👍1

Yesterday's update to CWA 1.5.0 seems to have solved it; since this morning 39508 has not shown!
Thx to everybody involved!

Galaxy S5 Neo SM-G903F
Android 6.0.1
App Version 1.5.0

cedei on 20 Oct 2020

🎉1

Hi,
The 1.5.0 CWA update seems to have solved the problem. The app seems to be
working fine, as it did when it was installed at the end of August.
Hopefully the problem is solved now.
Thank you!

Samsung S5 SM-G901F
Android version 6.0.1
Error message (Cause:3 etc.) since October 10th

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#m_-3074646755462058895_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, 20 Oct 2020 at 14:17, cedei notifications@github.com wrote:

Yesterday's update to CWA 1.5.0 seems to have solved it; since this
morning 39508 has not shown!
Thx to everybody involved!

Galaxy S5 Neo SM-G903F
Android 6.0.1
App Version 1.5.0

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-android/issues/1021#issuecomment-712808041,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNMGZFF4APX3RLYDMRQUZDSLV5WTANCNFSM4P7K65OA
.

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Martine-J on 20 Oct 2020

🎉1

Happy to confirm that 1.5.0 has also fixed the error for me. :tada:

pathmapper on 20 Oct 2020

🎉2

Yesterday updated to CWA 1.5.0 (from the app store).
When I opened the updated app yesterday, still got the error 39508.
So I waited until this morning.
App updated at 02:03 am.
Now everything is working fine.
Thank you!

Gigaset GS160
Android 6.0
App Version 1.5.0

HeHigigaset on 20 Oct 2020

🎉1

@daimpi I finally got arond to your suggestion. Setting the time of the phone into the future changed the error from 39508 back to 10 (public key issue).
Otherwise the problem persists.

PapaBravo on 20 Oct 2020

👍1

@PapaBravo I'll quote my reply from here:

you're probably encountering #1304.

To quote @thomasaugsten:

The issue is related to Android 11 and GMS. 20.26.XX it will fixed in the next Google Play Service release

Which Google Play Service version do you have?

daimpi on 20 Oct 2020

Cause 3.

Gerät: OnePlus 7 Pro
OS: Android 10 (Oxygen OS 10.0.7.GM21BA)
App-Version: 1.5.0

DerKlabauter on 20 Oct 2020

Mit 1.5.0 funktioniert es auch auf meinem alten S5 mini mit Android 6.0.1

Gut gemacht, vielen Dank

Ich verstehe nur noch nicht warum die Überprüfung auf mögliche ... um ca. 2:00 beginnt und alle ca 45 Min. wiederholt wird, bis ich um 7:00 die App geöffnet habe.

schneik1 on 20 Oct 2020

🎉1

@DerKlabauter
Unfortunately the FAQ entry for 39508 doesn't explicitly say that after updating to CWA 1.5.0 you will need to wait until after 00:00 UTC (until the clocks change next weekend, that is 02:00 CEST) before the quota is cleared and the error no longer occurs.

Let us know tomorrow if you still see the problem.

MikeMcC399 on 20 Oct 2020

👍1

@schneik1 kannst du deinen EN log hier posten (nach dem exportieren die Endung einfach von .json zu .txt ändern, dann kannst du das hier hochladen).

daimpi on 20 Oct 2020

@daimpi My Play Services version is 20.39.15

PapaBravo on 20 Oct 2020

👍1

@PapaBravo thanks 🙂

@thomasaugsten

The issue is related to Android 11 and GMS. 20.26.XX it will fixed in the next Google Play Service release

shouldn't the issue (error 10) be fixed with 20.39.15? If not: do you know which version should fix this issue? Maybe it would make sense to reopen https://github.com/corona-warn-app/cwa-app-android/issues/1304 until then?

daimpi on 20 Oct 2020

👍1

@thomasaugsten
Do we have additional info about the root cause of 10 'no public key found'? Is it a problem parsing the DK files?

vaubaehn on 20 Oct 2020

👍1

I have the same problem (it doesn't work properly since april, and I keep hoping that updates will solve the problem...).

Updated 1.5.0 yesterday around 2pm, opened app for the first time since then today at 11pm (more than 24 hours later). Nothing has changed, the error remains: "Ursache: 3 Etwas ist schiefgelaufen". It also says "Ihr Risikostatus: Risiko-Ermittlung nicht möglich. Ihre Risiko-Ermittlung konnte seit mehr als 24 Stunden nicht aktualisiert werden. Letzte Ermittlung: Niedriges Risiko. Aktualisiert: 22. Sep., 02:00. Risiko-Ermittlung einschalten." Risiko-Ermittlung is active, though.

I don't have mobile internet, only WLAN while I'm at home. Is this a problem? Bluetooth does work. Background activity is allowed. No power saving mode active.

Device Name: LG Magna
Android Version: 6.0
CWA App Version: 1.5.0

Google Play-Services Version: 20.39.15
all-exposure-checks.txt

LSDJGLKJG on 20 Oct 2020

@LSDJGLKJG
could you maybe try what I proposed above:

Before you go to bed tonight, de-activate "Exposure-Logging" in CWA
When you wake up tomorrow, make sure that your phone is plugged into a charger
Open CWA and activate "Exposure-Logging" while being plugged into a charger
CWA should now try to perform an update, keep it for at least ~3 min in the foreground for this update to conclude
Check whether the error has disappeared

The basic idea is the same as in my post above: we're trying to get CWA to perform the update while having optimal conditions (power plugged in, no battery savings, foreground task) and then check whether the problem disappears.

daimpi on 21 Oct 2020

@LSDJGLKJG looking at your EN log I think you're probably still experiencing a (silent) 9002 timeout after 180s.

Check No. | timestamp | keyCount | hash
-- | -- | -- | --
20 | 20.10.2020 12:11 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
19 | 20.10.2020 11:58 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
18 | 20.10.2020 11:08 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
17 | 20.10.2020 10:33 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
16 | 20.10.2020 10:09 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
15 | 20.10.2020 09:56 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
14 | 20.10.2020 09:12 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
13 | 20.10.2020 08:35 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
12 | 20.10.2020 08:06 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
11 | 20.10.2020 07:53 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
10 | 20.10.2020 07:07 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
9 | 20.10.2020 06:30 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
8 | 20.10.2020 06:08 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
7 | 20.10.2020 05:53 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
6 | 20.10.2020 05:03 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
5 | 20.10.2020 04:21 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
4 | 20.10.2020 03:57 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
3 | 20.10.2020 03:42 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
2 | 20.10.2020 02:52 | 319766 | YH6YsV03Cf/G7dd0TgoAncmlUu0XXz0Gbv3zDxMgpBY=
1 | 20.10.2020 02:08 | 313380 | 0MC2QI0b2GU7MU/18WvjGGAa3/wKu1oCVAF4ygsNEVM=

The good news is that the timeout extension (from 3 min to 8 min) will already come with the CWA 1.5.1 hotfix.
Also: given that the padding multiplier has been reduced to 1, packages are much smaller now (despite the fact that we also have federation roaming) and as the old large packages are continuously dropping out of the 14 day window, the load on the phones will hopefully decrease further.

daimpi on 21 Oct 2020

Hi @LSDJGLKJG ,

Nothing has changed, the error remains: "Ursache: 3 Etwas ist schiefgelaufen".

could you please try to describe the error message as precise and detailed as possible? For that, you could click on 'details' of the message box with the error. You may also take a screenshot of the message and post it here.

(@daimpi : if it's really "cause: 3", then sounds more like ENF-API problem (API10?), "timed out" would be "cause 9002")

vaubaehn on 21 Oct 2020

@vaubaehn are we talking about @LSDJGLKJG or @PapaBravo ?

Former looks to me like a classical case of silent 9002 timeout (now instead of 60s presumably after 180s), while the latter seems to be a case of API (10), no?

daimpi on 21 Oct 2020

@daimpi we are actually talking about @LSDJGLKJG :+1:

According to ENF log, API call counter and GoogleQuotaCounter in CWA must already have been reset for the new day for entry 1.
there were 20 calls all over the day. Because CWA 1.5.0 now has a (working) GoogleQuotaCalculator, there should be no more API39508.
If there was a timeout, the reported error should be Cause 9002, and not Cause 3
Reported Cause 3 points to ENF, and as API39508 should be excepted, only API 10 remains.

But I'm not sure, this is why I asked for more error details :)

vaubaehn on 21 Oct 2020

Version 1.5.0 helped me out after 24h wait. Thanks alot for fast fix and good handling.

DanielKroegerPriv on 21 Oct 2020

🎉1 👍1

still receiving the "CAUSE: 3 Something went wrong. ApiException: 39508" message on my

Samsung S5neo
Android 6
CWA 1.5.0

Screenshot_20201021-131336

vthomw on 21 Oct 2020

@vthomw Have the same error message every time I open this app.

Xiaomi 8a, MIUI 11.0.1 (Android 10)
CWA 1.5.0

ka223 on 21 Oct 2020

I guess I have to wait 24 hours with the app closed .. lets see what happens tomorrow.

vthomw on 21 Oct 2020

👍1

@vaubaehn Thanks, thb I'm wasn't entirely familiar with all the details of the new 1.5 approach. A few questions for my understanding:

According to ENF log, API call counter and GoogleQuotaCounter in CWA must already have been reset for the new day for entry 1.

Do you infer this from the timestamp being after 00:00 UTC, or something else?

there were 20 calls all over the day. Because CWA 1.5.0 now has a (working) GoogleQuotaCalculator, there should be no more API39508.

I totally forgot that CWA now has a quota calculator, that's cool 👍. Yes you're right this should actually prevent 39508 if it was working correctly 🤔.

If there was a timeout, the reported error should be Cause 9002, and not Cause 3

Let's imagine the following scenario: a very slow device which is hitting the timeout limit of 3min. In this case there will be 20 times 9002 timeouts but they will not be "silent" b/c GoogleQuotaCounter prevents a 21st call which would trigger error 39508 which would cover up the 9002 error. Is this the correct reasoning?

Reported Cause 3 points to ENF, and as API39508 should be excepted, only API 10 remains.

But I'm not sure, this is why I asked for more error details :)

Good point, let's wait for more info from @LSDJGLKJG.

daimpi on 21 Oct 2020

Hey,
@daimpi I did not read your message until today, but something seems to have happened. I opened the app today, just now, and everything is working fine. It says it updated today at 2:23.
The log says there were only two encounters today, which is possible, as I only did a short trip to the supermarket. And I didn't see my flatmates today. Is it possible that my app (or my phone...) is unable to cope with too many encounters in one day? And that there are too many encounters if I spend the whole day with one of my flatmates who has the app as well?

I will just wait and see how it goes over the next few days, I guess.

LSDJGLKJG on 21 Oct 2020

🎉3

@vaubaehn Sorry that I can't give you more error details, now that the error seems to fixed.

LSDJGLKJG on 21 Oct 2020

@LSDJGLKJG great that it seems to be working for you now 👍 🙂

Could you maybe share your EN log from today as well, just for comparison?

The log says there were only two encounters today,

Could you share a screenshot of this?

Is it possible that my app (or my phone...) is unable to cope with too many encounters in one day? And that there are too many encounters if I spend the whole day with one of my flatmates who has the app as well?

Unlikely. The real computational cost seems to come from the expansion of diagnosis Keys (via @mh-) :

The expensive operation is AES, not the 16 byte comparison.

We recently had a detailed discussion on this topic in the community Slack if you're interested to learn more 🙂.

I will just wait and see how it goes over the next few days, I guess.

Sounds good, let us know how it goes 🙂.

daimpi on 21 Oct 2020

Alright, here it is:
all-exposure-checks.txt

LSDJGLKJG on 21 Oct 2020

👍1

I had the same problem error#39508.
I have updated the App yesterday and keep it closed for nearly 24 hours.
Now I have reopened it again and the bug is done! The information screen shows the correct days and state.
I am satisfied. Congratulations for this fix👍!

Erbsenklemmer on 21 Oct 2020

🎉3

Yesterday updated to CWA 1.5.0 (from the app store).
When I opened the updated app yesterday, still got the error 39508.
So I waited until this morning.
App updated at 02:03 am.
Now everything is working fine.
Thank you!

Gigaset GS160
Android 6.0
App Version 1.5.0

Same with my phone 😀 it's working now.
Samsung SM-A300FU
Android 6.0.1
App Version 1.5.0

Thank you!

dieLouisa on 21 Oct 2020

🎉3

The update solved my problem. After about six weeks I can check the risk status again.

Samsung Galaxy S5 mini (SM-G800F)
Android 6.0.1

BN72 on 22 Oct 2020

👍3

@daimpi @vaubaehn

I totally forgot that CWA now has a quota calculator, that's cool +1. Yes you're right this should actually prevent 39508 if it was working correctly thinking.

The quota calculator is currently not armed. It tracks the quota and can be armed in a future update while already knowing the correct values, but currently it will not prevent submission to the ENF. This decision was made to not accidentally hide an underlying issue, as the quota of 20 calls should be enough on 95% of devices, those that have the newer ENF, where we can submit all files in one call. We should not be able to reach the quota limit :thinking: .

d4rken on 22 Oct 2020

👍2

Works fine today, too. I'm really happy.

LSDJGLKJG on 22 Oct 2020

👍3

@d4rken thanks for clarifying 🙂.

Did you see my post above? There @LSDJGLKJG's phone actually hit the limit of 20 calls.

My guess was that this was caused by silent 9002 timeouts, as this is something we have seen before the release of CWA 1.5 with low powered devices. What I'm wondering: if CWA gets the timeout, will it next time again submit the whole package of DKs to ENF, or will it only submit the "rest" which hasn't been processed yet? Because if it every time submits everything again, what is stopping it from timing out on every submission and then retrying again? If this happens it's easy to hit the limit of 20 calls. Does this make sense?

daimpi on 22 Oct 2020

👍1

Did you see my post above? There @LSDJGLKJG's phone actually hit the limit of 20 calls.

I missed that. I currently don't why it would retry this often.
Assuming there may be an exception being thrown, the retry timing does not seem to fit the "retry" behavior specified in https://github.com/corona-warn-app/cwa-app-android/blob/master/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/worker/BackgroundWorkBuilder.kt
Though this retry mechanism kicking in because the whole transaction failed, is AFAICT the only reason it would repeat so often.

My guess was that this was caused by silent 9002 timeouts, as this is something we have seen before the release of CWA 1.5 with low powered devices. What I'm wondering: if CWA gets the timeout, will it next time again submit the whole package of DKs to ENF, or will it only submit the "rest" which hasn't been processed yet?

It will submit all available (those in the cache) packages. If only the download times out for a few files and the transaction timeout it not reached, it will continue with those files that are available. So even if a few downloads timeout each time, even a slow device/network should eventually have and submit all files, if at least one download completes per attempt.

At least one key package has to have been downloaded because the DefaultDiagnosisKeyProvider would have skipped the submission if the file list is empty.

Because if it every time submits everything again, what is stopping it from timing out on every submission and then retrying again? If this happens it's easy to hit the limit of 20 calls. Does this make sense?

That's theoretically possible, I'm just not sure what would lead to this. 20+ times in a row. Could the device be downloading files slow enough to reach 3 minute timeouts on every attempt? It's all on the same day too. So there would have to be a least one valid existing file, and in 20 attempts it never manages to download all existing ones, so a success ratio below 1 per attempt. As it seems to be fixed, maybe that was the case :thinking:.

The timeout increase in the hotfix should improve this behavior. Would arming the quota calculator have helped here? It would only have hidden the issue, wouldn't it?

@LSDJGLKJG Wifi at home? 4G?

d4rken on 22 Oct 2020

👍1

@d4rken @vaubaehn thanks for the detailed explanations (also over at https://github.com/corona-warn-app/cwa-app-android/issues/1187). I'm still trying to fully wrap my head around everything, but this helps a lot 😊 ❤️.

Regarding

Would arming the quota calculator have helped here? It would only have hidden the issue, wouldn't it?

Yes I would think so too.

@schneik1 reported a similar story wrt multiple checks above (just that theirs didn't go all the way to 39508):

Mit 1.5.0 funktioniert es auch auf meinem alten S5 mini mit Android 6.0.1

Gut gemacht, vielen Dank

Ich verstehe nur noch nicht warum die Überprüfung auf mögliche ... um ca. 2:00 beginnt und alle ca 45 Min. wiederholt wird, bis ich um 7:00 die App geöffnet habe.

but unfortunately their log seems to have been corrupted, so I couldn't check this yet.

@schneik1 könntest du einen neuen log für uns hochladen, da dein alter scheinbar beschädigt ist? TIA 🙂

daimpi on 22 Oct 2020

Yes, @schneik1 , a new ENF log would be nice. The other one looks a bit fishy to me. :fish:

vaubaehn on 22 Oct 2020

😄1 👍1

@vaubaehn well actually… 🤓
Dolphins are not fish.

Ok I'll see myself out 🏃 😂

daimpi on 22 Oct 2020

😄1

success .. update to 1.5.0 and a 24 hr wait fixed it. And my CWA still shows a green low risk.

vthomw on 22 Oct 2020

👍1

@daimpi Hier der 2.Versuch.
@vaubaehn Attached a new portion of fish :-)

Nach Installation von 1.5.0:
20.10. 2:17-7:20 15 Abfragen mit immer 319766 Schlüssel
21.10. 2:40-5:59 11 Abfragen mit immer 314522 Schlüssel
22.10. 3:03-3:48 4 Abfragen mit immer 307304 Schlüssel
Die Abfragen werden weniger.

Gruß
Schneik1

all-exposure-checks.txt

schneik1 on 22 Oct 2020

😄1 👍1

@schneik1 Super, vielen Dank! Nun fühle ich mich von einem ENF log geküsst, nicht von einem Delfin ;)

Schön, dass es jetzt funktioniert, aber eine Frage hätte ich trotzdem noch, weil das ENF log doch etwas merkwürdig aussieht: Wie oft öffnest du die Corona-Warn-App? 1x am Tag, alle paar Tage, 1x die Woche, oder seltener? Oder schaust du gerne in den Google-COVID-19-Benachrichtigungen rein, ohne die App zu öffnen?
Die Antwort auf die Frage könnte helfen zu verstehen, ob möglicherweise das Power Management von Android die mehrfachen Anfragen bedingen könnte.

vaubaehn on 22 Oct 2020

😄1 👍1

@schneik1 ... und noch ein paar weitere Fragen:

hattest du zwischendrin mal die App-Daten gelöscht?
wie verbindet sich dein Telefon nachts mit dem Internet: WLAN oder mobil (LTE/4G/3G)? Wie ist die Empfangsqualität am Standort des Telefons?
wie viel freier Speicher hat der interne Speicher deines Telefons (nur intern, nicht externe SD Karte)

vaubaehn on 22 Oct 2020

UPDATE
This bug has been fixed with the currently available version 1.5 of the Corona Warn App. We therefore ask you to update the app accordingly.

IMPORTANT:
After updating to version 1.5 it will take up to 24 hours until the error is gone.

Hello everyone,

we are happy to hear many positive feedback after updating to 1.5 but since this issue with over 300 comments is too bloated, it makes it really hard to seperate new issues. This is why I needed to lock this conversation.

I did create a follow up topic in case you are still receiving the same error after updating to 1.5

Thank you very much for your understanding.

Best regards,
SG

Corona-Warn-App Open Source Team

svengabr on 23 Oct 2020

Cwa-app-android: CAUSE: 3 Something went wrong. ApiException: 39508

Most helpful comment

All 271 comments

1088 is listed in the changelog for `1.4.0-SNAPSHOT-RC1`, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA `1.4.0` ?

1088 is listed in the changelog for `1.4.0-SNAPSHOT-RC1`, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA `1.4.0` ?

1041 has been reverted (in #1107) b/c there seemingly has been miscommunication by Google. It turns out, the correct time to use is UTC after all. This has since been rectified in the Google documentation as well:

1088 has been superseded by https://github.com/corona-warn-app/cwa-app-android/pull/1150 which does the same, but additionally implements a branching logic to catch older ENF versions afaiu.

Related issues

Cwa-app-android: CAUSE: 3 Something went wrong. ApiException: 39508

Most helpful comment

All 271 comments

1088 is listed in the changelog for 1.4.0-SNAPSHOT-RC1, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA 1.4.0 ?

1088 is listed in the changelog for 1.4.0-SNAPSHOT-RC1, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA 1.4.0 ?

1041 has been reverted (in #1107) b/c there seemingly has been miscommunication by Google. It turns out, the correct time to use is UTC after all. This has since been rectified in the Google documentation as well:

1088 has been superseded by https://github.com/corona-warn-app/cwa-app-android/pull/1150 which does the same, but additionally implements a branching logic to catch older ENF versions afaiu.

Related issues

1088 is listed in the changelog for `1.4.0-SNAPSHOT-RC1`, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA `1.4.0` ?

1088 is listed in the changelog for `1.4.0-SNAPSHOT-RC1`, but #1041 is missing and not listed in any changelog despite the PR is merged. Do you plan to include also #1041 for CWA `1.4.0` ?