DioxusLabs/dioxus · error
No first party renderer feature enabled. It looks like you a
Error message
No first party renderer feature enabled. It looks like you are trying to use a third party renderer. You will need to use the launch function from the third party renderer crate.
What it means
Error "No first party renderer feature enabled. It looks like you are trying to use a third party renderer. You will need to use the launch function from the third party renderer crate." thrown in DioxusLabs/dioxus.
Source
Thrown at packages/dioxus/src/launch.rs:370
#[cfg(feature = "web")]
if matches!(platform, KnownPlatform::Web) {
return dioxus_web::launch::launch(app, contexts, configs);
}
#[cfg(feature = "liveview")]
if matches!(platform, KnownPlatform::Liveview) {
return dioxus_liveview::launch::launch(app, contexts, configs);
}
// If the platform is not one of the above, then we assume it's a custom platform
if let KnownPlatform::Other(launch_fn) = platform {
return launch_fn(app, contexts, configs);
}
// If we're here, then we have no platform feature enabled and third-party-renderer is enabled
if cfg!(feature = "third-party-renderer") {
panic!(
"No first party renderer feature enabled. It looks like you are trying to use a third party renderer. You will need to use the launch function from the third party renderer crate."
);
}
panic!(
"No platform feature enabled. Please enable one of the following features: liveview, desktop, mobile, web, tui, fullstack to use the launch API."
)
}
}
View on GitHub (pinned to 24f6a829df)
Solutions
- No first-party renderer is enabled. Use the launch function from your third-party renderer crate instead of dioxus::launch.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at packages/dioxus/src/launch.rs:370 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/70e25f4a073c944b.
Report an issue: GitHub.