Troubleshooting

Login or organization access failsCopy Anchor Link

From any directory, inspect your CLI settings without printing the saved credential:

reprolane config show --json

Check the API URL, app URL, and destination organization. REPROLANE_API_KEY overrides saved credentials, so check whether your shell or CI provides it. Run reprolane login again for the intended deployment. Saved credentials remain until a new login succeeds.

Create or join an organization before capture. Set defaultOrgId or pass --organization. An organization API key must use its own organization. If a reproduction URL denies access, check the browser account and sharing permissions too.

If capture allowance is exhausted, ask an owner about your plan or wait until the next UTC calendar month. Allowance is checked before capture and again at upload confirmation.

Upload review blocks the captureCopy Anchor Link

Read the file selection and privacy report. Correct the destination or policy before consenting. Include rules cannot restore ignored or denied files. Keep credentials out of source and policy files.

In automation, provide a reviewed policy and --consent-upload for each invocation. --json and nonterminal sessions never prompt. Missing consent and privacy failures exit with code 2.

Missing required replay inputs need correction or an explicit capture only choice. --capture-only does not bypass privacy checks. If a bundle is too large, exclude unnecessary source; frozen source has a 100 MiB limit and archive limits also apply.

Screenshots and recordings remain excluded unless their exact bytes are reviewed and approved. In automation, enabling the category alone is insufficient; the policy also needs the reviewed digest. See privacy review.

The command does not failCopy Anchor Link

Run the command directly in the same app directory and confirm the selected bug still occurs. Quote the complete command passed to capture command. Use --allow-success only when deliberately capturing a successful run.

The captured command and CLI have separate exit statuses. CLI exit 0 can mean a failing test was captured and uploaded successfully.

Browser or scenario startup failsCopy Anchor Link

Install local dependencies before capture. Interactive capture needs a desktop display and browser tools, which may download on first use. Check the CLI's browser startup error for missing system requirements.

When connecting, start your app on the exact selected port. With an authored manifest, --connect uses its port and leaves the server running. Without --connect, leave the port available for Reprolane to start the app.

Check the startup command, readiness path, initial route, and selectors. A project without a dev script needs --start. Local app network access does not change isolated replay network permissions.

Clean replay is unavailable or failsCopy Anchor Link

Read Replay readiness, the eligibility reason, and the full verification report. Check for a complete failure baseline, selected required files, supported runtime, setup commands, environment names, and fixture services.

Local scenario capture skips setupPlan. A setup that only works because your machine already has generated files or dependencies may fail in replay. Correct the setup and capture again as needed.

Provider and setup failures are execution errors, not evidence that the bug is fixed. If source changed after a run, request current verification when eligible. If the terminal is suspended or disconnected, follow terminal recovery.

Gather a useful reportCopy Anchor Link

Include the CLI version, operating system, workflow, and sanitized error text. Keep API keys, customer source, personal data, and private URLs out of public reports. Consult command help from any directory for your installed version:

reprolane capture command --help
reprolane capture scenario --help

For a fresh starting point, return to the quickstart.