False "3 unread" notification badge persists on notifications icon

[Shu-Ji]

Select Topic Area

Product Feedback

Body

The notifications icon in the top navigation bar constantly shows a badge indicating "3 unread" messages.

However, when I click on the icon and view the notifications list, the three supposed unread items are not visible. The list appears to be empty or does not actually contain any unread notifications that I can view or interact with.

This issue persists across page refreshes and has been occurring for many days.

Chrome 141.0.7390.78
macOS 26.0.1

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[davevad93]

Hi @Shu-Ji,

You can find a workaround here. Open your browser console, type allow pasting, then copy and paste the following code into your browser console and execute it (you may need to run it multiple times for it to take effect.):

(function(){var f=document.querySelector('.js-notifications-mark-all-actions form[action="/notifications/beta/mark"]');if(f){fetch(f.action,{method:f.method,body:new FormData(f),credentials:"include"}).then(r=>{if(r.ok)setTimeout(()=>location.reload(),500);});}})();

[jimdigriz]

@davevad93 Please do not call this a solution, 'solutions' can be ignored, whilst 'workarounds'/hacks cannot :)

We have to be clear to everyone that all this does is plaster over the problem until the next batch of "you have no access to read" notifications comes through from a private repo.

For example, a persistent side effect is when I use this workaround, I still am 'following' the private repo I have no access to and it remains listed in the left sidebar.

GitHub need to fix this, none of us can.

[davevad93]

Hey @jimdigriz, yes, you're absolutely right, this is more of a workaround than a definitive solution, I should have chosen my words better, (I'll update the comment properly) and yes, GitHub should fix this.

If you look at the discussion via the link I provided above, one of these "workarounds" has been provided by GitHub Support itself. The discussion dates back to October 28, 2021, so it's almost four years old, and they still haven't fixed it, which makes me wonder if they intend to.

[jimdigriz]

and they still haven't fixed it, which makes me wonder if they intend to.

...probably not, unless they can get Copilot/AI shoved into the 'fix'. :-/

[xiaoxustudio]

I also have the same problem, which makes me unsure whether there was actually a notification or not.

[xiaoxustudio]

I also have the same problem, which makes me unsure whether there was actually a notification or not.我也遇到了同样的问题，这让我不确定是否真的有通知。

We hope to solve this problem, which has existed for at least several months.

[ChristinWhite]

Oh good, it's not just me. I really hope GitHub looks into this problem soon. It was helpful to learn that it's being caused by a private repo, I couldn't figure out how I had a notification from a non-existent repo and hadn't considered just loosing access to one.

[aimuz]

Please refer to this link to eliminate the annoying points.
https://github.com/orgs/community/discussions/111157

[Stephlovesone]

Many users are also in this situation. I hope the team resolves this soonest 🙏

[faridvatani]

I tested this solution, and it worked. Create the token only through Notifications Access.
https://github.com/orgs/community/discussions/111157#discussioncomment-8836967