DateTime Picker issues on Bubble Native (Bubble Go) – Timezone shift

Mobile Beta Mobile Beta - bugs
1

Hi everyone,

I’m experiencing several issues with the DateTime Picker in Bubble Native (Bubble Go) and after debugging, it appears to be related to timezone handling.

Context

  • Device timezone: Australia/Sydney (currently UTC+11)

  • App language: French

  • Testing in Bubble Go

  • This is for a real DateTime event (e.g., “Tuesday 18th at 11:00 AM” for a run)

Time is shifted by exactly 11 hours

When selecting a time, the saved value is always 11 hours earlier than what I selected.

Example:

  • I select 18:00

  • The stored value becomes 07:00

The 11-hour difference exactly matches the current Sydney timezone offset (UTC+11).

To debug, I compared:

  • This device timezone

  • This device timestamp

  • Input DateTime’s value

It looks like the native picker may be returning a UTC value, but Bubble is not converting it back correctly to the device timezone or possibly applying an incorrect conversion.

Has anyone confirmed how the Native DateTime Picker handles timezone internally?

Picker language is always English

Even though my app language is French, the native Date/Time picker always displays in English.

Is localization currently supported for native pickers?

Placeholder does not show existing value

If the DateTime field already contains a value:

  • The placeholder remains empty

  • The current stored value is not displayed

  • The user must reselect the date/time to see it

Question

Is this a known limitation or bug of the Native DateTime Picker regarding timezone conversion and state handling?

Right now I’m considering splitting:

  • Date

  • Time (minutes since midnight)

  • Timezone

But I would prefer to use a proper DateTime field if possible.

Any clarification would be greatly appreciated :folded_hands:

Thanks!

1 Like
2

hey :waving_hand:

this doesn’t sound like a mistake on your end. the 11-hour shift matching Sydney’s UTC+11 offset is the giveaway it likely means the native picker is returning UTC and Bubble isn’t converting it back properly (or it’s being converted twice). that exact offset difference is almost always a timezone handling issue.

the language part is also expected for now. native pickers usually follow the device/system locale, not the app language set in Bubble, so French inside the app won’t necessarily change the picker UI.

and the placeholder not showing the existing value feels more like a current limitation of the component.

splitting date, time, and timezone is the safest workaround if accuracy really matters, even if it’s not as clean as a single DateTime field.

3

You got this sorted already?

4

Picker language is always English

Even though my app language is French, the native Date/Time picker always displays in English.

Is localization currently supported for native pickers?

Hi, this is a problem I have already reported regarding the language inside the p.list file of the build that the bubble generates. At the moment no language outside of EN English was supported. I reported it to the engineering team and @nick.carroll assured me that it will be on the roadmap within the next two weeks.

5

They didn’t said short term for me : “I wanted to let you know that our engineering team is aware of the current limitation with the Date/DateTime picker and the build language, and that they’ve included these features on our roadmap to implement in the longer term.”

8
9

This topic was automatically closed after 14 days. New replies are no longer allowed.