Google's log says "0 keys" after risk update

[nilsalex]

Avoid duplicates

• Bug is not mentioned in the FAQ
• Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
• Bug is not already reported in another issue

Describe the bug

Today at 00:01 the first check of keys via the API has been performed. The app indicates a successful risk update and says 'low risk'. What puzzles me is that the log in the Google settings says 'Anzahl der Schlüssel: 0'.

Expected behaviour

The log should say 'Anzahl der Schlüssel: n' with n being the number of keys pulled from the CDN. I expect the app to download keys and initiate a check via the API. If the log is correct, something went wrong. If the log is incorrect, this is another issue. But I can't know what is the case.

Steps to reproduce the issue

Open App, see that risk update has been made, check Google's log, see new (first) entry, check entry, see: 0 keys, 0 matches

Technical details

• Mobile device: Samsung Galaxy A50
• Android version: 10
• App version: 1.0.4

[nilsalex]

[MikeJayDee]

I'm trying to check this but I can't even find the "Details prüfen" screen you included. I can't find it in Settings->Google->COVID-19 Exposure Notifications. I'm using a Pixel 2 (fully updated) but would expect this to look the same for everybody as this is provided by Play Services.
@nilsalex - Can you let me know where in the menu you found this screen?

[nilsalex]

It seems that the log is not available in every Android version. For me, with Android 10, it is. For my girlfriend, with Android 9, it isn't.

I can access it by clicking on "Überprüfung auf mögliche Begegnungen" in the first screen and then on the entry "00:01" in the list.

[jmb-oddbook]

Exact same issue with Android 6.0.1 running on Sony Xperia Z3.

[MikeJayDee]

Thanks @nilsalex - I have Android 10; I guess that I may not have the current version of the API, which gets rolled out automatically but probably not simultaneously.

On the topic: note that iPhones appear to be showing that keys are being checked (since yesterday or so). So it is indeed odd that Android would show 0 keys being checked as the same files with keys to be checked is downloaded by Android and iPhone.

[w-flo]

Just 2 days ago, that button was missing from my "Google" phone settings. I have restarted my phone and a few hours later the button appeared, not sure if the reboot was related. Might just be an update rolling out to Android phones in phases these days.

In any case, I now have 3 updates in that log. One update yesterday, and 2 updates today.

There are 0 "Anzahl der Schlüssel" and 0 "Anzahl der Treffer" in all three of my log entries, just like in the screenshot above. I was wondering if "Anzahl der Schlüssel" refers to the number of "bluetooth contacts" registered by my phone, though it's unlikely since the API doesn't exchange the keys themselves via bluetooth as far as I know. I've noticed that calibrated RSSI values from logcat are in the -90 to -100 range even when I sit close to someone else while watching TV, and even when I put my phone on their desk for one hour and they keep their phone in their pocket while sitting at the desk, it's rarely "closer" than -80. So it's entirely possible that my phone has registered 0 "close enough" contacts even though I live with that person, since either my phone or their phone appears to have some calibration / hardware issues.

[jmb-oddbook]

Android 8.1.0 does not have the button "Überprüfung auf mögliche Begegnungen". The user cannot see the number of keys exchanged.

[jakobmoellerdev]

We are investigating and will update here once we analysed the subject accordingly.

[gizmo21]

Android 8.1.0 does not have the button "Überprüfung auf mögliche Begegnungen". The user cannot see the number of keys exchanged.

So doesn't my Android 6.0.1 - phone restart did not help.
Version of up-to-date Google Play Dienste is 20.12.17(040308-316502805)

Sorry for hijacking thread.

[fdellwing]

Moto One
Android 10
1. Juni 2020 Patch
1. Mai 2020 Google Play

[DooMMasteR]

Same issue here

Xiaomi Mi 8
MIUI 11.0.4.0
Android 10
1. April 2020 Patch
Play Services 20.21.17 (120400-316502805)

[MikeJayDee]

Is there anyone that has the menu on the phone, and where there the "number of keys" is more than 0 for any check?

[DooMMasteR]

I cannot check any other devices in my family, because none even have the menu to access the information. But they do all have the same Google Play Services installed.

[jakobmoellerdev]

The menu is coming from a GMS Update which is still not fully deployed to all devices yet. Also, the assumption is that the 0 keys are only a display bug and the key retrieval and matching are in fact working properly. I will update once this can be finally confirmed from our side.

[treysis]

There were screenshots on twitter showing one person who has received warning after husband was tested positive. But it was on iPhone...Android still doesn't allow screenshots.

[gizmo21]

Android 8.1.0 does not have the button "Überprüfung auf mögliche Begegnungen". The user cannot see the number of keys exchanged.

So doesn't my Android 6.0.1 - phone restart did not help.
Version of up-to-date Google Play Dienste is 20.12.17(040308-316502805)

Other Android 6.0.1 and here the menu point is at least available
Version of Google Play Dienst is
20.21.17(040400-316502805)
So on this device it has at least been deployed, as @jakobmoellersap said (thx for mentioning)

[jmb-oddbook]

On my Android 6.0.1 device the button is also there, see my first comment, but the keys are at 0.
Does your device show the number of keys checked @gizmo21 ?

[gizmo21]

Does your device show the number of keys checked @gizmo21 ?

On that button showing device there is no and won't be a CWA app, so just wanted to report the GPS version.

For that 0 key issue, the devs are on it so we'll just have to wait and perhaps Google has to fix that with an even newer service version :)

[juanaleon]

BlackBerry KeyOne, Android 8.1.0

The past three days there have been several transfers per day (3 just today), and all of them show "Number of Keys = 0"

It seems unlikely to be 'just' a display issue: why would the system attempt a transfer so many times each day?

Our iPhone got just one update two days ago, and shows 503 keys.

UPDATE

corona-warn-app/cwa-app-ios#778

From this iPhone thread I see that it is normal to have several requests every day. It is the expected behaviour, as each day the data of the past 14 days is retrieved again. This means the first day you have 1, then 2, then 3... onwards.

END OF UPDATE

[jakobmoellerdev]

This is not a display of a "transfer". This is about the calls for "provideDiagnosisKeys" of the Google API, as can also be deduced from the UI description. The number of keys is likely just a display bug as if no key packages were there, we would not even call the specified function "provideDiagnosisKeys". Since we do call this function (which would correlate to one UI entry), and we do not tamper with the packages, we can be sure it is the same key file package that is also used by iOS.

[DooMMasteR]

Is there any open issue on Googles end so far?
My experience with issue tracking on that far end are not… good.
Do you have a link to an issue on Googles Issue tracker or is this still speculation.

So far it could also be a handling issue and nothing is ever checked, not really reassuring.
Also: was this never tested?
Would be bad to get an update and have X amount of positive matches suddenly popping up.

[jakobmoellerdev]

@DooMMasteR I will recheck with Google to see if there is anything I can link to from here.

This was tested on our side and we were able to see the correct key packages being downloaded. Also on our Devices, we were able to see the correct key count with the productive setup while trying to replicate the behaviour. This could be related to some devices being whitelisted and showing up correct key counts while others do not, but we cannot fully guarantee this yet.

[DooMMasteR]

The fact that you can see the correct count, but many (I know no case that can) makes me wonder if the number 0 might be correct and there is nothing being checked on our devices.
Getting anything productive from Google alone is a privilege on your end, I guess, usually it feels like a dead end for many bugs and issues, that will eventually get fixed, but they offer about zero feedback down the road. Let us hope this gets sorted quickly because people might get the impression (might even be true) that the app is not working for them.
Also: I had one device, and for the lulz resetted it completely (factory) and set up the app again, but it now is not showing the insights anymore, so I guess the access to this feature is quite random at the moment and Google is using multiple versions, the devices had access to it before...

[jakobmoellerdev]

Regarding your comment of resetting the device: As stated previously in this issue, the rollout is probably not yet completed, and the device reset means that you also reset GMS to a version prior to the rollout of the functionality. I would thus not call the observed behaviour random but in fact expected, wouldn't you agree?

[DooMMasteR]

It got the COVID functionality back, but not the insights into the API calls, the Corona-Warn works just fine, but I cannot see the checks anymore (I could see them before) the stock GMS has no COVID functionality at all, since it is an Android 9 device. (I guess any phone to date would not have the APIs without any update).

Basically: the way Google handles their rollouts is random... the phone previously got the version with insights, now got one without :-)
My other phones have always had the insight, I never even knew there was one without this feature until I asked a friend about it.

[jeschket]

As you can see in my log-file below the keycount is 0 for all days (exept 25/26.07.2020). The CWA was installed on the rollout day, What you can also see is that the logs do not cover all the past 14 days (please note: my phone was carried around a lot during all the 14 days and no logs for several days are very unlikely).

Question: The keycount should be the same number for everyone each day as the keycount number should be equal to the number of postive-reports each day. Can someone confirm?

all-exposure-checks_t.txt

[MikeMcC399]

@jeschket

As you can see in my log-file below the keycount is 0 for all days (exept 25/26.07.2020).

As you noted in your edited comment, the newest risk updates have non-zero values, and this closed thread is about the problem of zero values, so the thread is not really relevant to your question.

I'm sorry that I don't know the explanation about varying "Number of keys" for the same day. If you don't get an answer here, you might try starting a new issue.

[mh-]

As you can see in my log-file below the keycount is 0 for all days (except 25/26.07.2020).

@jeschket
I think this means that you had old Google Play Services that would incorrectly record "0" until 24 July.
And now you have new Google Play Services, and everything is fine.
As explained here, searching for matches worked properly before as well. Only the recording of the number of keys was incorrect.

[MikeMcC399]

@jeschket

Question: The keycount should be the same number for everyone each day as the keycount number should be equal to the number of postive-reports each day. Can someone confirm?

I went back and read some of the documentation
https://developers.google.com/android/exposure-notifications/exposure-notifications-api and
https://github.com/corona-warn-app/cwa-documentation/blob/master/solution_architecture.md
and my understanding is that the risks are calculated using historical data split up by days. So the number of keys depends on what keys were relevant for a risk calculation on a particular day. (If I got this wrong, please feel free to correct me!)

https://github.com/corona-warn-app/cwa-documentation/blob/master/cwa-risk-assessment.md explains it nicely with an example.

The Google Exposure Notifications UI shows only the timestamp that the keys were received from the server, but it doesn't display the historical time period that the keys apply to. That would perhaps be a good enhancement suggestion for Google to add the missing information.

Update

This is now described in the FAQs.

[kereng5]

The Problem "Anzahl der Schlüssel 0" is back.

App Version 1.2.1
COVID-19-Benachrichtigungen Version 15202902003
Google Play-Dienste Version 20.26.14

I checked the numbers every day since July 23. Until yesterday there were 14 different numbers but today (timestamp August 17, 2020 09:39) all 14 numbers are 0.

[jmb-oddbook]

All systems green here.
Timestamp August 17, 2020, 3:30, shows lots of Keys checked, thankfully no match.

Specs:
Sony Xperia Z3 compact w/ Android 6.0.1
App Version 1.2.1
COVID-19-Benachrichtigungen Version 16203302004
Google Play-Dienste Version 20.26.14 (040306-320008519)

[daimpi]

@kereng5 could you export and share your exposure log? :)

[kereng5]

I exported what I think is the "exposure log" and got a .json-File which is not accepted here, so I saved it as .txt.
I did not activate the "priorisierte Hintergrundaktivität" but trigger the exposure check every day by looking into the app.
My phone is Motorola G3 with Android 6.0.1.

all-exposure-checks-1.txt

[mh-]

BTW, this app (“Warn-App-Companion”) https://play.google.com/store/apps/details?id=org.tosl.warnappcompanion might also be helpful for debugging, as it will show how many keys can be downloaded. (It needs root access, though.)

[kereng5]

Thank you, mh!
But granting root access seems too difficult for me.

[daimpi]

@kereng5
This is indeed very weird… I just spot checked a few hashes from your August 17th entries and compared them with mine and they were identical, just for me keyCount was always greater than 0.

Could you maybe check if the same behavior occurs again tomorrow?

My device:
Samsung Galaxy S8 (Android 9)
CWA 1.2.1
ENF v. 15202902003
Google Play Services: 20.26.14

• My log: me-17.zip

[mh-]

@kereng5 I modified the WarnAppCompanion app https://play.google.com/store/apps/details?id=org.tosl.warnappcompanion - starting with version 1.1.1, it will always least try to download the Diagnosis Keys, also without root access.
This might help to check whether a firewall prevents downloading them.

[kereng5]

Could you maybe check if the same behavior occurs again tomorrow?

Same as yesterday.
all-exposure-checks-2.txt

[kereng5]

version 1.1.1, it will always least try to download the Diagnosis Keys, also without root access.

I got the Diagnosis Keys. The numbers are 2500 for August 4, then 2325, 2095, 1935, 1820, 1780, 1575, 1450, 1190, 890, 680, 435, 285, 20, 0. The last one (0) for today.
How do I understand the 20 for August 17? I guess only 4 of yesterday's 56 reporters transferred their last Diagnosis Key to the server. And the 285? 56*5=280, so only one Diagnosis Key is from the 33 who reported positive on August 16, or some of the 56 had no old keys. (Data source https://micb25.github.io/dka/ )

[mh-]

@kereng5 Yesterday's keys (17 Aug 2020) can only be uploaded today. So they are part of the hourly packages that have been published today. As of right now I already see 50, so 50/5==10 users have already uploaded keys for yesterday.

[daimpi]

@mh- I'm not so sure that @kereng5 is missing any packages/downloads: when I was comparing hashes yesterday I found the same hashes as for my checks, even for the most recent package… I don't think that this would be possible w/o the package actually being downloaded. This seems to me to be a displaying error like we had before ENF 1.5…

[kereng5]

I can see key numbers again. all-exposure-checks-3.txt

Yesterday I noticed that there was not much internal memory free in my phone, and I deleted some pictures from camera and WhatsApp. I am not convinced that this is the reason. I would expect an error message if there is no space for the Diagnosis Keys.

Do the Diagnosis Keys need less space in companion app? There seems to be less redundancy.

edit: there is a new Version: 16203302004
amatenki had it already 2 days ago. I found it now on my phone.

[mh-]

@kereng5 I really don't know, in Warn-App-Companion I just download the Diagnosis Keys to RAM. The data downloaded from the server is probably also cached somewhere, but I think that cached data might be deleted automatically in low-disk-memory situations.
One major difference is that Warn-App-Companion makes no effort to download anything in the background, it only works when you start the app in the foreground. An OS usually gives priority to the foreground application.

[vanMacG]

Also this issue is closed and the FAQ says the problem is solved with newer google play services versions:
I saw the problem on my dads phone with recent CWA and play services, see screenshots. On top of that, it's not only a invalid display, but risk calculation is not performded correctly.
Should I create a new issue for this, or should it be tracked here?

[vaubaehn]

Hi @vanMacG ,
I found your comment by chance.
As the issue here is closed and as the observation on your dad's phone may have different reasons, I'd recommend to open a new issue.
We would need some more information then, like the phone model and Android version, and how long the app has already been installed.

[vanMacG]

@vaubaehn
Thank you for your comment. I will get the infos and post a new issue in the evening.

[vaubaehn]

@vanMacG
Great, thank you. What also would be good if you could check how much free space there still is on internal storage.