Skip to content

fix(desktop): treat relay-closed mobile pairing as expired - #7372

Open
Chessing234 wants to merge 1 commit into
block:mainfrom
Chessing234:fix/mobile-pairing-relay-closed-as-expired
Open

fix(desktop): treat relay-closed mobile pairing as expired#7372
Chessing234 wants to merge 1 commit into
block:mainfrom
Chessing234:fix/mobile-pairing-relay-closed-as-expired

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Summary

  • The pair-relay closes the socket at 120s before settings recognized session timed out.
  • Treat relay connection closed as expired, matching identity recovery pairing.

Test plan

  • Let a mobile pairing QR sit past the relay timeout and confirm the expired step
  • A real error still shows the error step

Made with Cursor

The pair-relay drops the socket at 120s while settings only recognized session timed out, so users saw a raw transport error instead of the expired step.

Signed-off-by: Taksh <takshkothari09@gmail.com>
@Chessing234
Chessing234 requested a review from a team as a code owner September 5, 2026 07:05
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is f038cbbb0d4092a72ffd93f17916f84d2b39bb43...595d6be0fefebd928295308f45d7524aea6cc6bc.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review 595d6be0fefebd928295308f45d7524aea6cc6bc to authorize a new review.
Any previous review applies only to its recorded range.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant