corona-warn-app/cwa-app-android

No warning on Android 12 for wrong time

MikeMcC399 opened this issue · 3 comments

MikeMcC399 commented

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
  • Related to #5183

Technical details

  • Device name: Samsung Galaxy A52 5G (SM-A526B/DS)
  • Android version: 12
  • App version: 2.25.0

Describe the bug

App does not stop exposure check taking place when date incorrectly set to future before installation on Android 12.

On Android 8 an error message is output and no exposure check takes place.

Steps to reproduce the issue

On Android 12:

  1. Set device date to two days into the future
  2. Uninstall CWA (if already installed)
  3. Install CWA
  4. Open CWA
  5. Tap "Let's Get Started"
  6. Tap "Next"
  7. Tap "Activate Exposure Logging"
  8. Tap "Turn on"
  9. Tap "Next", tap "Next"
  10. Tap "Do Not Share"
  11. Tap "OK"
  12. Tap "Allow", disable optimized battery usage for Corona-Warn (device specific)
  13. Dismiss QR Code Scanner pop-up by tapping on "X"
  14. Note "Exposure check failed, with timestamp Today"
    Exposure check 1

Repeat the steps 1 - 11 on Android 8:

At step 11, Android 8 already shows an error message:

  1. Tap OK for message "Exposure Check Not Possible"
    Exposure Check Not Possible
  2. Tap "Allow", disable optimized battery usage for Corona-Warn (device specific)
  3. Dismiss QR Code Scanner pop-up by tapping on "X"
  4. Note "Encounters have not yet been checked."
    Encounters not yet checked

Expected behavior

  • On Android 12 the app should prevent an exposure check from taking place if the date does not match the server date. It should output the same error message "Exposure Check Not Possible" as displayed on Android 8 under the same conditions.

Internal Tracking ID: EXPOSUREAPP-9077

sapcoder123 commented

@MikeMcC399 Thank you for reporting the issue which is fixed with #5183

MikeMcC399 commented

@sapcoder123

the issue ... is fixed with #5183

  • #5183 is another related issue (not a PR with a code change). The resolution is supposed to be in PR #5465.
MikeMcC399 commented

I successfully tested this issue with Corona-Warn-App-2.27.0-RC0-deviceForTesters-release.apk so I am now closing it.