Cwa-app-android: UI partially not updating when exposure check is run in the foreground

[crcsn]

Avoid duplicates

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

Describe the bug

The "Updated: Today, 06:33" part of the risk card on the main view does not update, when the exposure check is run in the foreground, i.e. when an update was not done in the last ~24 hours and the user opens the app, so that the exposure check is manually triggered.

I opened the app this morning, the check ran (visible in the UI), and afterwards the first two lines of the risk card updated correctly (in the first line, the number of exposures went up from 1 to 2 for me today; in the second line it read "Exposure logging permanently active" again after the check). In the third line, it still read "Updated: Yesterday, [time]" Closing and reopening the app updated the UI, so that it read "Updated: Today, 06:33". I noticed the same bug yesterday.

Expected behaviour

The "Updated" part of the UI should update immediately after the check is run in the foreground, as the other parts of the UI apparently do.

Steps to reproduce the issue

1. Put the app in a condition, where it needs to do a manual run of the exposure check.
2. Open the app.
3. Let the exposure check run.

Technical details

• Mobile device: Samsung Galaxy S10
• Android version: Android 10

Possible Fix

Additional context

[daimpi]

@crcsn
Your problems sounds very similar to https://github.com/corona-warn-app/cwa-app-android/issues/1081

In particular

The mainView/risk card is not completely refreshed
Internal Tracking ID: EXPOSUREAPP-2795

Do you agree? If so feel free to close this issue here and move the discussion over to https://github.com/corona-warn-app/cwa-app-android/issues/1081 🙂.

[crcsn]

@daimpi
true, that is indeed the same issue (EXPOSUREAPP-2795) that is _supposed_ to be discussed in the #1081

Will close this. Sorry for the duplication and thanks for the heads up! :)

[daimpi]

@crcsn no worries… it's hard to find the right one among the the plethora of issues 😅.