sootsim report-issue

sootsim report-issue

Preview and submit a missing or broken SootSim compatibility report. The command attaches the local compatibility scan plus CLI, runtime, operating-system, and architecture details. It never attaches source, environment variables, terminal output, logs, screenshots, or app data, and it requires confirmation before sending.

terminal

sootsim report-issue [options] "<description>"

Options

flagdescription
--app <dir>scan a target app directory instead of cwd
--dry-runpreview the attachment summary without sending
-y, --yessubmit after the user has explicitly approved the preview; required in non-interactive sessions

Examples

terminal

sootsim report-issue "react-native-example renders its sheet behind the tab bar"
sootsim report-issue --dry-run "the compat scan does not recognize react-native-example"
sootsim report-issue --yes "react-native-example crashes when opening its picker"

Explicit Feedback, With Bounded Context

Use report-issue when sootsim compat misses a package or the running app exposes a concrete SootSim compatibility gap. The command shows the description and attachment summary before it sends anything.

An interactive terminal asks for confirmation. A non-interactive agent must first show the finding to the user and ask whether to report it. Only after the user explicitly agrees may the agent rerun with --yes. Setup and compatibility scans never submit a report automatically.

The CLI attaches the local compatibility scan and the SootSim CLI/runtime, operating-system, and architecture versions needed to reproduce the gap. It does not attach source files, environment variables, terminal output, logs, screenshots, git data, or app data. Use --dry-run to inspect that attachment summary without sending.

Ready to build?

Run your React Native app in the browser. No simulators, no native toolchain, no waiting.

curl -fsSL https://sootsim.com/install.sh | sh