[BUG] NotificationBell silently ignores notification API failures

[joshnajojo12]

Problem

The NotificationBell component currently swallows notification-related API failures without providing any feedback to the user.

Examples:

catch {
  // silent fail
}

and

fetch("/api/notifications", { method: "PATCH" }).catch(() => {});

When these requests fail:

• Users are not informed that notifications could not be loaded.
• Notification data may become stale.
• Read/unread status can become inconsistent if the mark-as-read request fails.
• Failures become difficult to identify and debug.

Current Behavior

• Failed notification fetch requests are silently ignored.
• Failed mark-as-read requests are silently ignored.
• Users receive no indication that an error occurred.

Expected Behavior

The component should provide clear feedback when notification-related requests fail.

The UI should distinguish between:

1. Loading notifications
2. No notifications available
3. Failed notification requests

Mark-as-read failures should also be handled gracefully.

Proposed Solution

• Add a dedicated error state for failed notification fetch requests.
• Display a user-friendly error message when notifications cannot be loaded.
• Handle mark-as-read request failures appropriately.
• Avoid silently swallowing API errors.
• Preserve the existing notification functionality and user experience.

Benefits

• Improves reliability and user experience.
• Prevents confusion caused by stale notification data.
• Makes notification behavior more predictable.
• Provides better visibility into API failures.

File

src/components/NotificationBell.tsx

[joshnajojo12]

Hi @Priyanshu-byte-coder

I reviewed the NotificationBell component and noticed that notification fetch failures and mark-as-read request failures are currently handled silently, which can lead to stale notification data and inconsistent read/unread states.

I would like to work on improving the error handling and user feedback for this component under GSSoC'26.

Could you please assign this issue to me?

Thank you!

[srinidhi-2006-bit]

/assign

[github-actions]

Assigned to @joshnajojo12! You have 7 days to open a PR. No PR after 7 days = auto-unassigned so others can pick it up. Good luck!

[github-actions]

Hey @joshnajojo12 — this issue was assigned 7 days ago with no PR opened. Unassigning so others can pick it up.

Still working on it? Drop a comment and request re-assignment.