makeplane / makeplane/plane

[bug]: cannot read notifications

Open
#8,521 1 comment 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Jan 9, 2026.

🐛bug plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior

In the Plane UI, I see a red dot on top of an icon that looks like a tray or inbox. When I click on it, a side panel opens up that says "All (5)", and nothing else. I expect to see content for five notifications.

I am using Firefox 146.0.1 (64-bit) (Mozilla Firefox Snap for Ubuntu) with a self-hosted installation of Plane. When I click on the question icon, I can see that it says "Version: v2.0.0".

I have the following observations.

  • When I have web developer tools open, in the network tab, I get a 200 in response to a request ending in users/notifications/?snoozed=false&archived=false&per_page=300&cursor=300:0:0. The response to this request has field "results" with five entries. All five entries have "is_inbox_issue": false.
  • After this request and response goes through, no other requests follow immediately.
  • In the console tab, I see the following error Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Image
Steps to reproduce
  1. From the Plane UI, click on the inbox icon with a red dot.
  2. A side panel opens up that says, "Inbox" at the top with "All" and a number below. No other content is below that.
Environment

Production

Browser

Mozilla Firefox

Variant

Self-hosted

Version

v2.0.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.