Repository navigation
Conversation
The Android e2e job fails `prewarm › accepts idle SDK readiness after the loading deadline` on master and on every PR run with `Render timeout: Element did not mount within 1000ms`. No `render` call in the prewarm, example or auth flow suites passed a timeout, so each used the harness default of 1s. The failing test is the first in its file: its render creates the process's first native WebView, which on the CI Android emulator takes longer than that. Later renders get a warm WebView and fit, which is why only that one test fails and iOS never does. Every render in those suites now passes a 10s mount timeout, matching the dark theme suite, so a change in test order cannot move the failure elsewhere. What the tests assert is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
The Android e2e job fails on
masterand on every PR run:It isn't the prewarm logic. The test never gets past
render.Why
None of the
rendercalls inprewarm.harness.js,example.harness.jsorauthFlow.harness.jspass atimeout, so each uses the harness default of 1s.The failing test is the first in its file. Its render creates the process's first native WebView,
and on the CI Android emulator that cold start takes longer than a second. Later renders get a
warm WebView and fit inside 1s. That's why only this one test fails, why it fails every time, and
why iOS (faster WebView creation) never hits it.
darkTheme.harness.jshas always passed a 10s mount timeout, which is why it never hit this.Change
Every
renderin the three suites now passes a 10s mount timeout (MOUNT_OPTIONS), not just thefailing one, so a change in test order can't move the failure to another test. What the tests
assert is unchanged.
Not covered
example.harness.js › opens, dismisses, and reopens the live demo challengealso failed once onmaster's Android run with a different error (
expected [] to have a length of 1). It talks to thelive hCaptcha demo and passed on the two PR runs since, so it looks like network flakiness, not
this bug.
Unblocks the e2e checks on #120.
🤖 Generated with Claude Code