SeamError
Base class for all Seam errors.
These errors are thrown by Seam classes and interfaces. They are all subclasses of SeamError.
Inheritors
Types
The app user's phone has not been activated. Call SeamSDK.activate first.
The SDK is already initialized. Thrown when trying to call SeamSDK.initialize multiple times. You can call SeamSDK.deactivate first.
There are multiple credential errors. Thrown when trying to unlock with a credential. Check the errors list for more details.
A deactivation is already in progress. Throw when trying to call SeamSDK.deactivate multiple times.
The SDK has not been initialized. Call SeamSDK.initialize first. Usually thrown when trying to call a method that requires the SDK to be initialized, such as SeamSDK.unlock or SeamSDK.activate.
No integration found for the specified credential. Usually thrown when trying to unlock a credential that doesn't have an integration (Assa Abloy, Latch, Salto, etc) associated with it.
The device does not have an internet connection. Usually thrown when trying to call a method that requires an internet connection, such as SeamSDK.unlock, SeamSDK.initialize, SeamSDK.refresh, SeamSDK.activate etc.
The client session token is invalid. Trhown when trying to call SeamSDK.initialize with an invalid client session token.
The credential id is invalid. This error is usually thrown when trying to unlock with a credential that is invalid, or not recognized by the SDK.
The unlock proximity is invalid. Thrown when trying to unlock with an invalid unlock proximity.