Hi folks. Anyone else encountering the issue where...

# compose-android

[Alexandru Gheorghe]

Hi folks. Anyone else encountering the issue where DatePicker drops milliseconds to retain only the date disregarding time? I'm having an issue where I'm trying to store the datetime a user selects in the UI by defaulting the states for DatePicker and TimePicker to Clock.System.now().toEpochMilliseconds() and getting the issue where I'm seeing the date off by 1 day when converting DatePicker milliseconds to system's timezone.

[Alexandru Gheorghe]

Before you jump at me that I should post in #C01923PC6A0, I do believe it's relevant here as well since it's more related to DatePicker rather than kotlinx datetime itself.

[Alexandru Gheorghe]

There's a bug opened @ https://issuetracker.google.com/issues/281859606 for a similar issue. Could be the same root cause. Though I'd still like to know if some of you encountered this problem and how you solved it.

[Stylianos Gakis]

Which date picker is this? Material? Material3?

[Alexandru Gheorghe]

M3

[Alexandru Gheorghe]

I've opened https://issuetracker.google.com/issues/380110866

[Stylianos Gakis]

I see you're using a very old bom. In general it's a good idea to file bugs on latest versions to make sure that this isn't addressed already.
You could create a sample project using the latest alpha and try to see if this behaves the same way there.
If they've changed how this works since that old bom, I doubt they'll look into this bug at all.