There was a timeout when attempting to connect to the Signiant app.
Root causes could include:
The Signiant app connection was not initialized for an operation that requires the app.
App initialization should be done automatically when a download is generated.
Error thrown when the app may not be installed. This happens the first time the SDK is used but can be overwritten with the force flag when generating a transfer.
Error while trying to decrypt message received.
Error while trying to encrypt message to publish.
Unknown problem while launching the Signiant App.
The user does not have permission to download one or more of the specified files.
The user cancels the file selection cancelled
There was an error in the file selection
A folder was not selected by a user.
A user should be prompted for a destination folder automatically when a transfer is created.
The User canceled folder selection on download.
There was an unknown error during folder selection.
The input does not conform to the expected logger format.
Null loggers are not allowed, If you wish to disable all logging consider turning the log level of the default logger to OFF.
There was no recognized provided in the relevant messaging config.
The user is not a member of the portal.
Used when request timeouts
State transition is not valid.
Examples of this error include but are not limited to:
Error code when attempting to start a transfer without the Transfer Config
Error code when attempting to start a transfer without the destination
An event dispatched by the Signiant app was unknown.
This might represent a mismatch between the SDK version and the Signiant app version.
Operation not supported.
Currently only download operations are supported.
Error code when trying to start an upload without selected files
The user does not have any member permissions on the portal.
Websocket connection timed out after fixed interval.
An unknown error occurred while initializing the websocket.
Generated using TypeDoc
This enum represents the various caller facing errors the application may throw. Implementations may optionally catch CodedError objects and define control behaviour on the basis of a specific error.