This section covers the most common issues you may encounter with Quash and Mahoraga. Use the descriptions below to find the right page for your problem.Documentation Index
Fetch the complete documentation index at: https://quashbugs.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Device & Setup Issues
→ Connecting Devices & Setup Start here if you cannot get a device to appear in Quash, or if Mahoraga is not configuring correctly on a physical device. Covers:- Device not appearing after “Scan for devices”
- Mahoraga accessibility service won’t enable
- Bounding boxes misaligned on physical devices
- Cloud devices showing as busy or auto-disconnecting
- Android emulator or iOS simulator not detected
- WDA Install Error
- Command line Error
Test Run Issues
→ Test Runs & Results Start here if a test starts but does not complete as expected, returns inconsistent results, or produces no report. Covers:- Understanding Partial Success, Failure, and inconsistent outcomes
- Tests passing locally but failing in CI
- Flaky tests (inconsistent pass/fail without code changes)
- Agent tapping in the wrong location
- Credentials not working during runs
- Run completing but report is empty or missing
Test Studio & Recipe Issues
→ Test Studio & Megumi Agent Start here if the Recipe agent is generating poor-quality tests, losing context between prompts, or not updating the Tests panel as expected. Covers:- Recipe generating generic tests with no app-specific detail
- Recipe not remembering previous session context
/compactnot working as expected- Tests panel not updating after a prompt
- Figma attachments not providing context
- Recipe producing duplicate test cases