bevyengine/bevy · error · ReadLogError

Encountered an invalid log line: '{0}'

Error message

Encountered an invalid log line: '{0}'

What it means

ReadLogError::InvalidLogLine: while replaying the ProcessorTransactionLog, a line was encountered that does not match any known entry format (begin/end markers, unrecoverable marker). The offending raw line is carried in the error; the log is likely corrupted or from an incompatible version.

Source

Thrown at crates/bevy_asset/src/processor/log.rs:241

    }

    fn end_processing<'a>(
        &'a mut self,
        asset: &'a AssetPath<'_>,
    ) -> BoxedFuture<'a, Result<(), BevyError>> {
        Box::pin(async move { self.write(&format!("{ENTRY_END}{asset}\n")).await })
    }

    fn unrecoverable(&mut self) -> BoxedFuture<'_, Result<(), BevyError>> {
        Box::pin(async move { self.write(UNRECOVERABLE_ERROR).await })
    }
}

/// An error that occurs when reading from the [`ProcessorTransactionLog`] fails.
#[derive(Error, Debug)]
pub enum ReadLogError {
    /// An invalid log line was encountered, consisting of the contained string.
    #[error("Encountered an invalid log line: '{0}'")]
    InvalidLine(String),
    /// A file-system-based error occurred while reading the log file.
    #[error("Failed to read log file: {0}")]
    Io(#[from] futures_io::Error),
}

/// An error that occurs when writing to the [`ProcessorTransactionLog`] fails.
#[derive(Error, Debug)]
#[error(
    "Failed to write {log_entry:?} to the asset processor log. This is not recoverable. {error}"
)]
pub(crate) struct WriteLogError {
    pub(crate) log_entry: LogEntry,
    pub(crate) error: BevyError,
}

/// An error that occurs when validating the [`ProcessorTransactionLog`] fails.
#[derive(Error, Debug)]

View on GitHub (pinned to 396ca72708)

Solutions

  1. Delete the transaction log so it is recreated from scratch (all assets will be reprocessed)
  2. Ensure the same bevy/processor version wrote and reads the log
  3. Avoid manually editing the processor log files
Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at crates/bevy_asset/src/processor/log.rs:241 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/144b7f61a39a85f4. Report an issue: GitHub.