Fixed
Status Update
Comments
dw...@gmail.com <dw...@gmail.com> #2
Please fix this bug. I rely on this calendar software to track my tasks and this is causing me serious trouble.
je...@gmail.com <je...@gmail.com> #3
I'm getting reports from users of an app I developed which uses the Google Tasks API about this issue. Hoping Google will fix this one as it kind of breaks the API functionality..
bi...@gmail.com <bi...@gmail.com> #4
I see a little bit different issue. Once the date is "locked out" I cannot see the changes I make with third party apps whether or not I reload one or all of the apps. Everything displays correctly in the TP Apps on all sync'd devices, but never correctly displayed in the "Google Task" app on any sync'd device.
If I change the Due Date using the "Google Task" app, everything is displayed correctly in all TP Apps as well as Google Task apps on all sync'd devices.
If I change the Due Date using the "Google Task" app, everything is displayed correctly in all TP Apps as well as Google Task apps on all sync'd devices.
tx...@case.edu <tx...@case.edu> #5
I have been using Google Tasks with a third-party app for years, to manage personal and professional activities. This bug is making Tasks much harder to use and trust. Please prioritize and address. Thanks.
ro...@gmail.com <ro...@gmail.com> #6
I use http://calendar.google.com on my desktop and a hhird party app on my mobile devices. I am experiencing the exact behavior described by the original poster. This makes http://calendar.google.com unreliable and not usable. Please fix this bug so that http://calendar.google.com will be usable again.
ke...@gtaskd.com <ke...@gtaskd.com> #7
The OP is absolutely right. After some testing, I'm 99% sure the issue here is that there are two different due date fields in the database: the one available through the Google Tasks API, and the one that Google Calendar (and the rest of GSuite) uses. As the OP and others have said, this started when the due times and task recurrence features were added. Details on how to recreate the problem:
1. Create a Task with a due date (with or without a due time) athttps://calendar.google.com/
2. Use any app to update the task's due date via the Google Tasks API, even Google's own:https://developers.google.com/tasks/v1/reference/tasks/update
3. The Google Tasks API will report the date as the one that was changed, but Google Calendar will show the date it originally set
From that point on, changing the date with Google Calendar changes both dates (API and Calendar), but changing via the API only works if the date was never set by Calendar. As soon as Calendar writes to it's other field in the database, it will copy any change it makes to the datetime field the API uses, but will only every use the value it wrote to display in Calendar.
Solving the issue seems fairly straightforward: use the same datetime field in both Google Calendar/GSuite and the Google Tasks API. This would have the added advantage that developers using the Google Tasks API could set due times. Currently the Google Tasks API date is always rounded to 0 UTC, even if you set a time in Calendar, or attempt to set one via the API.
Thanks and have a good one,
Kevin
1. Create a Task with a due date (with or without a due time) at
2. Use any app to update the task's due date via the Google Tasks API, even Google's own:
3. The Google Tasks API will report the date as the one that was changed, but Google Calendar will show the date it originally set
From that point on, changing the date with Google Calendar changes both dates (API and Calendar), but changing via the API only works if the date was never set by Calendar. As soon as Calendar writes to it's other field in the database, it will copy any change it makes to the datetime field the API uses, but will only every use the value it wrote to display in Calendar.
Solving the issue seems fairly straightforward: use the same datetime field in both Google Calendar/GSuite and the Google Tasks API. This would have the added advantage that developers using the Google Tasks API could set due times. Currently the Google Tasks API date is always rounded to 0 UTC, even if you set a time in Calendar, or attempt to set one via the API.
Thanks and have a good one,
Kevin
wh...@gmail.com <wh...@gmail.com> #8
I have been experiencing exactly the same issue with a little command-line tool I wrote to help manage my task-lists.
Glad to finally find out what the problem is and hoping for a speedy bug-fix from Google.
(This is seriously ruining my productivity at work - I organise everything via Google Tasks!)
Glad to finally find out what the problem is and hoping for a speedy bug-fix from Google.
(This is seriously ruining my productivity at work - I organise everything via Google Tasks!)
jo...@sovcik.net <jo...@sovcik.net> #9
Experiencing the same issue....
Was there any update on this from Google side?
Was there any update on this from Google side?
ra...@gmail.com <ra...@gmail.com> #10
I too am having this problem. Very annoying.
kr...@gmail.com <kr...@gmail.com> #11
I'm also experiencing this. It's causing issues with tracking my tasks. Please fix this!
wj...@gmail.com <wj...@gmail.com> #12
please fix this bug....
da...@gmail.com <da...@gmail.com> #13
We have a to-do list app on Google Play that is also affected by this bug. A prompt fix from Google would be appreciated, as we are getting complaints from our users about this.
r....@gmail.com <r....@gmail.com> #14
Experiencing the same issue.... please fix it.
an...@gmail.com <an...@gmail.com> #15
Same issue here. For me, this makes G tasks unusable. Please fix!
jo...@gmail.com <jo...@gmail.com> #17
The described issue is a follow up problem introduced by implementing this ticket:
https://issuetracker.google.com/issues/36759725
ek...@google.com <ek...@google.com> #18
I've been able to reproduce this issue and raised it with the Tasks API engineering team. At the moment the old workaround is to delete the due date in the sidebar UI and then ensure it is only set via the API after that.
ca...@gmail.com <ca...@gmail.com> #19
Similar issue here. Moving a task to a different date via a third party app does not change the date on Google. Please address the API issue. THanks
el...@gmail.com <el...@gmail.com> #20
Pleases fix this bug. I rely on CalenGoo to keep up with my calendars/tasks/due dates. Thank you.
wh...@gmail.com <wh...@gmail.com> #21
It looks like this issue might now have been fixed.
Certainly the GTasks app I use on my Android device and my own little command-line tool that uses the Tasks API are both now updating my Google Calendar Tasks list correctly.
Certainly the GTasks app I use on my Android device and my own little command-line tool that uses the Tasks API are both now updating my Google Calendar Tasks list correctly.
ca...@gmail.com <ca...@gmail.com> #22
Still broken here. Create task using calendar.google.com on a specific date. Move the task to a different date using Calengoo. Date remains the same on calendar.google.com .
gs...@gmail.com <gs...@gmail.com> #23
Really need a solution with this, otherwise will move to microsoft to do with any choice.
Not completely sync with Google Tasks (When task was generated by apps, it can sync with Google Tasks. The old task that already in Google Tasks, only sync when change was done by Google Task. If change was done by the apps, its not sync with Google Tasks).
Not completely sync with Google Tasks (When task was generated by apps, it can sync with Google Tasks. The old task that already in Google Tasks, only sync when change was done by Google Task. If change was done by the apps, its not sync with Google Tasks).
mi...@gmail.com <mi...@gmail.com> #24
+1
ak...@gmail.com <ak...@gmail.com> #25
Please fix issue: task not usable like this in Google. Thanks
pa...@gmail.com <pa...@gmail.com> #26
Same here, still experiencing this bug.
ma...@upian.com <ma...@upian.com> #27
Same here, third-party applications using Task API are unusable because of this bug.
Please fix it !
Please fix it !
gs...@gmail.com <gs...@gmail.com> #28
Same here, kindly fix it soonest.
j....@fornext.info <j....@fornext.info> #29
Please fix it!
dw...@gmail.com <dw...@gmail.com> #30
Hey All, good news. Appears to be fixed. I can finally go back to using Calengoo instead of the dreadful Task app.
ca...@gmail.com <ca...@gmail.com> #31
Yes. Working for me too. Thank you Google developers.
an...@gmail.com <an...@gmail.com> #32
Yes, works, and nicely: just change a task in CalenGoo, and it gets re-aligned in Google.
But one funny new (?) bug: onhttps://calendar.google.com the blue dot with the present date is on the wrong date, ha ha. Attached is a screenshot is of today, May 21, but the blue dot is on May 5.
Oops, now, 30 minutes later the blue dot is on May 21 correctly.
But one funny new (?) bug: on
Oops, now, 30 minutes later the blue dot is on May 21 correctly.
ek...@google.com <ek...@google.com> #33
This issue should now be fixed, let us know if you are still seeing the problem.
ju...@gmail.com <ju...@gmail.com> #34
I think that the problem is back today. My Google Calendar was not showing any tasks due this week!
I use CalenGoo on Android. None of the tasks that I created or edited in CalenGoo appear on the Google Calendar, but they do appear in the Tasks panel on the right hand side of Google Calendar.
If I change the due date in CalenGoo, the due date in the Tasks panel is also changed, but the task still doesn't appear on the Calendar.
If I change the due date in the Tasks panel, the task appears on the calendar (on the new date).
I use CalenGoo on Android. None of the tasks that I created or edited in CalenGoo appear on the Google Calendar, but they do appear in the Tasks panel on the right hand side of Google Calendar.
If I change the due date in CalenGoo, the due date in the Tasks panel is also changed, but the task still doesn't appear on the Calendar.
If I change the due date in the Tasks panel, the task appears on the calendar (on the new date).
d....@googlemail.com <d....@googlemail.com> #35
I have already created a new bug report for that problem yesterday:
https://issuetracker.google.com/issues/133809207
Please "star" it by clicking the star in the upper left corner if you are interested in Google fixing it. :-)
Please "star" it by clicking the star in the upper left corner if you are interested in Google fixing it. :-)
ca...@gmail.com <ca...@gmail.com> #36
Problem has returned? Create task on the web and then change the date on the web. Changes are not reflected on the Calengoo app.
d....@googlemail.com <d....@googlemail.com> #37
Now it is a new problem that is even worse, because it now affects all fields (title, notes, due date). I have reported it here:
https://issuetracker.google.com/issues/136123247
and here:
https://issuetracker.google.com/issues/136738290
Please "star" both issues if you have problems syncing tasks.
and here:
Please "star" both issues if you have problems syncing tasks.
ma...@gmail.com <ma...@gmail.com> #38
Please fix it !
je...@gmail.com <je...@gmail.com> #39
It's not working.. if you set date and time, API will only return date, (For instance 2020-02-13T00:00:00.000Z) not time..
Please fix this
Please fix this
se...@gmail.com <se...@gmail.com> #40
+1
in...@mdwd.org <in...@mdwd.org> #41
+1
ek...@google.com <ek...@google.com>
lu...@gmail.com <lu...@gmail.com> #42
Google, please allow devs to use the same api as google calendar app does (due times are working correctly there).
em...@gmail.com <em...@gmail.com> #43
+1
wo...@gmail.com <wo...@gmail.com> #44
+1
an...@gmail.com <an...@gmail.com> #45
+1
ya...@gmail.com <ya...@gmail.com> #46
+1
an...@gmail.com <an...@gmail.com> #47
+1
da...@gmail.com <da...@gmail.com> #48
How is this not fixed after 3 years?
The suspicion must be Google's bad faith. This API is broken by policy.
Please Google, don't be evil.
The suspicion must be Google's bad faith. This API is broken by policy.
Please Google, don't be evil.
lu...@gmail.com <lu...@gmail.com> #49
Shameful
ri...@gmail.com <ri...@gmail.com> #50
+1 but I will probably abandon Google Tasks because of this.
vi...@gmail.com <vi...@gmail.com> #51
+1
in...@gmail.com <in...@gmail.com> #52
+1
ro...@gmail.com <ro...@gmail.com> #53
+1
[Deleted User] <[Deleted User]> #54 Restricted
Restricted
Comment has been deleted.
[Deleted User] <[Deleted User]> #55
Add commander
ri...@gmail.com <ri...@gmail.com> #56
+1
da...@gmail.com <da...@gmail.com> #57
Please be evil. We understand.
ni...@nickbetcher.com <ni...@nickbetcher.com> #58
Comment has been deleted.
so...@gmail.com <so...@gmail.com> #59
+1
ez...@gmail.com <ez...@gmail.com> #60
+1
ma...@gmail.com <ma...@gmail.com> #61
+1
na...@gmail.com <na...@gmail.com> #62
+1
dl...@gmail.com <dl...@gmail.com> #63
+1
fl...@inovex.de <fl...@inovex.de> #64
C'mon, almost 5 years and not even a comment why it isn't fixed? That's really not nice!
rv...@gmail.com <rv...@gmail.com> #65
+1
fa...@gmail.com <fa...@gmail.com> #66
Wtf google
vi...@turtlepic.com <vi...@turtlepic.com> #67
How disappointing to see a 5 year old issue is still not fixed. I use Google Workspace for all my startup infra, and yet such a basic functionality seems to be missing.
ps...@gmail.com <ps...@gmail.com> #68
Agreed that this is frustrating that this has not been fixed after 5 years. Do they ignore comments on bugs that never marked as fixed? Do we need to open a new ticket? Since feedback would be very appreciated, Google.
lu...@gmail.com <lu...@gmail.com> #69
Jesus. How long will it take Google? 5, 10 more years?
sn...@gmail.com <sn...@gmail.com> #70
I have decided not to support Google Task API, because obviously they don't want developer using Google Tasks since they refuse to provide the most basic functionality.
me...@gmail.com <me...@gmail.com> #71
+1
Description
If the due date of a task has been set on
Detailed description of the problem:
Recently a new function has been added to
Probably the Google Tasks API has to copy its due date into the new due date field that was added somewhere internally when adding support for a due time.