KoolbaseException class abstract

The root of every error the SDK raises.

Each subsystem has its own family beneath this — data, storage, auth — so an application can catch narrowly where it wants to and broadly where it does not:

try {
  await Koolbase.storage.upload(...);
} on KoolbaseUnauthenticatedException {
  await goToLogin();          // any surface, one handler
} on KoolbaseStorageException catch (e) {
  showError(e.message);       // storage-specific
} on KoolbaseException catch (e) {
  report(e);                  // anything else from the SDK
}

The families used to be unrelated roots, which meant a failure that belongs to no single subsystem — a rejected session, discovered by whichever call happened to make it — had to be redefined in each one, and applications wrote the same handler several times.