Skip to content

Version 2.11.1#72

Merged
hynek-urban merged 4 commits into
mainfrom
dev
May 14, 2026
Merged

Version 2.11.1#72
hynek-urban merged 4 commits into
mainfrom
dev

Conversation

@hynek-urban
Copy link
Copy Markdown
Collaborator

  • Don't crash the prepare flow when the browser closes during Google login detection.
  • Increase timeouts.

boweiliu and others added 2 commits May 5, 2026 10:17
The login detector for `auth browser-prepare google-*` listens for
console.cloud.google.com responses and asynchronously reads each
response body to decide whether the user is past the sign-in page.
That `response.text()` promise has no `.catch()` handler, so when the
page or context closes while a body is still being read (e.g. the
automation navigates onward, or the user closes the browser window),
Node sees an unhandled rejection and terminates the entire prepare
process — at which point any GCP project / OAuth client already
created by the flow is orphaned in the user's account because
latchkey never reaches the point where it persists the credentials.

Add a `.catch()` that swallows the closed-page rejection. The login
detector treats a response we couldn't read as inconclusive (same as
not seeing it at all), so this is behaviour-preserving for the happy
path and only changes the failure mode for the closed-page race from
"crash the process" to "keep polling until login is detected or the
flow times out".

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…ed-rejection

Don't crash the prepare flow when the browser closes during Google login detection
Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vet found 0 issues.

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vet found 0 issues.

@hynek-urban hynek-urban merged commit 0ae0ba2 into main May 14, 2026
3 checks passed
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.

2 participants