Cwa-app-ios: Key count has changed from 1 to 0
I think there must be something wrong here. Yesterday the app showed me I had 4 low risk encounters, after the latest update during the night it now shows I only had 1. I looked at the exposure checks (attached them here too) and it seems that yesterday one of the keys had a match count of 1 while today same key now has 0.
Is that a correct behavior? Anyone else has the same issue?
sebastiancomsa
All 5 comments
Yes. This happens, as soon as the match "expires", 14 days after the encounter.
Reason is that the RPI stored locally on your device have this lifetime. After this there will be no match.
For low-risk (green) encounters, unfortunately, you cannot see the date of encounter. In the ENF log you see only the matches with file granularity, corresponding to the day where a person uploaded her DEK keys.
ndegendogo
on 25 Oct 2020
@sebastiancomsa I second what @ndegendogo said above ^
A similar question was discussed here in some more detail if you're interested 馃檪.
daimpi
on 25 Oct 2020
Thanks a lot guys, sorry if it was a duplicate post.
Happy it's not a bug and should function like this.
KR,
Seb
sebastiancomsa
on 25 Oct 2020
@sebastiancomsa no worries 馃檪.
If you're satisfied with the answers and don't have any other questions, feel free to close the issue 馃檪.
daimpi
on 25 Oct 2020
Closes: #1404
sebastiancomsa
on 25 Oct 2020
Related issues
rainervonuns
路
3Comments
Hermann12
路
3Comments
mss1010
路
3Comments
Eisbaerhaar
路
3Comments
wandoliver
路
3Comments
Most helpful comment
Yes. This happens, as soon as the match "expires", 14 days after the encounter.
Reason is that the RPI stored locally on your device have this lifetime. After this there will be no match.
For low-risk (green) encounters, unfortunately, you cannot see the date of encounter. In the ENF log you see only the matches with file granularity, corresponding to the day where a person uploaded her DEK keys.