Regression in date of birth formatting

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 Follow on report from https://github.com/corona-warn-app/cwa-app-android/issues/3963#issuecomment-911924812 and https://github.com/corona-warn-app/cwa-app-android/pull/3987

Technical details

• Android version: 11
• App version: 2.10.0-RC2 (pre-release version)

Describe the bug

PR https://github.com/corona-warn-app/cwa-app-android/pull/3987 has introduced a regression concerning inconsistent formatting regarding dates of birth.

For example, the date of birth in PersonDetailsFragment_cwa.png in release 2.10 should use the same order of month day year according to the English (United States) locale which is used in the date of sample on the same screen.

Instead of showing the date of birth as 1981/03/20, it should be shown as 03/20/1981.

---

PersonDetailsFragment_cwa from release/2.10.x

---

PersonDetailsFragment_cwa from screenshots 2.8 for comparison. In this version the date formats were fixed and did not use the device’s locale settings.

Steps to reproduce the issue

1. Settings > System > Languages and input > Languages
   set to English (United States)
2. Settings > System > Date & time
   select “Use locale default”/ disable “Use 24-hour format”
3. Connect mobile device to Android Studio
4. In Android Studio Build > Select BuildVariant deviceForTestersDebug
5. run src/androidTest/java/de/rki/coronawarnapp on emulator
6. View > Tools Windows > Device File Explorer
7. Go to /data/data/de.rki.coronawarnapp.test/screenshots
8. View screenshots and check the formatting of all dates of birth

Expected behavior

Dates of birth should be formatted according to the device’s locale setting, except in certificates where a field label indicates formatting using YYYY-MM-DD.

---

Internal Tracking ID: EXPOSUREAPP-9297

[marcauberer]

@MikeMcC399 new pr is open. Would be nice, if you could take a look at the screenshots and report back to me if the bug is solved. Thank you!

[dsarkar]

@MikeMcC399 I forwarded your comment into the new internal ticket.