šŸ—“ [FREE Plugin] Air Date/Time Picker

Showcase
938

@ZeroqodeSupport Iā€™m just returning to the issue with time zones not being respected in this plugin, as itā€™s still causing problems in my appsā€¦

Iā€™ll explain the issue more clearlyā€¦

If I define a date (e.g. 20th October, 00:00 in UTC), and then display that Date, formatted as dS mmmm, H:MM UTC, it should always display as ā€˜20th October, 00:00ā€™, for every user, regardless of their own device timezone.

However, when setting a date with the Zeroqode Air Date/Time picker, and setting the air date pickerā€™s dynamic timezone to UTC, it is NOT defining the selected date in UTC, but rather it seems to be using Europe/London time.

This is not the expected or correct behaviour of a date picker.

Iā€™ve made a simple demonstration, with two simple examples to highlight the issueā€¦

Air Date Picker Issue (bubbleapps.io)

The first one uses Bubbleā€™s own Date Picker element - and this works as expected (i.e. it defines the selected date as 00:00 UTC)

And the other one uses the Air Date Picker - this one does NOT define the date correctly, but rather always uses Europe/Londonā€¦ which during Winter (as it is now), when selecting a date in the Summer, puts the selected date one hour (and therefore also one day) behind the selected date.

Specifically, itā€™s a problem when selecting dates prior to October 30th, which was when Europe/London time switched from BST to GMT.

Again, the example on the left is using Bubbleā€™s own Date Picker, which works correctly.

The example on the right uses the Air Date/Time Picker, which outputs the wrong date.

Both date pickers are set to define the date as 00:00 in UTC

Both text elements display the respective dates formatted in UTC.

If you select 20th October 2023 in the Bubble date picker, the text will display ā€œ20 Oct 2023, 12:00amā€, exactly as expected.

But you select 20th October 2023 in the Zeroqode Air Date/Time Picker, the text displays ā€œ19 Oct 2023, 11:00pmā€ instead, which is obviously incorrect.

It seems to only display this bug when my computer device timezone is set to a timezone that observes DST, but itā€™s only ever out by one hour, regardless of the device timezone. It seems to be using Europe/London time instead of UTC.

But if I Set my device time zone to UTC, or any timezone that doesnā€™t have DST, this issue does not occur.

Obviously, seeing as the Date is being set and displayed in UTC, the device timezone should not have any effect on the date being set (and it doesnā€™t when using the Bubble date picker), so the issue seems to be that the Zeroqode Date picker is somehow being affected by the device timezone, even when it shouldnā€™t be.

see this thread for additional context: A favour needed - Bugs - Bubble Forum

2 Likes