Cwa-app-android: 2147483647 Tage seit der letzten Begegnung

[carstenkowalzczek]

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

I had a high risk contact on November 17th. This mornig the app status was still red and showed
'15 Tage seit der letzten Risiko Begegnung'. After updating the risk status it shows
'2147483647 Tage seit der letzten Begegnung'

Expected behaviour

Steps to reproduce the issue

I did just open the app.

Technical details

• Mobile device: Galaxy S10
• Android version: 10
• Corona Warn App Version 1.7.1

Possible Fix

Additional context

---

Internal Tracking ID: EXPOSUREAPP-4255

[ndegendogo]

@dsarkar @svengabr seems your robot didn't pick up this one?

[vaubaehn]

2147483647 decimal is 32 bit binary 01111111 11111111 11111111 11111111. So probably a calculation was performed on a wrong persisted value.

Please forgive me in advance for kidding, I just can't resist:
Or did you indeed have an encounter 2147483647 days ago? I mean, that's around 6 million years ago, I would also have problems to remember who I met that day.

[ndegendogo]

probably a calculation was performed on a wrong persisted value.

@vaubaehn or a wrong datatype is also a good candidate for this kind of bug

[vaubaehn]

@ndegendogo : or both: wrong data type with a negative value (looks like this to me).
Maybe something similar like #1029 / #1082 which was related to tracing days?

[ndegendogo]

@vaubaehn 🤪🤪🤪

[Ein-Tim]

I came here because @ndegendogo linked to this Issue (normally I don't take the 🚆 to the Android Repo) but reading through this I have just one small question

@carstenkowalzczek:
Is the App still showing this number?

[dsarkar]

Dear @carstenkowalzczek, @ndegendogo, @Ein-Tim, @vaubaehn,

Thank you for your contributions and analysis. We have created a ticket for the bug in the internal Jira system. Any further developments will be notified here in this Github issue.

Best wishes,
DS

---

Corona-Warn-App Open Source Team
Internal Tracking ID: EXPOSUREAPP-4255

[dsarkar]

Issue of Google´s ENF, possibly mitigated with ENF 2.0, implemented in CWA 1.8

[ndegendogo]

@dsarkar very nice idea to indicate the planning for the fix in the headline. 🎉🎉

[MKTH2020]

My App shows the same issue on Android 9.

[dsarkar]

@MKTH2020, thanks for the feedback. Please, let us know

• CWA version 1.9.1?
• Device model/name
• Android 9
• More details: The day before, what did it show, the next day, and the day after.
• Screenshots if possible would be nice

Many thanks. Best wishes, DS

---

Corona-Warn-App Open Source Team

[MKTH2020]

Cwa 1.7.1
Sony Xperia
The Day before: High risk with correct Date and correct Test result
This morning: Bug showed
When I opened again a minute ago to look up the version number, it was already gone. App shows green again now.

[MKTH2020]

[MKTH2020]

[dsarkar]

@MKTH2020, thanks.
CWA 1.9.1 was released a few days ago. This issue should have been fixed in 1.9.1. Please update and we would appreciate your feedback if this issue was resolved for you and others. Thanks, DS

---

Corona-Warn-App Open Source Team

[MKTH2020]

Thanks. After the update, App shows Red again without showing a number of encounters.

[ndegendogo]

@MKTH2020 yes, cwa 1.9 is using the new improved risk calculation formula based on ENS v1.5 (Google) / ENF v2 (Apple).
This improved formula yields not number of encounters, but number of days with risky exposition (in your case: 1 day).

[heinezen]

Hey @carstenkowalzczek ,

We are getting positive feedback from users that the issue is fixed in CWA version 1.9 which just got released, so we will therefore close this issue. Please update to 1.9 if you haven't already. If the error stilloccurs, make a comment here and we will reopen the issue.

Regards,
CH

---

Corona-Warn-App Open Source Team