Skip Navigation

Nonexistent Notification That Won’t Go Away

I have a red circle with a “1” for a notification on the home screen, but I don’t have any unread messages. Any idea what’s causing it or how to correct it?

EDIT: I have 3 accounts added, but I’ve checked all 3, and there’s no unread on any of them.

8

You're viewing a single thread.

8 comments
  • Thanks for pointing this out. It turns out this is actually a bug in the notification server. The server is not sending updates if the unread count is zero, I accidentally introduced this in an update the other day.

    This will be a quick fix, as I’ve already identified the issue. I will update the server this evening and the issue should automatically resolve itself for you. I’m at work right now, but I’ll roll a fix out as soon as I get home.

    • That is awesome! I'm glad that it's an easy fix. THANK YOU!

      • This should be resolved now. Let me know if it is still not working properly for you.

        I also resolved an issue where an incorrect badge count would be displayed when you have unread messages on multiple accounts.

        If you received any duplicate notifications, that’s to be expected from reloading the server. I think I have that fixed for future updates though.

        • It's still showing one notification for me, but I don't have any unread messages. I tried to force quitting and restarting, but no change.

        • Correction, the phantom notification seems to be gone now. Thanks again!

          • I went ahead and rewrote the badge notifications on the server. It will only send updates when needed now, and it should behave better with multiple accounts. It also sends periodic updates in case an case of a failure to receive a notification on the device. I also have an update for Arctic coming soon that will locally update the badge whenever you change the notification settings.

            Hopefully that resolves these issues, please let me know if you encounter anymore issues.

          • That’s good. I’m still looking into this though, because that should have updated a lot quicker than that.

8 comments