Console

Settings

Sign out

Notifications

Alexa

Amazon Appstore

Ring

AWS

Documentation

Support

My Cases

Console

Vega Developer Docs

Home

Get Started

Design and Develop

Publish

Reference

Support

Detect Where the App Crash Originates

Open Beta Documentation Amazon offers this technical documentation as part of a pre-release, open beta. The features described might change as Amazon receives feedback and iterates on the features. For the most current feature information, see the latest Release Notes.

This document helps you determine whether a crash in your app originates from your code or Amazon's code. Knowing the crash source is key to efficient debugging and deciding when to contact Amazon support.

Note: This technique might help identify the origin of a crash but can't guarantee the source with certainty.

Prerequisites

Before you start:

Read Symbolicate App Crash Reports to learn how to symbolicate aggregated crash report (ACR) files.
Read Debug Crashes with ACR Summary to understand how to read stack traces and stack frames.

Important: For crash traces on release builds, you may observe JS stack traces that contain the @amzn/ string in the path instead of @amazon-devices/.

Identify the crash source

Follow these steps to identify the crash source.

Step 1: Symbolicate the crash report

Run the ACR file through Vega Studio to generate a symbolicated summary. See Symbolicate App Crash Reports for instructions.

Step 2: Determine your app type

Identify whether your app is JavaScript-only or a mix of JavaScript and native code. Then check the CRASH_LANG field in the ACR summary metadata to confirm the crash language.

Step 3: Find the stack trace in your ACR summary

Open the symbolicated stacktraces section in the ACR summary. The symbolicator prioritizes JavaScript traces when they exist in the ACR file.

Step 4: Match the trace to identify the source

Use the following patterns to determine whether the crash originates from your code or Amazon's code.

For JavaScript stack traces:

Your code — Points to your app source files. Doesn't include @amazon-devices.

/Users/developer_name/workspace/kepler/testapp/VegaProjectApp/src/App.tsx:47:crash

Amazon code — Includes @amazon-devices in the path.

node_modules/@amazon-devices/react-native-kepler/Libraries/...

For native stack traces:

Your code — Contains your workspace directory and shows your symbol path.

#0  0xa1a701bc in VegaProjectTMTurboModule::VegaProjectTM::voidFunc (this=0xa1d99838) at /Users/developer_name/workspace/vega/testapp/VegaProjectTM/kepler/turbo-modules/VegaProjectTM.cpp:33

Amazon or OS code — Doesn't have a workspace directory reference. Shows system paths or ??.
```
#0 0xb6e01b26 in ?? () from /private/var/folders/_p/.../lib/libc.so.6
```

Step 5: Take action based on crash source

If the crash originates from your code, use the ACR summary to review the full stack trace, system info, and metadata. Then locate and fix the issue in your source code.

If the crash points to Amazon code and you see any of the following, contact Amazon support:

Native stack traces in a JavaScript-only app
Stack traces that don't reference your code
The topmost frame in a JavaScript stack trace doesn't point to your app code
LMK crashes occur repeatedly with no stack trace to analyze

When contacting support, share the original ACR file from your device, not the summary report.

Last updated: Feb 18, 2026