Skip to main content
All errors thrown by the Encore SDK are subclasses of EncoreError, organized into four categories by cause.

Hierarchy

Error Categories

Integration — SDK misuse

Errors caused by incorrect SDK setup. These are preventable by following the integration guide.

Protocol — response failures

Errors from the API layer — HTTP failures, malformed responses, or API-level errors.

Transport — infrastructure failures

Errors from the network or persistence layer.

Domain — business rule violations

Usage

In production, catch EncoreError broadly and log it. Only catch specific subtypes when you need to handle them differently (e.g. showing a “no internet” message for Transport.Network).