System adds iPhone-only due time of 12:59 am
I've noticed that when I create a new task and assign it a due date but not a due time, the iPhone app adds a due time of 12:59 AM. This is true whether I create the task on iPhone or on another platform.
This due time doesn't show up on other platforms (Web, OSX) -- only on the iPhone app.
Bug or feature? Can you clarify? Thanks.
Correction -- Phantom due time also appears on iPad. So it's an iOS thing, not an iPhone thing.
Unfortunately, I can't reproduce this issue. Please try to delete and reinstall the app, make sure you have the same time zone in Todoist as on all your devices and if the issue persist - let me know what exact date are you typing in?
David -- The issue is maddeningly persistent and also maddeningly inconsistent. A delete/reinstall seemed to fix it for a couple of minutes, but then it reappeared in one, but not all, the affected items. Plus there's anew wrinkle: I assign a due date of "feb 1" to an item, and it correctly parses this a due date of "Feb 1 2014," but within a few minutes the app has moved the due date to the next day, February 2nd, and added that 12:59 AM due time. I can manually edit the item and change the due date to "feb 1" and it seems to stick, but I don't have much confidence it, or another item, won't suddenly add a due time, or change the due date, or both.
So I decide to kick the tires some more. I create an item in the OSX app, assign a due date of "Monday" with no due time, and when the item syncs down to my iPhone it shows a due date of Tuesday, and a due time of -- yep -- 12:59 am. This, at least, happens consistently.
Or, this just happened: Create a task on the iPhone app. Use the date picker to asisgn a due date of November 5. Save the item. It displays in "Next 7 days" with a due date of Nov 6th and a due time of yes, 12:59 AM.
I gotta be honest: This is the kind of issue -- flaky, weird, semi-inconsistent -- that drives me absolutely nuts.
Update: Could this be an issue that is somehow being created as part of the sync process? I just created a task on my phone and used the date picker to set a due date of Sunday, no due time. No problems. Then I watched for the task to show up on my desktop app. It did. Then I looked again at the iPhone app. It was now showing a due date/time of Monday 12:59 am. This behavior, at least, is consistent. I was able to duplicate it several more times.
This sounds exactly as an issue we've had recently which caused this to happen for all tasks that were added after the day the Daylight Savings Time ended last weekend. We've fixed it and if you have the correct time settings and time zone across all devices, in Todoist and in case Todoist asked you to change the zone - you've agreed, then this should certainly not happen.
And again, I can't reproduce this. Please try to log into your Todoist account on the web, go to Settings -> Account, pick a similar time zone, that is - one with the same correct delay (according to your location), but with a different city. Then make sure the same one is selected within the Todoist iOS app and of course - on all your devices.
To test it again, I've just added a task through our iOS app, picked a date "Nov 5" from the calendar and it shows under "Tuesday" (Nov 5) in 7 days, has the correct date and doesn't have any time added to it. Please double0ceck your time zones as so far, this is the only way that we know of that can cause such problems.
David -- Sorry, I should have specified sooner that my time sone is set the same across all my devices.
Latest iteration: I set a task on my phone with a due date of Sunday. Left it in Inbox. It syncs correctly to Web interface. Repeat with a second item. Same result. Then I create a similar task on the Web interface. Save it. In the sync down to my iPhone, it forces ALL THREE TASKS to the next day at 12:59 AM on my iPhone only -- tasks continue to have correct due date in Web and OSX apps.
I tried changing my time settings across all devices to another location that has the same differential from GMT. No dice. Same errors. But honestly, if you're advising me to set my system time to say, Mazatlan, rather than Los Angeles, where I live, that doesn't seem like a viable solution.
Also: DST has not yet ended here in the States. It doesn't end until this weekend.
Really hope you guys can help with this. I like the product, but this is a very frustrating problem.
Hey -- just noticed that this maddening issue only occurs on tasks with a due date of this coming Sunday (the day DST ends in the States) and after. It doesn't happen on tasks set with due dates of tomorrow (Thursday), Friday or Saturday. So it seems like some sort of DST-related bug, doesn't it?
Yes, it does appear to be similar to the issues we have been having related to DST. Please let us know if it continues to do so after DST has completed this weekend.
We are sorry for the trouble.
Okay, thanks. Has it been your experience in other places that once local DST ends the issue clears up?
Yes, from our experience it does clear up after DST has finished. It's an issue that should not happen but we have had troubles fixing it as of yet.