The Veem Web SDK provides granular error data in order to allow you to better ascertain the criticality of errors thrown within the SDK, as well as when to reset the SDK due to an unrecoverable error.
Errors can be captured through registering a
onError callback function on the selected component. A list of wider properties that can be registered on these components can be found here.
onError callback will be called with an errors object that will contain a
priority value. This priority will help indicate the criticality of the error thrown, as well if any action is needed on your part to reset or abort the SDK, as well as possibly resolving the issue.
priority=0 (SDK initialization error): Fatal errors pertaining to the SDK configuration, or instantiation of the SDK. SDK has found itself in a non-recoverable state and should be restarted. Most commonly, these errors indicate a malformed SDK configuration.
priority=1 (SDK execution error): Fatal errors pertaining to the SDK application. Application has found itself in a non-recoverable state and should be restarted. This would require a resolution by Veem's internal team.
priority=2 (SDK application error handling) Non-fatal errors handled by the SDK application itself. Examples of these errors can be network errors. No action is needed and can be ignored.
Updated 7 months ago