Add notification auto-refresh and tab re-entry refresh #89

New issue

Open

opened 2026-07-11 21:44:31 +00:00 by starsetbyte · 0 comments

starsetbyte commented

2026-07-11 21:44:31 +00:00

Owner

Current gap

Notifications currently load through the paged notification repository, but the long-term plan called for foreground refresh and refresh when returning to the Notifications tab.

Scope

Define the refresh cadence and lifecycle rules.
Refresh on tab re-entry without duplicating requests or resetting pagination unexpectedly.
Keep unread state and updateSeen behavior coherent during refresh.
Handle background/foreground transitions, account switching, offline mode, and concurrent refreshes.

Acceptance criteria

A documented policy defines when refreshes occur and when they do not.
New notifications appear without a manual pull-to-refresh in the supported foreground cases.
No duplicate notifications, cursor corruption, or unread-count regressions occur.
Unit tests cover refresh cancellation/concurrency and a device check covers tab re-entry.

## Current gap Notifications currently load through the paged notification repository, but the long-term plan called for foreground refresh and refresh when returning to the Notifications tab. ## Scope - Define the refresh cadence and lifecycle rules. - Refresh on tab re-entry without duplicating requests or resetting pagination unexpectedly. - Keep unread state and `updateSeen` behavior coherent during refresh. - Handle background/foreground transitions, account switching, offline mode, and concurrent refreshes. ## Acceptance criteria - A documented policy defines when refreshes occur and when they do not. - New notifications appear without a manual pull-to-refresh in the supported foreground cases. - No duplicate notifications, cursor corruption, or unread-count regressions occur. - Unit tests cover refresh cancellation/concurrency and a device check covers tab re-entry.

starsetbyte added the

enhancement

notifications

labels

2026-07-11 21:44:31 +00:00