Logging and error handling
The logging and error handling features of the Unblu Android mobile SDK help you deal with errors and unexpected behavior that may arise when using the SDK in your app.
The Unblu SDK uses a configurable internal logger.
The default value of the log level is
VERBOSE. In release builds, however, the
DEBUG logs are removed with ProGuard rules.
You can change the log level by means of the
By default, the logger doesn’t print any security-relevant information or additional details. To change this behavior for debugging purposes, set
To get logs about mobile co-browsing performance, set
true. For this the log level has to be
DEBUG or less and also the
enableDebugOutput flag has to be enabled.
Errors can occur either during initialization or at runtime. The error types are defined in the package
If an error occurs during initialization, the user can’t use Unblu.
You should either inform user that Unblu is momentarily unavailable or ensure that the Unblu integration isn’t displayed in your app to prevent users from trying to access the Unblu UI.
Most error types are returned on the callback of the method call they’re associated with. For example, if an error occurs when you try to start a mobile co-browsing session by calling
MobileCoBrowsingExceptionCallback contains a
How you should handle runtime errors depends on the specific error type. Most runtime errors aren’t fatal, but the following errors require you to deinitialize and reinitialize the SDK: