Ditto
All errors that are thrown by the Ditto SDK are wrapped as a DittoError. This type wraps multiple different types of error that each have an associated reason.
You can access more specific information about an error by switching over the error's reason value. A human-readable version of the error is available via the localizedMessage property of the error's reason.
Types
The possible underlying reasons an ActivationError occurs.
The possible underlying reasons an AuthenticationError error occurs.
The possible underlying reasons a BusError error occurs.
Represents a fatal error that the Ditto instance cannot recover from. Should your app encounter one, the instance should be closed and a new instance created.
An error occurred accessing the filesystem.
Errors related to internal ditto core native communication.
The possible underlying reasons an InternalError occurs.
Errors related to IO devices.
The possible underlying reasons an IoError occurs.
Outstanding usage of ditto's working directory detected when trying to instantiate a new Ditto, which would have led to concurrent usage of the backing database files.
Errors transforming Ditto mesh presence data to or from JSON encoding.
The possible underlying reasons a PresenceError occurs.
The possible underlying reasons a StoreError occurs.
The possible underlying reasons a TransportError error occurs.
Some not-yet-categorized error occurred.
Operation is not supported.
Errors interacting with DittoSmallPeerInfo.
Functions
A String representation of the error suitable for display.
Properties
A formatted description of the error. Not all errors have a message. Use the null-safe getLocalizedMessage if you don't want to have to handle null values.