-
Notifications
You must be signed in to change notification settings - Fork 496
Risk status not updating after reopening backgrounded app #594
Comments
Hi @SoerenBusse , just to clarify: before putting the app to the background, it was showing "1 von 14 Tagen aktiv"? |
Hi @tkowark Exactly. It was showing "1 von 14 Tagen aktiv". I think this might be related to am Life Cycle issue where the number of days isn't correctly initialized and the default int value is beging shown. |
hi @SoerenBusse thank you for bringing this issue up. Could you please check on the date and time settings on phone if:
|
I can also reproduce the issue on my device. (Xperia XA2, Android 9). It seems to happen, when the App get's evicted from RAM and then gets restored, when you reopen it. To reproduce: go to the risk status activity and then open lots of other apps, so the CWA app, will be killed. The next time it gets opened, it takes a little bit longer, as it gets restored from storage and it will show "1 von 14 Tagen aktiv" |
…warn-app#594 Fix risk status not updating after reopening backgrounded app.
Just as a quick question: If you say you can reproduce it would mean that it shows "0 von 14 Tagen aktiv" not "1 von 14 Tagen aktiv" after restoring the app like you describe @jan-hofmeier. Did I get this wrong or is there a misunderstanding? |
@jakobmoellersap You are correct, I meant "0 von 14 Tagen aktiv" |
Okay, just for confirmation: Does this issue persist with 1.0.4 of the App? |
@jakobmoellersap yes, I just tested it again to make sure. I have 1.0.4 and still have the issue |
Describe the bug
The risk status page shows "0 von 14 Tagen aktiv" when the app is reopened after the operating system put it into background.
I'd love to add a screenshot. This is not possible as described in the appropriate issue. This makes reporting bugs very hard.
Expected behaviour
The app should show "1 von 14 Tagen aktiv" when the app will be reopened from the background.
Steps to reproduce the issue
Technical details
Android 8.1.0
I think this issue will only occur on older devices with less RAM.
Possible Fix
Additional context
I think this is a minor or cosmetic bug, however I would like to share this unexpected behavior to you.
The text was updated successfully, but these errors were encountered: