API calls error handling

Most methods on NablaClient and NablaMessagingClient can return an error: by throwing it, or via their AnyPublisher return type. This error will always be of type NablaError.

There are 2 types of exceptions you might want to handle specifically:

• NablaError.Network: for a network related error. You probably want to provide the patient with a retry mechanism when this error happens
• NablaError.Authentication: when a call to NablaClient.setCurrentUser(userId:) is missing before calling an authenticated API or when the SessionTokenProvider failed to get fresh tokens

See all cases in the Errors folder

Handling by UI components

If any error occurs, the Nabla UI component will handle it in one of the following ways.

• If error is global, e.g. we failed to fetch the list of conversation. Component will then show a text message with a retry button.
• If error is not global, e.g. we failed to load a second page of messages. Component will then show an alert explaining what failed.

Logging

In all cases, errors will also be logged. If you need more control on what's logged and want to enable INFO logs, you can do it during the SDK initialization:

NablaClient.initialize(
  configuration: .init(
    apiKey: "YOUR_API_KEY",
    logger: ConsoleLogger(level: .info)
  ),
  // ...
)

Nabla SDK debugging

By default, the SDK will communicate anonymized events with Nabla servers to help us improve features like video calls.
If you want to disable this reporting, you can do so during the SDK initialization:

NablaClient.initialize(
    configuration: .init(
        apiKey: "YOUR_API_KEY",
        enableReporting: false,
        logger: ConsoleLogger(level: .info)
    )
    // ...
)