+ Add Question

DST bug pops up again for tasks due-dated spring 2014

BB

The troubles I was having with the DST bug (due-dated tasks getting a random due time and jumping forward a day) stopped after the end of DST here in the US last weekend. But I was unhappily surprised to see them pop back up again when I tried to create a task for May 1 2014, which is after the annual restarting of DST. Is this going to be an issue every year? It's really annoying. Thanks.

All responses

Brendon Wadey staff
Replied on Nov 06, 2013 - 23:39 UTC

Hi Bill,

To clarify, you create a task for May 1, 2014 right now, and it gets pushed to May 2nd?

Are you adding this task on mobile, or web, does it happen on both?

Thanks,
Brendon.

BB
Bill Barol premium
Replied on Nov 07, 2013 - 00:00 UTC

Brendon:

1) If I create a task for May 1 2014 (no due time) on iPhone and then sync, it changes to a due date of May 2 2014 at 10:59 PM. The changed due date appears across platforms. The added due time only appears on mobile.

2) If I create a task for May 1 2014 (no due time) on Web, when it syncs to my iPhone and to the OSX app the date stays the same but there is an added due time of 10:59 PM.

3) If I create a task for May 1 2014 (no due time) on the OSX app, when it syncs to my iPhone and to the Web the date stays the same but there is an added due time of 10:59 PM.

Brendon Wadey staff
Replied on Nov 07, 2013 - 00:26 UTC

Bill,

Please confirm that your desktop, iOS and Todoist are all set to the same timezone. You have probably been told this or read it a few times, but I'd like to confirm everything is indeed in the correct setting.

We are still having a few issues from DST right now and are looking into it. Though these are normally with older tasks created before hand.

Thanks,
Brendon.

BB
Bill Barol premium
Replied on Nov 07, 2013 - 00:46 UTC

Yes, all devices/platforms are set to US Pacific Standard Time (GMT -0800).

Brendon Wadey staff
Replied on Nov 07, 2013 - 17:44 UTC

Bill,

Please try logging out of the iOS app and back again and let me know if that helps.

As for the added time, is that shown when hovering over the date area, or when you edit it you actually see this time added?

Thanks,
Brandon.

BB
Bill Barol premium
Replied on Nov 07, 2013 - 18:31 UTC

Logging out/logging back in to the iOS app didn't help.

And the added time is present only in the iOS app. I can see it in the task view, but not in the "Edit" view. Date field in "Edit" view has date alone, no time. Time is not present in iOS app or Web app. Sorry if I wasn't clear about that before.

Also sorry it took me a few minutes to respond; todoist.com is now crashing Safari every single time I try to open the page. Every time. Swear to God. (I'm writing this in Firefox.)

David Trey staff
Replied on Nov 07, 2013 - 20:33 UTC

Hello Bill,

Thank you for your report, I've been able to reproduce this issue and I've passed it to the developers, we'll look into it.


Best regards,
David

BB
Bill Barol premium
Replied on Nov 07, 2013 - 20:43 UTC

Thanks.

BB
Bill Barol premium
Replied on Nov 20, 2013 - 00:23 UTC

Hi -- Any update on this annoying bug? Thanks.

David Trey staff
Replied on Nov 20, 2013 - 12:37 UTC

Hello Bill,

This should have been fixed by now, please tell me - does logging out and back into the app solve it? Can you still reproduce it after creating a new task?


Best regards,
David

BB
Bill Barol premium
Replied on Nov 20, 2013 - 20:02 UTC

David: Bug is still present, at least partly, and this is after logging out/logging back in on all devices/platforms.

To wit: Tasks created with a due date falling after the switch back to US DST (but no due time) have a due time of 10:59 PM added. This is true whether the tasks are created on iOS or created elsewhere and synced back to iOS. However, the added due time is visible only on iOS.

The good news is, these tasks are no longer pushed to the next day.

Thanks.

David Trey staff
Replied on Nov 20, 2013 - 23:13 UTC

Bill,

I'll notify the developers about this now.


Best regards,
David

BB
Bill Barol premium
Replied on Nov 20, 2013 - 23:14 UTC

Thank you.

BB
Bill Barol premium
Replied on Dec 07, 2013 - 01:33 UTC

Looks like your latest iOS update squashes this pesky bug. Thanks!