/API/updateRecurringDate bug - sets wrong date

Hi,
I use the /API/updateRecurringDate in my app to mark a recurring task as complete (I would use the Sync API, but I haven't found a way other than to roll my own DateString parser).

When I call the API, it sets the date one day late. For example, when I create a new recurring task with "next Friday" and call the endpoint with its Id, the tasks due date gets set to the Saturday after next Friday.

If I set the date using the Web app, it works correctly. After inspecting the traffic, I came to the conclusion that the Web app calculates the next occurrence internally (not using any server APIs) and then does a full sync using item_update_date_complete. That could mean that you have separate client and server implementations for date string parsing with the server one being faulty. In that case, can you fix it?

All responses

And one more piece of information I discovered - the task one doesn't get shifted one more day each time I mark it as complete. It stays shifted one day no matter how many occurrences are completed

David Trey staff

Replied on Apr 28, 2014 - 12:16 UTC

Hello Jan,

I've passed your question to our developers and will let you know once they reply.

Best regards,
David

Amir Salihefendic staff

Replied on Apr 28, 2014 - 14:35 UTC

Hi Jan

We have a client side implementation and a server side implementation of the date-parser.

We might make it possible to get a next occurrence using our API. What is the use case of this?

Best regards,
Amir

Jan Kratochvíl premium

Replied on Apr 29, 2014 - 08:49 UTC

The use case is marking an ocurrence of a recurring task as complete.

Using the Full Sync APIs, I need to provide the date of next ocurrence as part of the item_update_date_complete action. To do that, I would need to develop my own date parser which is bound to be error prone and I'd therefore like to avoid it.

Thanks,
Jan

Amir Salihefendic staff

Replied on Apr 30, 2014 - 21:54 UTC

Hi again Jan

Just to make sure I understand this 100%:
You would like to have a new command to complete recurring tasks without supplying next date?

Regards,
Amir

Jan Kratochvíl premium

Replied on Apr 30, 2014 - 21:57 UTC

Yes, it would help me a lot.

Thanks,
Jan

Jan Kratochvíl premium

Replied on May 06, 2014 - 14:44 UTC

What's the status? I haven't heard from you in a while.

David Trey staff

Replied on May 06, 2014 - 14:45 UTC

Hello Jan,

We will consider implementing this in the future.

Best regards,
David

Jan Kratochvíl premium

Replied on May 06, 2014 - 14:46 UTC

And will you at least fix the bug in the /API/updateRecurringDate endpoint, as described in the original post?

Hi there,
I use the new implementation you mention.
However I'm getting the same results as before.

One new thing I found out is that the bug does not happen always. Notably, when a task is set to "every day", it behaves as expected at least for me.

What information (if any) can I provide you with to help resolve the issue?

David Trey staff

Replied on Jun 22, 2014 - 17:59 UTC

Jan,

The most important information we'd need is a way to reliably reproduce it every time. Roz mentioned that it happened if the task had a due time, such as "everyday at 7am". It then seemed to change to 11am the next day. Can you reproduce this every time when the task has a specific due time?

Best regards,
David

Jan Kratochvíl premium

Replied on Jun 22, 2014 - 18:25 UTC

Here is exhaustive repro information:

--Step 1
Create a task using the web app with due date "every day at 7:00"
At this point, the web app shows "next due date" to be Monday at 07:00, which is fine

--Step 2
Call the Sync API to mark the recurring task as complete like so:
"[{\"type\":\"item_update_date_complete\",\"temp_id\":null,\"timestamp\":1403468061,\"args\":{\"id\":\"138279450\",\"is_forward\":1}}]"

--Step 3
At this point, the web app shows "next due date" Tuesday at 05:00, which is two hours earlier than it should be.
In another words:
Expected: Tuesday at 07:00
Actual: Tuesday at 05:00

--(Step 4)
During a subsequent sync using the Sync API, the API returns an update to target task's "due_date" date field which is consistent with the one displaying in the web app, that is, off by two hours.

David Trey staff

Replied on Jun 22, 2014 - 20:16 UTC

Jan,

Thank you very much for your report, I've passed it directly to our developers and will let you know once they reply.

Best regards,
David

Jan Kratochvíl premium

Replied on Jun 28, 2014 - 14:04 UTC

What's the status?

Brendon Wadey staff

Replied on Jun 28, 2014 - 17:31 UTC

Jan,

Very sorry I just asked again and hopefully it won't be much longer.

Regards,
Brendon.

Roz Ariffin Rozaid

Replied on Jun 29, 2014 - 15:29 UTC

Any update yet from dev team?

Roz Ariffin Rozaid

Replied on Jul 01, 2014 - 19:26 UTC

10 days since you passed the issues to your todoist developer team. How long it need to wait, 6 months? Is there any members from dev team itself that willing to give a comment about current status? I hope this time, someone from todoist support team bother to give a reply.

David Trey staff

Replied on Jul 01, 2014 - 20:14 UTC

Roz,

It's on the developer's to-do list and as soon as we hear back from the them, we'll post the reply here instantly.

Best regards,
David

Jan Kratochvíl premium

Replied on Jul 14, 2014 - 19:50 UTC

What is the status? Can you at least confirm the issue and provide a clear timeline?

Brendon Wadey staff

Replied on Jul 14, 2014 - 20:21 UTC

Jan,

We do not have any timeline at this time, but its known and being looked into.

Regards,
Brendon.

Thomas Gardner premium

Replied on Jul 15, 2014 - 12:57 UTC

Hello Todoist Staff, please prioritize this. Jan's app is the only legitimate third-party Todoist representation on the Windows Phone platform, and this recurring task bug deserves attention. I am one of the affected users who keeps seeing his recurring tasks slowly change dates and times.

Thank you,

Roz Ariffin Rozaid

Replied on Jul 15, 2014 - 13:36 UTC

I totally agreed with what Thomas said. The prob is there since April. Now it's been 4 months yet Todoist team still don't have timeline to fix this. Furthermore, I don't think we as a premium user deserved this kind of support. Bare in mind that we are not using this for free.

Like i said, it's either you release an official app or fix this bug so we as Windows Phone User do have option to use Todoist third party like Jan created. We glad Jan did provide his precious time to provide alternative Todoist plus released an update almost every few days or weeks to provide good Todoist experience.

May i ask you, do you expect us to sit in front of laptop or computer of all time? No, right? This is why this is very important for you guys to fix this bug so we don't have to go web based over and over again to edit recurring time occured. My phone with me all the time when ever i travel or outside my home.

At least, Todoist please show some appreciation for your customer who paid by providing your time to fix this bug. We understand Todoist too busy until they don't have time to create official apps for Windows Phone. A lot of customers requested the same thing but the same reasons like "we will consider", "maybe in future" bla bla bla etc but until now, nothing appeared.

Again, please fix this bug so we don't have to bother you guys again.

David Trey staff

Replied on Jul 15, 2014 - 14:31 UTC

Hello Roz,

We're very sorry for the inconvenience, it's on our developers' to-do lists, I have now notified them about your response and as soon as we hear back from them we will notify you in this thread immediately.

Best regards,
David

TP

Trish Putnam premium

Replied on Jul 15, 2014 - 21:28 UTC

I am also a user impacted by this defect. I use Jan's tool because it's the best available for Todoist on WP8, and I have to be able to manage my tasks on my phone. Please understand that this IS a critical issue for anyone who has time and date critical recurring tasks in the system.

Roz Ariffin Rozaid

Replied on Jul 16, 2014 - 03:49 UTC

Hey David

I appreciated your response but i want to know exactly when the due date that developer put in their to do list and their priority, it's either critical or not?

And also i want the developer to make a direct comment to here and keep us updating at least every 2 days about what he or she working on. Is it too hard to fix the bug? Can developer put this as their first to do list?

David Trey staff

Replied on Jul 16, 2014 - 11:28 UTC

Roz,

As soon as I hear any response from our developers regarding this particular issue, I will let you know as soon as I possibly can. The devs are fixing all reported bugs, but I can't give you any specific order in which they will be fixed.

Again, as soon as I hear anything back from them, I will let you know.

Best regards,
David

David Trey staff

Replied on Jul 28, 2014 - 16:01 UTC

Hello,

This bug has now been fixed.

Regards,
David

Jan Kratochvíl premium

Replied on Jul 28, 2014 - 16:48 UTC

Great news!
Is this fixed in all Sync API versions or if not, what is the lowest Sync API version that has been fixed?