bevyengine/bevy · error

Failed to create file watcher from path {path:?}, {e:?}

Error message

Failed to create file watcher from path {path:?}, {e:?}

What it means

Logged/produced in AssetSourceBuilders watcher construction: creating the FileWatcher for the given directory path failed (notify crate error). Hot-reloading for that asset source is unavailable; the error reports the path and underlying cause `e`.

Source

Thrown at crates/bevy_asset/src/io/source.rs:561

    ) -> impl FnMut(async_channel::Sender<AssetSourceEvent>) -> Option<Box<dyn AssetWatcher>> + Send + Sync
    {
        move |sender: async_channel::Sender<AssetSourceEvent>| {
            #[cfg(all(
                feature = "file_watcher",
                not(target_arch = "wasm32"),
                not(target_os = "android")
            ))]
            {
                let path = super::file::get_base_path().join(path.clone());
                if path.exists() {
                    Some(Box::new(
                        super::file::FileWatcher::new(
                            path.clone(),
                            sender,
                            file_debounce_wait_time,
                        )
                        .unwrap_or_else(|e| {
                            panic!("Failed to create file watcher from path {path:?}, {e:?}")
                        }),
                    ))
                } else {
                    warn!("Skip creating file watcher because path {path:?} does not exist.");
                    None
                }
            }
            #[cfg(any(
                not(feature = "file_watcher"),
                target_arch = "wasm32",
                target_os = "android"
            ))]
            return None;
        }
    }

    /// This will cause processed [`AssetReader`](crate::io::AssetReader) futures (such as [`AssetReader::read`](crate::io::AssetReader::read)) to wait until
    /// the [`AssetProcessor`](crate::AssetProcessor) has finished processing the requested asset.

View on GitHub (pinned to 396ca72708)

Solutions

1. Check the watcher error kind: path may be missing, permissions insufficient, or inotify/fs event limits exhausted (Linux)
2. Ensure the asset source directory exists and is watchable
3. Run without hot-reloading (disable the file_watcher feature) if watching is not required

When it happens

Trigger: Thrown at crates/bevy_asset/src/io/source.rs:561 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of bevyengine/bevy@396ca72708 (2026-08-20). Data as JSON: /api/errors/bb03231bb1994155. Report an issue: GitHub.