The unread notification indicator stays on even when I have read everything

[Fil]

Select Topic Area

Bug

Body

For the last 3 or 4 days, the notification indicator is stuck in "unread" state, but my list of notifications shows no unread message. However the pagination element shows “1-0 of 1” (which makes no sense), and the "Inbox", "Participating" and "Mentioned" trays indicate they have 1 message.

I can only guess that a message has been stuck in a bad state that makes it impossible to display, but is still counted. It is annoying because I used to look at my new notifications when this indicator was on.

I hope to either get a fix for my account, or an alternative way to delete this message if my hypothesis is correct.

Note: this is different from https://github.com/orgs/community/discussions/77877

[Fil]

To be sure I created a PAT and called the API:

❯ curl -L \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer ghp_xxxxxx" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/notifications
[

]

the answer came empty.

[StrandedKitty]

Same exact problem with my account, got it around a week ago.

[Fil]

I found a solution by going to the full list, doing "select all", then mark as read.

[Qwerty-Space]

@Fil I don't even have that option

[jhpratt]

Running into this myself. The suggestion from @Fil does not work for me.

[SonoSooS]

Seems like Microsoft is breaking notifications just for the sake of doing something, instead of fixing bugs present since a decade. Because changing something just to make it worse is much better than fixing things, amirite...

Anyway, what you really need to do, is

• get at least 26 real notifications (dig some up from your Done list, move them to inbox)
• check "Select all" checkbox, and wait
• if you truly have at least 26 real notifications, some seconds later a link will show up, suggesting to select all notifications, click that
• go into the "..." menu, and make all of them unread
• refresh the page with CTRL-R (or CTRL-SHIFT-R in Firefox)
• select all notifications with the "select all notifications" link
• make them read
• refresh the page again

How this works, is that when you select all notifications with the link (instead of just the checkbox), it uses a whole entirely different endpoint.
Since the broken notification doesn't show up at all, when you just do "select all", it just selects the IDs you have received from the server, and does an array-based flag endpoint.
However, if you do "select all", it doesn't actually select all, it just makes the frontend code use a whole different set of endpoints entirely. In this case, https://github.com/notifications/beta/unmark and https://github.com/notifications/beta/mark, with a POST payload that looks like this:

authenticity_token=some randomly-generated token&query=&mark_all=1

Sadly I can't figure out how to generate this token, but it seems like you can execute this Javascript in https://github.com/notifications to reproduce the above payload:

(function(doc,endpoint)
{
    const a=doc.querySelector('form[action="'+endpoint+'"]');
    const b=doc.createElement("input");
    b.type='hidden';
    b.name='query';
    b.value="";
    a.appendChild(b);
    const c=doc.createElement("input");
    c.type='hidden';
    c.name='mark_all';
    c.value="1";
    a.appendChild(c);
    a.submit();
})(document,"/notifications/beta/mark");

How this Javascript works, is that the token is already present as a hidden <input> element in a <form>, and the target of the <form> is set to this new beta endpoint. So all I need to do, is add the necessary "query" and "mark_all" request params (otherwise you'll get a HTTP 400 or HTTP 404 or HTTP 500), and submit the form.
If it doesn't work first try, try doing unmark instead of mark first (just edit the string in the last line of the script), then execute the mark one, and the combination of these two seems to make the ghost notification be read. It sadly doesn't get rid of it, but at least the notification bubble goes extinguish :)

[Yogu]

Thank you! The steps worked for me.

[profi200]

This also started to happen for me. Yesterday and today again. Since i have enough notifications in the inbox the mark all as unread and then mark as read trick works. This is really annoying.

First they vandalized the dashboard feed removing the one feature that made it useful (showing commits of repos you follow) and now the notification system that was working perfectly before broke. I don't want a Windows situation where every update breaks something please.

[sgf]

i have the same problem.