Roku Crash Reporting and Error Tracking

Docs > Error Tracking > Frontend Error Tracking > Mobile Crash Reporting > Roku Crash Reporting and Error Tracking

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Overview

Error Tracking processes errors collected from the Roku SDK.

Enable Roku Crash Reporting and Error Tracking to get comprehensive crash reports and error trends with Real User Monitoring. With this feature, you can access:

Aggregated Roku crash dashboards and attributes
Trend analysis with Roku error tracking

Your crash reports appear in Error Tracking.

Setup

If you have not set up the Roku SDK yet, follow the in-app setup instructions or see the Roku setup documentation.

Add the latest version of the Roku SDK to your ROPM dependencies (or download the zip archive).
Configure your application’s env when initializing the SDK.

For any given error, you can access the file path, line number, and a code snippet for each frame of the related stack trace.

Limitations

Crash reporting on Roku doesn’t yet support stacktraces.

Test your implementation

To verify your Roku Crash Reporting and Error Tracking configuration, you need to trigger a crash in your application and confirm that the error appears in Datadog.

To test your implementation:

Run your application on an Roku device.

Execute some code containing a crash. For example:

sub explodingMethod()
    x = 1
    print x.foo

After the crash happens, restart your application and wait for the Roku SDK to upload the crash report in Error Tracking.

Forward errors to Datadog

Whenever you perform an operation that might throw an exception, you can forward the error to Datadog by adding the following code snippet:

    try
        doSomethingThatMightThrowAnException()
    catch error
        m.global.datadogRumAgent.callfunc("addError", error)
    end try