docs: note the screenshot fallback when android layout fails - #33
Merged
Conversation
`android layout` cannot dump the view tree on Xiaomi/MIUI devices — it crashes inside MIUI's resource loading on a missing theme_compatibility.xml, regardless of the app under test. The README offered no alternative, which makes the journeys look unrunnable there. Document the annotate/resolve path that does work, including the --screenshot flag name (not --screen) and the need to re-capture after each interaction, since labels are per-screenshot. Co-Authored-By: Claude Opus 5 (1M context) <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
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
android layoutis unusable on Xiaomi/MIUI devices — the dump crashes inside MIUI's own resource loading, regardless of which app is under test:journeys/README.mdrecommendsandroid layout --prettyas the way to inspect a screen and offers no alternative, so on these devices the journeys read as unrunnable. They are not — the annotated-screenshot path works fine, and I used it to drive a journey on this hardware while debugging #32.Documents that fallback so the next person does not have to rediscover it.
Changes
android layoutfails" subsection tojourneys/README.md, covering:screen capture --annotate+screen resolvecommands that work--screenshot, not--screen(easy to get wrong; the error message does not make it obvious)resource-idtest tags are unavailable on this path, so steps fall back to visible textTest plan
Checklist
./gradlew detektpassesChecklist items are unticked rather than N/A: this changes no code, so detekt and the platform runs have nothing to exercise.
Split out from #32 rather than folded into it — that PR is a Claude API fix and this is unrelated. No dependency between them; either can merge first.
🤖 Generated with Claude Code