DioxusLabs/dioxus · error · anyhow::Error

Application [{bundle_format}] exited with error: {status}

Error message

Application [{bundle_format}] exited with error: {status}

What it means

Exit-status report in the run loop: the spawned application process for a bundle format terminated (ProcessExited) with a non-success ExitStatus, so its output is treated as an erroneous run. This reports the app's own exit code — the application crashed or exited non-zero — not a build failure; the distinguishing input is the child process's exit status.

Source

Thrown at packages/cli/src/cli/run.rs:154

                        BuilderUpdate::CompilerMessage { message } => {
                            print!("{message}");
                        }
                        BuilderUpdate::BuildFailed { err } => {
                            tracing::error!("❌ Build failed: {}", err);
                            return Err(err);
                        }
                        BuilderUpdate::StdoutReceived { msg } => {
                            tracing::info!("[{bundle_format}] {msg}");
                        }
                        BuilderUpdate::StderrReceived { msg } => {
                            tracing::error!("[{bundle_format}] {msg}");
                        }
                        BuilderUpdate::ProcessExited { status } => {
                            if !status.success() {
                                tracing::error!(
                                    "Application [{bundle_format}] exited with error: {status}"
                                );
                                bail!("Application [{bundle_format}] exited with error: {status}");
                            }

                            break;
                        }
                        BuilderUpdate::ProcessWaitFailed { err } => {
                            return Err(err.into());
                        }
                        BuilderUpdate::ProfilePhase { .. } => {}
                        BuilderUpdate::DepInfoDiscovered { .. } => {}
                    }
                }
                ServeUpdate::Exit { .. } => break,
                ServeUpdate::NewConnection { .. } => {}
                ServeUpdate::WsMessage { .. } => {}
                ServeUpdate::FilesChanged { .. } => {}
                ServeUpdate::OpenApp => {}
                ServeUpdate::RequestRebuild => {}
                ServeUpdate::CycleHotreloadMode => {}

View on GitHub (pinned to 24f6a829df)

Solutions

  1. The application exited with an error status. Check the application logs and fix the runtime failure.
Defensive patterns

Strategy: try-catch

When it happens

Trigger: Thrown at packages/cli/src/cli/run.rs:154 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of DioxusLabs/dioxus@24f6a829df (2026-08-23). Data as JSON: /api/errors/4e925c9de3b42de7. Report an issue: GitHub.