DatePicker shows UTC date instead of local date [281859606]

Assigned

Bug

Status Update

No update yet.

Description

la...@gmail.com

created issue #1

May 11, 2023 06:27PM

Jetpack Compose version: 1.4.0-beta01

Jetpack Compose component used:

DatePicker
DatePickerDialog

Android Studio Build:

  Android Studio Flamingo | 2022.2.1
  Build #AI-222.4459.24.2221.9862592, built on March 31, 2023
  Runtime version: 17.0.6+0-17.0.6b802.4-9586694 aarch64
  VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
  macOS 12.6.5

Kotlin version: 1.8.0

The Material 3 DatePicker shows the UTC date instead of the local time zone. Using the code below, the expected selected date in the DatePicker should be May 19, 2023 but it shows May 20, 2023.

@Composable
fun MainView(modifier: Modifier = Modifier) {

    Scaffold {
        var showDatePicker by remember { mutableStateOf(true) }

        Text(
            text = "Hello",
            modifier = modifier.padding(it)
        )
        if (showDatePicker) {
            // 1684540800000 milliseconds
            // UTC: Sat May 20 2023 00:00:00
            // Local: Fri May 19 2023 20:00:00
            //
            ShowDatePicker(initialSelectedDateMillis = 1684540800000) {
                showDatePicker = false
            }
        }
    }
}


@OptIn(ExperimentalMaterial3Api::class)
@Composable
fun ShowDatePicker(initialSelectedDateMillis: Long, callback: () -> Unit) {
    val datePickerState = rememberDatePickerState(
        initialSelectedDateMillis = initialSelectedDateMillis
    )

    DatePickerDialog(
        onDismissRequest =  callback,
        confirmButton = {},
    ) {
        DatePicker(
            state = datePickerState,
            title = {
                val dateFormatter = DateTimeFormatter.ofLocalizedDate(FormatStyle.MEDIUM)
                val millis = datePickerState.selectedDateMillis ?: 0L

                Text(
                    text = Instant.ofEpochMilli(millis).atZone(TimeZone.getDefault().toZoneId()).format(dateFormatter),
                    style = MaterialTheme.typography.titleMedium,
                    modifier = Modifier.padding(20.dp)
                )
            },
            showModeToggle = false
        )
    }
}

DatePicker Incorrect Date.png

268 KB

View

Download

Comments

la...@gmail.com <la...@gmail.com> #2May 24, 2023 11:34PM

Hi,

Thank you for your feedback. I understand that this is a frustrating experience - we aren't in a super easy spot with Swipeable. It currently has a number of critical bugs that need to be addressed first (we are working on this), which is why we are limiting the surface we are exposing for Swipeable in M3 for the time. Our plan for the coming months is to focus on this specific area and improve developer experience.

Material 3 for Jetpack Compose is still in alpha - this means we consider components production-ready, but the API shape is flexible while in alpha. This gives us space to iterate while getting real-world feedback from developers, which ultimately helps improve your experience. Copy-pasting source code for components that are not (fully) implemented or exposed in an alpha version can be a good thing to do in the meantime! Owning the source code while the API shape is still flexible gives you a number of benefits like ease of updating dependencies, even if the APIs change, and allows you to evolve your components in your own pace.

We are aware of your request to expose rememberSwipeableStateFor in M3 though and will do so when the time is right and Swipeable in a good enough spot. I will close this issue in favor of b/163132293 which has a bit more historical context.

mi...@gmail.com <mi...@gmail.com> #3Jun 11, 2023 10:03AM

..and no such anger. Sorry about that. Agree, close this. And thank you for your considerations. :)

jo...@gmail.com <jo...@gmail.com> #4Jun 9, 2024 07:53PM

Just asking, do you have a reference to the critical bugs in swipeable? I'm using the M2 variant and I'm actually pretty happy with it... Curious about which issues I can expect with it.

sg...@google.com <sg...@google.com> Jun 10, 2024 03:21AM

Reassigned to ma...@google.com.

sp...@nxr.global <sp...@nxr.global> #5
Restricted+
Aug 29, 2024 08:31AM

Comment has been deleted.

ly...@gmail.com <ly...@gmail.com> #6Nov 15, 2024 01:58AM

That makes sense, because that is what I'm using it for. :-) I wanted my UI screens to be swipeable a la Telegram (example)

Sadly the navigation authors are unresponsive to feature requests which would facilitate this pattern, so I've been hacking it out myself with just Compose + State. It works surprisingly well so far. I have to commend you guys, Compose is a blast!

al...@gmail.com <al...@gmail.com> #7Nov 21, 2024 07:43AM

I've noticed one little glitch. Velocity seems to be too high if I 'jiggle' the swipeable element and then release. See attached video: the pane is swiped all the way even though I wouldn't expect it to for such a small drag.

Maybe it's the same issue as https://issuetracker.google.com/issues/216582726 ?

Message last modified on Nov 21, 2024 08:30AM

ma...@gmail.com <ma...@gmail.com> #8Feb 12, 2025 11:02AM

https://android.googlesource.com/platform/frameworks/support/+/071c483c7223af673a5c0145e2fee7b0c94af1fd%5E%21/

PLEASE

STOP

MARKING

USEFUL

APIS

INTERNAL

br...@pappin.ca <br...@pappin.ca> #9Feb 28, 2025 01:25PM

Hi, we hear your frustration and as my colleague pointed out, we are balancing many factors when committing to API surfaces. Each API goes through multiple internal reviews and we do read through all feedback/bugs as input on what APIs we build next. We ask for patience and we appreciate the time you've taken to give us input from the community!

However, all-caps aggressive complaints like #comment8 provide little value, are not productive, and violate the terms of our tracker. When you find APIs that you need, please continue to file bugs, but remember to be respectful in how you communicate here.