corona-warn-app / cwa-app-android

Native Android app using the Apple/Google exposure notification API. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
2.44k stars 495 forks source link

Unusual multi-event (4) "red tile" / exposure risk notifications on CAT S61 vs. none on LG V20. #5787

Closed b2zer closed 1 year ago

b2zer commented 1 year ago

Technical details

Describe the bug

I have received a notification for a "red tile" / increased risk today (January 3rd, 2023) for my CATS61. The notification was sent to my smartwatch "as configured" (despite I haven't opened the cwa-app in weeks; guess authorization is not automatically revoked, which is good!).

The app shows a total of FOUR increased risk / red contact days: Jan. 1, Jan 2, Fri 30 Dec 22, Thu Dec 29. No warning for Saturday 31st.

Steps to reproduce the issue

Expected behaviour

Both phones or none of them reporting a "risk contact" with - presumably - a neighbor through a wall, especially as four contacts on four different days reported.

Additional context

I have adb installed on my desktop. If I can do anything to help (if this seems relevant), just "say the command" you want me to execute, and I'll send some logs, if applicable.


Internal Tracking ID: EXPOSUREAPP-14528

b2zer commented 1 year ago

Update: Now the notification arrived on the LG V20, too. Continuously from 29th December to 2nd of January (including) for every day. Still weird, but maybe it is my neighbor after all, then - and they only submitted the positive test to warn everybody after 11 pm today (previously the latest update for LG V20), but before 1 pm? Maybe it's not a bug after all, then, if such a delayed warning is possible.

larswmh commented 1 year ago

Thanks for your report @b2zer. We have created an internal ticket for it and will raise this topic internally. Internal Tracking ID: EXPOSUREAPP-14528


Corona-Warn-App Open Source Team

larswmh commented 1 year ago

@b2zer

According to internal feedback, such a delayed warning is possible. This is due to the fact that the two phones can download the exposure keys at different times. Because of this, this cannot be considered a bug, like you suggested in your most recent comment.

Feel free to comment again if you have any further questions. If you consider this to be solved, please close the issue.