stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Recover mobile notification setup after permission is blocked #1132

New Issue
Closed
opened 2026-08-19 13:23:22 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-19 13:23:22 +00:00
Member
Copy Link

Evidence

Mobile Device Setup currently repeats the notification permission request after denial and only tells users to visit browser settings. Returning to the app rerenders readiness but cannot resume the explicit update/deadline setup intent (frontend/push-notifications.js, frontend/mobile-device-setup.js, frontend/dashboard.js). The complete issue and PR title history contains no notification-permission recovery flow; #715/#716 configured deadline time and #1120/#1121 added delivery health only after subscription.

User outcome

A mobile user who blocked notifications can open browser settings guidance, return, check permission again without another prompt, and finish the update or deadline setup they already requested. Selected deadline hour and horizon remain intact.

Acceptance

  • Opening/rerendering Device Setup never prompts for permission.
  • A denied explicit setup action changes the action to Check again with browser-settings guidance.
  • Check again while denied makes no subscription/server mutation.
  • After permission is granted externally, Check again creates at most one subscription and resumes the pending update or deadline intent once.
  • Subscription/network failure stays visible and retryable.
  • Recovery controls remain phone touch-safe and existing Today detour behavior is preserved.
  • Focused behavioral tests and full suite pass.
## Evidence Mobile Device Setup currently repeats the notification permission request after denial and only tells users to visit browser settings. Returning to the app rerenders readiness but cannot resume the explicit update/deadline setup intent (`frontend/push-notifications.js`, `frontend/mobile-device-setup.js`, `frontend/dashboard.js`). The complete issue and PR title history contains no notification-permission recovery flow; #715/#716 configured deadline time and #1120/#1121 added delivery health only after subscription. ## User outcome A mobile user who blocked notifications can open browser settings guidance, return, check permission again without another prompt, and finish the update or deadline setup they already requested. Selected deadline hour and horizon remain intact. ## Acceptance - Opening/rerendering Device Setup never prompts for permission. - A denied explicit setup action changes the action to **Check again** with browser-settings guidance. - Check again while denied makes no subscription/server mutation. - After permission is granted externally, Check again creates at most one subscription and resumes the pending update or deadline intent once. - Subscription/network failure stays visible and retryable. - Recovery controls remain phone touch-safe and existing Today detour behavior is preserved. - Focused behavioral tests and full suite pass.
timmy was assigned by rockachopa 2026-08-19 13:23:22 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1132
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?