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

Resume private mobile share bundles after sign-in #1004

New Issue
Closed
opened 2026-08-17 06:20:24 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-17 06:20:24 +00:00
Member
Copy Link

Problem

The PWA share target stores private text, links, and screenshots in IndexedDB and redirects to ?launch=new&shared=bundle. Anonymous users are then sent through sign-in with that opaque continuation, but frontend/login.js limits shared to five characters and only accepts image. Successful token or passkey authentication therefore lands on Home, leaving the draft stranded on-device.

User impact

A signed-out mobile user can successfully authenticate yet appears to lose the content they shared. The private record also remains retained instead of being consumed once.

Acceptance criteria

  • Token and passkey sign-in preserve exactly ./?launch=new&shared=bundle.
  • The restored New issue flow consumes the private bundle once without putting its contents in the URL.
  • Unknown markers, duplicate keys, extra parameters, fragments, and invalid launch modes still fall back to ./.
  • Focused behavioral tests and the full suite pass.

This is distinct from #903/#904, which introduced private bundle staging and restoration but did not cover the anonymous sign-in boundary.

## Problem The PWA share target stores private text, links, and screenshots in IndexedDB and redirects to `?launch=new&shared=bundle`. Anonymous users are then sent through sign-in with that opaque continuation, but `frontend/login.js` limits `shared` to five characters and only accepts `image`. Successful token or passkey authentication therefore lands on Home, leaving the draft stranded on-device. ## User impact A signed-out mobile user can successfully authenticate yet appears to lose the content they shared. The private record also remains retained instead of being consumed once. ## Acceptance criteria - Token and passkey sign-in preserve exactly `./?launch=new&shared=bundle`. - The restored New issue flow consumes the private bundle once without putting its contents in the URL. - Unknown markers, duplicate keys, extra parameters, fragments, and invalid launch modes still fall back to `./`. - Focused behavioral tests and the full suite pass. This is distinct from #903/#904, which introduced private bundle staging and restoration but did not cover the anonymous sign-in boundary.
timmy was assigned by rockachopa 2026-08-17 06:20:24 +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#1004
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?