mosaic-client/dev.catbit.mosaic.client.exceptions

Package-level declarations

Types

class DataNotFoundException(val message: String?) : Throwable

Thrown when a GetData reading resolves to null — a Single access mode reading a key that doesn't exist, or a Batch reading with allowMissingData = false hitting a missing key. Carried as GetData's onFailure incoming data.

DownloadCancelledException

class DownloadCancelledException : Throwable

Thrown when the user cancels a platform-native save dialog (e.g. iOS's FileKit.openFileSaver() document picker) instead of a real transfer/write failure — used by dev.catbit.mosaic.core.data.schemas.event.events.networking.DownloadFileEventSchema's runner to fire onFailure() with no data, matching the convention already used by OpenFilePickerEventRunner for picker cancellation.

EventNotFoundException

class EventNotFoundException(val message: String?) : Throwable

Thrown when an event is looked up by id somewhere in the screen's tile tree and none carries that id — the failure behind TriggerEvent's and UpdateEvents' onFailure, and TilesManager's own updateEventHolder.

GetRequestWithBodyException

class GetRequestWithBodyException(url: String) : Throwable

Thrown by MosaicNetworkImpl when an HTTP GET request would be sent with a non-null body — a real validation Mosaic's own network layer performs that isn't documented anywhere on the DSL side (SendNetworkRequest/GetScreen/RefreshScreen all accept a body regardless of method, and this only surfaces at request time). Any event issuing a GET with a non-null body fails with this as its onFailure cause.

MissingUploadUrlException

class MissingUploadUrlException : Throwable

Thrown by UploadFileEventRunner when dev.catbit.mosaic.core.data.schemas.event.events.networking.UploadFileEventSchema.url is null and NetworkParametersHolder has no staged URL to fall back to either — the case SetIncomingDataToNetworkParamsHolderUrl was supposed to cover but either wasn't chained, or staged a value some other network event already consumed first.

NetworkResponseException

data class NetworkResponseException(val status: HttpStatusCode, val error: String) : Throwable

Wraps a non-2xx HTTP response so it can travel as a Throwable through safeNetworkCall (extensions/ResultExtensions.kt) — carries the real status code and raw body text, which is what lets SendNetworkRequest/UploadFile's onNetworkFailure(code) matching (and GetScreen's equivalent) branch on the exact status.

OverlayAlreadyAddedException

class OverlayAlreadyAddedException(overlayId: String) : Throwable

Thrown when DisplayBottomSheet/DisplayModalBottomSheet/DisplayDialog is called with an id already in use by a currently-showing overlay of the same kind — the failure behind those 3 events' onFailure.

OverlayNotExistsException

class OverlayNotExistsException(overlayId: String) : Throwable

Thrown when DismissBottomSheet/DismissModalBottomSheet/DismissDialog is called with an id that has no currently-showing overlay registered under it — the failure behind those 3 events' onFailure.

TileNotFoundException

class TileNotFoundException(val message: String?) : Throwable

Thrown when a tile is looked up by id and none matches — the failure behind every dev.catbit.mosaic.client.ui.sdui.foundation.tiles.manager.behaviors.TilesEditor method that targets a tile/groupingTileId by id, and TilesEventDispatcher.onEvent/onGroupEvent.