Fix Debugging Issues - Amazon Vega Docs

This page helps you resolve common issues that occur when debugging Vega apps with Vega Studio. If you don’t find a solution to your specific problem here, post an issue in the Developer Forum for additional support.

The app terminates unexpectedly while debugging, interrupting the debugging session

Cause: The Lifecycle Manager (LCM) terminates apps that don’t send heartbeat signals. Breakpoints pause your app, preventing heartbeats, causing termination. Solution: Verify your device supports timeout disabling.

From the device’s shell, run:
vlcm --help
Look for the --disable-app-timeout flag in the debug command output.
Prevent app termination using one of these options: Option 1: Using Vega Studio (Recommended) a. Open your launch.json file. b. Add or modify the disableAppTimeout setting to true:
{ "name": "(script) Launch", "type": "vega", "request": "launch", "disableAppTimeout": true }
c. Save and restart your debugging session. Option 2: Using Vega CLI a. Disable timeouts for your component:
vlcm debug <component-id> --disable-app-timeout
b. Launch your app:
vega device launch-app --appName <component-id>
c. Attach your debugger in Vega Studio.
Re-enable timeouts after debugging using one of these options:
- Vega Studio: Launch app normally (without debug configuration)
- Vega CLI: Run then relaunch app
For information about launching your app, see Run Your App.

Example template for launching and debugging Vega and Turbo Module apps:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(script) Launch",
            "type": "vega",
            "request": "launch",
            "vegaMode": "debug",
            "cwd": "${workspaceFolder}",
            "deviceId": "${command:vega.state.getSelectedDeviceId}",
            "disableAppTimeout": true,
            "perf": {
                "startActivityMonitoring": false
            }
        },
        {
            "name": "(native) Launch",
            "type": "vegaNative",
            "request": "launch",
            "cwd": "${workspaceFolder}",
            "deviceId": "${command:vega.state.getSelectedDeviceId}",
            "disableAppTimeout": true
        }
    ]
}

GDB Native Debugging Error: liblzma.5.dylib Not Found

Error:

{Starting: "/usr/local/bin/gdb" --interpreter=mi
dyld[57162]: Library not loaded: /usr/local/homebrew/opt/xz/lib/liblzma.5.dylibReferenced from: <5BAC9301-8CA6-3EA3-9537-CD0E961C0FAB> /usr/local/bin/gdbReason: tried: '/usr/local/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/usr/local/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file)"/usr/local/bin/gdb" exited with code 134 (0x86).ERROR: Unable to start debugging. Unable to establish a connection to GDB. }

Cause: GDB can’t find the required XZ compression library (liblzma.5.dylib) which is a dependency for native debugging. Solution: Install or reinstall the XZ library:

Install the XZ library:
brew install xz
If already installed, try reinstalling:
brew reinstall xz
Verify symbolic links:
brew link xz
If the problem persists, try these additional steps:
Clear Homebrew cache:
brew cleanup
Update Homebrew:
brew update && brew upgrade

Additional considerations

Latest version of Homebrew is installed.
Some macOS versions might require additional security configurations for GDB.
Necessary permissions to access the library locations.

​The app terminates unexpectedly while debugging, interrupting the debugging session

​GDB Native Debugging Error: liblzma.5.dylib Not Found

​Related topics

The app terminates unexpectedly while debugging, interrupting the debugging session

GDB Native Debugging Error: liblzma.5.dylib Not Found

Related topics