Troubleshooting
Start with sis doctor: it checks the browser runtime and macOS permissions and says how to fix what’s missing.
“PERMISSION_DENIED” or desktop tests can’t see anything
Section titled ““PERMISSION_DENIED” or desktop tests can’t see anything”macOS hasn’t given the app running Sisyphus the Accessibility permission (Device Control and Data Access on macOS 27+). Grant it to Sisyphus Studio, or to your terminal when you use sis, then restart that app. Studio’s Settings → macOS permissions has a button that opens the right pane.
Screenshots of desktop apps are missing
Section titled “Screenshots of desktop apps are missing”Grant Screen Recording, then restart Sisyphus. Tests run without it; only the screenshots are skipped.
“RUNTIME_MISSING”
Section titled ““RUNTIME_MISSING””The browser runtime isn’t installed. Run sis setup (add firefox or webkit if your tests use them), or use Settings → Web runtime in Studio.
“APP_LAUNCH_FAILED”
Section titled ““APP_LAUNCH_FAILED””- Web: is the app running at that URL? If Sisyphus should start it, add
serve: { command: …, ready: <url> }to the app. - Desktop: check the
bundle,apporexeinsisyphus.yaml.sis appslists running apps with their bundle ids. - Reused apps: the app’s
reuse.checkfailed twice. Run the test with--no-reuseto see whether the app or the check is at fault.
“ELEMENT_NOT_FOUND” for something that’s clearly there
Section titled ““ELEMENT_NOT_FOUND” for something that’s clearly there”- Read did you mean: the name is often slightly different (“Sign In” vs “Sign in”, a trailing “…”).
- Run
sis inspect <app>and copy the selector from there. - The element may be in a different window, dialog or app: scope it (
dialog >> button "OK") or usein:. - It may have no accessible name at all; then fix that in the app, or use an id (
"#save").
“AMBIGUOUS_SELECTOR”
Section titled ““AMBIGUOUS_SELECTOR””Several elements match. The error lists them; narrow with >> (listitem "Milk" >> button "Delete") or a more exact name.
“NOT_INTERACTABLE”
Section titled ““NOT_INTERACTABLE””The element is there but disabled, or something covers it. The error names what’s on top: usually a banner, a dialog or a menu to close first.
“DIALOG_OPEN”
Section titled ““DIALOG_OPEN””A browser alert, confirm or prompt is open and the step wasn’t about it. Answer it first: click: dialog >> button "OK".
A test passes alone but fails in the suite
Section titled “A test passes alone but fails in the suite”Tests share something: data, a signed-in session, a window left open. See Flaky tests.
Typing loses characters in a desktop app
Section titled “Typing loses characters in a desktop app”Some apps drop keys while busy. fill retypes once and fails if the field is still wrong. Add step_delay: 200ms to the app’s tests, or to that test.
Still stuck?
Section titled “Still stuck?”Send the run folder (.sisyphus/runs/<id>/) to your Bussin Bytes contact: it has the result, screenshots and trees.
