Fix Crash Analysis Issues

This page provides resolution to common problems that can occur during ACR analysis and symbolication processes in Vega Studio. If you don't find a solution to your specific problem here, post an issue in Developer Forum for additional support.

ACR analysis fails due to device connectivity problems

Cause: Device is not properly connected or communication is interrupted during crash report collection.

Solution:

1. Check if your device is properly connected through USB or network.

2. Verify device appears in device list:

   vega devices list
   

3. Try reconnecting the device or restarting VS Code.
4. Ensure device has sufficient battery or is connected to power.

Symbolication produces incorrect or incomplete results

Cause: Wrong symbolication method selected for the type of code being analyzed, or mixed native/JavaScript code requires different approaches.

Solution:

1. If automatic symbolication fails, try manual symbolication.
2. For mixed code, verify you selected the correct decode type:
   • Use gdb for native code symbolication
   • Use js for JavaScript code symbolication
3. Check that you're using the correct symbolication profile for your app type.

Symbolication process completes but results are missing or partial

Cause: Missing debug symbols, outdated source maps, or incompatible Vega Studio extension version.

Solution:

1. Add additional debug symbol folders or source maps as needed:
   • Navigate to Vega Studio > ACR Analysis > Symbol Paths
   • Add paths to debug symbol directories
   • Verify paths are accessible and contain valid symbol files
2. Check if you're using the latest version of Vega Studio extension:
   • Go to VS Code Extensions
   • Update Vega Studio extension if newer version available
   • Restart VS Code after updating
3. Verify debug build configuration:
   • Ensure app was built with debug symbols enabled
   • Check that debug information wasn't stripped during build

Missing debug symbols or source maps prevent symbolication

Cause: Debug symbols or source maps are missing, incorrectly located, or outdated relative to the crash report.

Solution:

1. For native code:
   • Confirm you have the correct debug rootfs or symbol folders
   • Verify symbol files match the exact build that crashed
   • Check that debug symbols weren't stripped during compilation
2. For JavaScript:
   • Verify your source maps are up-to-date and in the correct location
   • Ensure source map file naming matches bundle files (e.g., index.bundle.map)
   • Check that source maps were generated during the build process
3. Regenerate symbols if needed:
   • Rebuild your app with debug symbols enabled
   • Ensure source maps are generated and accessible
   • Verify file paths in source maps are correct

ACR symbolication process is very slow or appears to hang

Cause: Large ACR files, complex projects with many symbols, or system resource constraints.

Solution:

1. For large ACR files:
   • Large ACR files or complex projects might take longer to symbolicate
   • Allow additional time for processing
   • Monitor system resources during symbolication
2. Free up system resources:
   • Close unnecessary VS Code extensions
   • Close other resource-intensive applications
   • Ensure sufficient RAM and disk space available
3. Restart VS Code if needed:
   • If symbolication appears stuck, restart VS Code
   • Try symbolication again with fewer concurrent operations

JavaScript source map files aren't being used during symbolication

Cause: Source map file naming issues, incorrect file locations, or source map format problems.

Solution:

1. Verify source map file naming:
   • Ensure source map file is named correctly (e.g., index.bundle.map)
   • Check that source map filename matches the bundle file name
   • Verify file extensions are correct
2. Check source map location:
   • Verify the source map is in the correct project folder
   • Ensure source map is in the same directory as the bundle file
   • Check that file paths are accessible to Vega Studio
3. Validate source map format:
   • Ensure source map was generated correctly during build
   • Verify source map contains valid mapping information
   • Test source map with other debugging tools to confirm validity

ACR file can't be loaded or parsed

Cause: Corrupted ACR file, unsupported ACR format, or file access permissions.

Solution:

1. Verify ACR file integrity:
   • Check that ACR file is not corrupted
   • Try opening ACR file with a text editor to verify content
   • Ensure file was completely downloaded/transferred
2. Check file permissions:
   • Verify you have read permissions for the ACR file
   • Ensure file is not locked by another process
   • Try copying ACR file to a different location
3. Validate ACR format:
   • Ensure ACR file is in supported format
   • Check that ACR was generated by compatible Vega SDK version
   • Try with a different ACR file to isolate the issue

Related topics

• Debug App Crash Using Vega Studio

---

Last updated: Sep 30, 2025