Errors

A method that asks Graine on the customer's behalf — memory, scheduled calls, device registration — fails with one error type carrying a code. Branch on the code; show the message, which is written for the customer.

The error type

class GraineError extends Error {
  readonly code: GraineErrorCode;           // the codes below, or a newer one as its word
  readonly status: number;                  // the HTTP status, 0 when nothing answered
  readonly retryAfterSeconds: number | null;
}
 
try { await client.forgetMemory(); }
catch (e) { if (e instanceof GraineError && e.code === "device_limit") showSignedInElsewhere(); }

Every code

The scheduling codes scheduling_off, too_soon, too_far, outside_window and too_many_pending come with a message written for the customer — show it as it is. scheduling_off, too_soon and too_far are usually refused on the device, before any request: those carry no HTTP status (status 0). A newer code reaches an older SDK as unknown, carrying its word — .unknown(raw) in Swift, Unknown(raw) on Android and in Kotlin Multiplatform, the word itself in TypeScript and on the website, and codeName beside unknown in Dart.

When the bar cannot start

The bar's voice and chat report setup problems through onError (and, in React Native, the launcher's error), not as a coded exception:

Other ways trouble is reported

The structures behind these: Types → GraineError.