QR code time for event moved 2 hours forward

[MikeMcC399]

Technical details

• Device name: Google Pixel 3a emulator
• Android version: 11
• App version: v2.0.0-RC2

Describe the bug

The time defined when creating a QR code for an event is displayed as 2 hours later when the event is saved.

Steps to reproduce the issue

1. Open CWA, scroll down to "CREATE QR CODE" and select it
2. Tap on "+ QR CODE"
3. Tap on "Cultural event"
4. Enter a description text and a place text
5. Define start and end times and make a note of them
6. Tap "SAVE"
7. Examine the screen with the header "My QR Codes" and note that the times are two hours later than the ones entered in step 5.

Expected behavior

The times entered should be the same as the times later displayed after a QR code for an event is created.

Possible Fix

It looks like there may be a confusion between UTC and local times. The local time zone is currently CEST which is UTC+2.

---

Internal Tracking ID: EXPOSUREAPP-6249

[d4rken]

Nice catch. I agree, it's an issue with UTC conversion.

We should either adjust for the users local time within the ViewModel, or change the picker to use users current timezone already on the generated choices, and then convert them to UTC before storing them.
Later one seems cleaner, expect the UI to be in the users timezone, and then convert to UTC before saving.

/cc @jurajkusnier

cwa-app-android/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/ui/eventregistration/organizer/create/TraceLocationCreateFragment.kt

Lines 162 to 174 in ea87861

	.setSelection(defaultValue?.toDateTime(DateTimeZone.UTC)?.millis)
	.apply {
	if (minConstraint != null) {
	setCalendarConstraints(
	CalendarConstraints.Builder()
	.setValidator(
	DateValidatorPointForward
	.from(minConstraint.withMillisOfDay(0).toDateTime(DateTimeZone.UTC).millis)
	)
	.build()
	)
	}
	}

[dsarkar]

Internal Tracking ID: EXPOSUREAPP-6249

[codejus]

Bugfix for this issue is #2786.

[MikeMcC399]

This issue has been fixed through the merged PR #2786 in branch release/2.0.x.

Since this was a development version and had not yet been released through the Google Play Store this issue can now be closed.