Notification badge keeps coming back even with no unread notifications

[Arika]

Browser, version and OS: 

Firefox 85.0.2. Windows 10 2004

 

Steps to reproduce/what were you doing before it happened?

N/A

 

What happened?

For the last 2 days i keep getting the notification badge popping up despite clearing it multiple times and confirming i have no new notifications. it's always 2 unless i only have 1 unread notification, any more and it will always show 2. After clearing it, it will stay gone for a few minutes before appearing again. closing the browser and reopening it removes the icon, but it always comes back (same with opening new tabs)

 

What did you expect to happen?

not to show notifications if i don't have any

 

Link to a page where it happened, if applicable: 

all forum pages that are not making a topic

 

Screenshots of the issue, if applicable: 

In the screenshot below i have 2 supposed notifications, clicking the button shows the drop down, but none of them are bold indicating that i have already viewed these.

 

 

and came back

 

 

 

Any other relevant details:

Cleared all cache and website data multiple times but still occurs. Doesn't appear to be my account because it only happens on my desktop. But even disabling all notifications in the notification settings doesn't seem to do anything for it.

 

If it's a cloudflare error, what was the ray ID from the bottom of the error page?

N/A

[LogicalDrm]

The core reason is that you are getting misclick notifications and their sources get removed before you check the bell.

 

Moderators get this constantly with all the spam bots.

[Arika]

11 minutes ago, LogicalDrm said:

The core reason is that you are getting misclick notifications and their sources get removed before you check the bell.

 

Moderators get this constantly with all the spam bots.

that's what i would have thought originally, but this is still on going as i type this and has been going on for over 24.

[Vishera]

Is it a cookie issue or a server side issue?

[Arika]

3 minutes ago, Vishera said:

Is it a cookie issue or a server side issue?

i have no idea. i cleared all cookies, caches and site data completely from firefox a few times to make sure i did it right and got everything.

[podkall]

If you're like in a thread and someone replies and on bottom left you click view reply, after few seconds the bell might also show you the notification of the same person.

[podkall]

Just happened same thing to me, I was looking at someones post, they replied twice, on bottom left I clicked view comment, (or whatever the button says), and the 2 notifications up top on bell didn't disappear (and than I click on bell and click away and the number goes away)

Edited February 10, 2021 by podkall

[colonel_mortis]

Have you changed the time on your computer recently by any chance?

[Arika]

40 minutes ago, colonel_mortis said:

Have you changed the time on your computer recently by any chance?

Huh. Yes I did for a very brief amount of time before changing it back to auto. 

[colonel_mortis]

16 minutes ago, Arika S said:

Huh. Yes I did for a very brief amount of time before changing it back to auto. 

The problem is most likely that it's cached the notification count from then, and isn't invalidating it because it thinks it's still up to date because of the timestamp. There are 3 options to solve it: wait until the time that it was changed to, at which point it will start working again; clear the local storage (sometimes called something like stored site data) in your browser (in the same place as clearing cookies, but it's sometimes a separate option); or open the dev tools and run

ips.utils.db.removeByType("notifications")

 

[Arika]

18 minutes ago, colonel_mortis said:

ips.utils.db.removeByType("notifications")

that looks like it did it. i hit enter and it even said

 

ips.utils.db.removeByType("notifications")
>2

the number 2 is haunting me

[Vishera]

9 hours ago, colonel_mortis said:

because of the timestamp

Can't you timestamp it with server time instead of the time of the device?

Using server time should solve the issue.

[colonel_mortis]

13 hours ago, Vishera said:

Can't you timestamp it with server time instead of the time of the device?

Using server time should solve the issue.

This is specifically caching the return value in the browser, so we don't have access to the server time at that point. There are other ways to solve it, but it's hardly a common issue.