/API/updateRecurringDate bug - sets wrong date
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?
In case it matters, I'm GMT+1.
Thanks a bunch,