-
Notifications
You must be signed in to change notification settings - Fork 285
Wrong number of encounters --> matchescount 0 #1525
Comments
Dear @montoyav, Thank you for your post.
Thanks. Best wishes, Corona-Warn-App Open Source Team |
@dsarkar Thanks for your answer. I will have a look to the documentation. Iphone 6s Thank you very much |
Hi @montoyav and @dsarkar , The problem described by @montoyav could be connected to:
Cheers, v. |
Anyway, having a look to the iOS exposure log, there is something wrong: |
@vaubaehn no, I did not close my phone Friday 13th :-) and I also realised about this point "November 16, there have been 3 checks with 14 files: one in the morning hours, and two at noon" --> that I found strange... so good you confirm that this is not the expected behavior. |
No problem 🙂 However, I'll say good-bye at this point of my short joy ride to the iOS repo, as I don't have any clue of iOS so far. |
@vaubaehn thanks for your help! |
@montoyav, can you also upload a screenshot showing the 2 encounters in the CWA, please. Thanks |
@dsarkar here you have. Thanks! |
This is a problem on Apple's side. |
@Ein-Tim OK, thanks! I will do so and report if the problem was solved or not |
@montoyav Yes please, but you will have to wait until the next check is performed, the old encounters will not be shown in the log. (See #1106 (comment)) |
OK! I will do as suggested |
I have updated my iphone to iOS 14.2 and now I have in the CWA "no exposure up to now" in agreement with the matchCount = 0 Thanks for your help, was very useful |
Okay good @montoyav. If your question is answered, please close this Issue. One more request: |
@Ein-Tim Thanks a lot! I will do so |
Avoid duplicates
Describe the bug
Hey,
Yesterday I recognized "2 encounters with low risk".
Then I checked the json file and found all "matchescount" were 0
Today I checked again and it is the same. I used: https://felixlen.github.io/ena_log/
and this appears:
Bei Begegnungsüberprüfungen wurden keine Treffer mit positiv getester Person gefunden.
Has anyone the same issue?
Expected behaviour
I would expect 0 encounters
Best regards
Vanessa
The text was updated successfully, but these errors were encountered: