Skip to content

bridgestate: report phone not ready after waiting for activation - #97

Closed
Fizzadar wants to merge 1 commit into
mainfrom
nick/surface-phone-not-ready
Closed

Fizzadar wants to merge 1 commit into
mainfrom
nick/surface-phone-not-ready

Conversation

@Fizzadar

Copy link
Copy Markdown
Member

If the phone never marks the session active, the bridge stays in the connecting state, which isn't sent to the HTTP status endpoint, so the user sees nothing. After 15 minutes without activation, report a transient disconnect (`gm-phone-not-ready`) with OPEN_NATIVE and a message asking the user to open Google Messages on their phone. It clears back to connected once the phone sends BROWSER_ACTIVE.

🤖 Generated with Claude Code

If the phone never marks the session active the bridge stays in the
connecting state forever, which the HTTP status endpoint never sends.

After 15 minutes without activation, report a transient disconnect
asking the user to open Google Messages on their phone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tulir

tulir commented Oct 13, 2026

Copy link
Copy Markdown
Member

Sounds suspicious, is there something wrong in practice? I'm pretty sure I already told the bridge not to get stuck in connecting

@Fizzadar

Copy link
Copy Markdown
Member Author

Yep - you covered it already - only gap is if a phone pings but never sends browser active which we've literally never seen before -> closing!

@Fizzadar Fizzadar closed this Oct 13, 2026
@Fizzadar
Fizzadar deleted the nick/surface-phone-not-ready branch October 13, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants