fix: relax Android snapshot helper session timeout#796
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
Top changed chunks:
|
|
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
1 participant
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.
Summary
Relaxes the Android persistent snapshot helper session request budget so delayed-but-successful UIAutomator captures do not time out early and fall back to slower one-shot instrumentation. Adds a regression test for delayed session responses. Touched-file count: 2. Scope is Android snapshot helper only; this is separate from replay progress PR #795.
Validation
Verified with focused Android snapshot helper tests, check:quick, and a live Android emulator run against the React Navigation Maestro suite. On Pixel_9_Pro_XL_API_37 / emulator-5554, the patched drawer+screen-layout pair passed 2/2, and the full patched React Navigation Android suite passed 38/38 in 396.5s. The drawer flow improved from the earlier failed/slow state; remaining drawer cost is Android accessibility capture on that screen, not helper fallback.