+ Add Question

Badge Numbers Updating Inconsistently

D

The badge number updates very inconsistently. Many times, in order to get it to update, I have to go into the app and manually update a date (even though it already says today) for it to update the badge icon. One of the major reasons that I picked ToDoist is for its push sync of the badge icon. I need to know at a glance how many tasks I have.

Some of the time it works, much of the time it doesn't. I want to stay with ToDoist, but as silly as it may seem to some, I have to be able to rely on it to be accurate and up to date. Having used it for several months now, through a few updates, this behavior has not gotten better.

All responses

Brendon Wadey staff
Replied on Mar 20, 2014 - 17:45 UTC

Hi Darren,

Which version of iOS are you running, and are you updated to the latest version of our app? There is a version coming soon (waiting on Apple) that may address this issue, but was not one of the main fixes.

Have you tried logging out and back in again to the app? Also, so it's always (when not working) showing less then the correct account, or does it sometimes show more?

Regards,
Brendon.

D
darren.behan premium
Replied on Mar 20, 2014 - 19:51 UTC

Hey, Brandon

I am running iOS 7.1 and the latest version of the app. Logging off and back on does not solve it for more than a day. The badge count is always less, usually there isn't one as I move all tasks that are due to the next day, then the badge does not update when the next day comes.

db

>

David Trey staff
Replied on Mar 20, 2014 - 23:42 UTC

Hello Darren,

Please tell us, is the difference in the count the same as the difference between your tasks due today and overdue?

In other words - does it show only an overdue task count or only a today task count instead of a combined count?


Best regards,
David

D
darren.behan premium
Replied on Mar 21, 2014 - 00:32 UTC

It's difficult for me to say since on a daily basis, I roll forward incomplete tasks. For me, it means that no badge shows up. I'll try to leave an over due task tonight & see what happens.

db

>

D
darren.behan premium
Replied on Mar 21, 2014 - 11:42 UTC

So what happens when a day passes with an overdue task and tasks set for today is that the badge count remains at yesterday's count (in this case 1). Whats more when I open the app, it shows the overdue task under the today heading, today's tasks under tomorrow, etc. Pull to refresh does not resolve this. It is only after I make a change to a task that ToDoist realizes what day it actually is, reorders the task under the right headings, and correctly displays the badge count.

Basically, it seems like ToDoist is not moving gracefully from one day to the next and refreshing anything properly.

db

>

David Trey staff
Replied on Mar 21, 2014 - 12:51 UTC

Darren,

This sounds like a typical issue that's caused by an incorrect time zone. Please make sure that you're using the same correct time zone on your device and also within Todoist's settings. Did Todoist ask you to adjust the time zone during the DST change? If not or if it did and you've rejected, then this can cause such problems like tasks displayed below different dates and the badge counting them incorrectly thinking it's a different day.


Best regards,
David

D
darren.behan premium
Replied on Mar 21, 2014 - 13:03 UTC

I go between time zones twice a week and I accept the change every time.

It is my understanding that ToDoist assigns a date/time to the task so even not changing the time zone, it should eventually catch up. That is, if my time zone difference is an hour, by 1 AM, tasks should appear on the right dates - which is not happening.

I have posted a separate thread about how time zones should be seamless and not require user intervention. I think ToDoist is a great app/platform but it has some real challenges with time zones. It's the only app I have ever used that requires me to take an action vs. just dealing with it.



db

>

David Trey staff
Replied on Mar 21, 2014 - 13:10 UTC

Darren,

If a task is due "tomorrow", then on the back-end, it has a date: 2012-3-22T23:59 if you then travel between time zones, even within 1 hour, it may be interpreted as 2012-3-23T00:59.

We'll look into it and improve time zone handling, though in this particular case, it could be a sync-related issue if making changes actually corrects the count and days, we'll look into this too. Sorry for the inconvenience.


Best regards,
David

D
darren.behan premium
Replied on Mar 21, 2014 - 13:21 UTC

No worries. I appreciate you guys looking into it and the quick attention you have given to this (and all) of my questions.

If I can be of any assistance in any way, please let me know.

db

>