Bug: ghost notifications #6874
-
See the screenshot. I must have 5 notifications I cannot see, as the bell has the blue dot, and the pagination shows I'm viewing notifications "1-0 of 5". Note I've tried clearing browser cache already. |
Beta Was this translation helpful? Give feedback.
Replies: 27 comments 76 replies
-
I shouldn't have any unread notifications or I have an unread notification I am unable to see. This doesn't seem device-based to me, as I'm getting the same notification behavior in the Github iOS app. Exactly similar scenario from me @jackrosenthal: I'm currently on Chrome 95.0.4638.54 running on an arm-based mac. I also get the same "ghost" notification via the iOS app: |
Beta Was this translation helpful? Give feedback.
-
Can confirm, except for me its 1 notification |
Beta Was this translation helpful? Give feedback.
-
Can confirm here as well with 1 notification |
Beta Was this translation helpful? Give feedback.
-
Same here, not device specific, or app specific, or network environment specific. |
Beta Was this translation helpful? Give feedback.
-
I am also experiencing this bug. |
Beta Was this translation helpful? Give feedback.
-
I also have 2 ghost notification from this repo edit: I've revoked all my other session and still have blue dot |
Beta Was this translation helpful? Give feedback.
-
Just noticed this is a discussion, anyone open an issue? |
Beta Was this translation helpful? Give feedback.
-
Experiencing the same issue on Safari v15.1 Notifications bell has blue dot and count is "1-0 of 2". Clearing cache doesn't change the outcome. |
Beta Was this translation helpful? Give feedback.
-
Now the unreads disappeared... |
Beta Was this translation helpful? Give feedback.
-
Seem solved here. If have more than 25, can truly select all and mark as read. |
Beta Was this translation helpful? Give feedback.
-
Still seeing this issue on my end, and I can't fix it cause I only have 13 items in "Done". I've no clue where this ghost notification is coming from! |
Beta Was this translation helpful? Give feedback.
-
No unfortunately it's grouped as a single thread. Thanks anyway and sorry
for the delay!
Il gio 6 gen 2022, 16:15 Seggan ***@***.***> ha scritto:
… Reply again, I marked the earlier one as done
—
Reply to this email directly, view it on GitHub
<#6874 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABAGR3QGOPAJ62BX5HXZP3UUWW2XANCNFSM5G3Z3G5Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Same issue / opened a ticket today |
Beta Was this translation helpful? Give feedback.
-
Same issue with 4 ghost nitifications 😭 |
Beta Was this translation helpful? Give feedback.
-
I filed a GitHub support issue about this and got a response with a pretty good workaround:
Cleaned up my ghost notification at least! |
Beta Was this translation helpful? Give feedback.
-
Finally get rid of it 😭
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I had the same issue as @Anonymitaet - if you are part of an org that requires single sign on, and you are not authenticated, you'll see the unread count includes notifs from that org but it won't show the actual notifications. Just sign into any other orgs you are a member of to ensure you are seeing all their notifications. |
Beta Was this translation helpful? Give feedback.
-
Same issue / opened a ticket today |
Beta Was this translation helpful? Give feedback.
-
Obligatory "this still happens in 2024" comment. |
Beta Was this translation helpful? Give feedback.
-
I had this today, and I can pinpoint my case to a certain event: Yesterday, at 2024-03-05 03:28 UTC, I received a notification by email that "no198", a user who doesn't seem to exist anymore, commented on this gist that doesn't exist anymore. The comment mentioned 50 Github users, all in my username's alphabetic range (Sil... through Sin...), and said nothing else. I assume: He was a spambot and he already got moderated. Still, his gist comment produced a ghost notification. I'm posting this in hope that it's useful evidence for the Github devs. As usual for this bug, my list showed "1-0 of 1", and I couldn't list the ghost notification. The token/curl solution from 2022-05-31 worked for me, thanks! The unread/read solution from 2023-01-05 failed for me. I'm not a member of any organization. |
Beta Was this translation helpful? Give feedback.
-
This is still happening in 2024 |
Beta Was this translation helpful? Give feedback.
-
Just started getting this recently, one ghost notification |
Beta Was this translation helpful? Give feedback.
-
If only GitHub would be an open source app so we could actually fix this. |
Beta Was this translation helpful? Give feedback.
-
So we now have large-scale confirmation of the bug, a pretty good diagnosis, a workable but grotty workaround. What do we do to get GitHub to fix this issue? |
Beta Was this translation helpful? Give feedback.
I filed a GitHub support issue about this and got a response with a pretty good workaround: