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.

Aggregated crash report (ACR) analysis fails due to device connectivity problems

Cause: Poor device connection or communication interruptions prevent crash report collection.

Solution:

1. Check that the device has sufficient battery.
2. Connect your device through USB or network.

3. Verify the device connection:

   Copy code Copied to clipboard.

   vega device list
   

4. Reconnect the device or restart VS Code.

Symbolication produces incorrect or incomplete results

Cause: You selected the wrong symbolication method 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 the 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:
   • Verify you enabled debug symbols when building the app
   • Verify the build retained debug information

Missing debug symbols or source maps prevent symbolication

Cause: Debug symbols or source maps are missing, incorrectly located, or outdated.

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 compilation didn't strip debug symbols
2. For JavaScript:
   • Verify your source maps are up-to-date and in the correct location
   • Ensure source map files have names that match bundle files (for example, index.bundle.map)
   • Check that the build process generated source maps
3. Regenerate symbols if needed:
   • Rebuild your app with debug symbols enabled
   • Ensure the build generates source maps that are accessible
   • Verify file paths in source maps are correct

ACR symbolication process is 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 apps
   • Ensure sufficient RAM and disk space available
3. Restart VS Code if needed:
   • If the symbolication appears stuck, restart VS Code
   • Try symbolication again with fewer concurrent operations

Symbolication doesn't use JavaScript source map files

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

Solution:

1. Check the naming of source map files:
   • Use correct naming for the source map file (for example, index.bundle.map)
   • Check that the source map filename matches the bundle file name
   • Verify file extensions are correct
2. Check the 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 the source map format:
   • Ensure the build generated the source map correctly
   • Verify the source map contains valid mapping information
   • Test the source map with other debugging tools to confirm validity

The system can't load or parse the ACR file

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

Solution:

1. Verify ACR file integrity:
   • Check that you haven't corrupted the ACR file
   • Try opening an ACR file with a text editor to verify the content
   • Ensure the file was downloaded or transferred completely
2. Check file permissions:
   • Verify you have read permissions for the ACR file
   • Ensure no other process is locking the file
   • Copy the ACR file to a different location
3. Validate ACR format:
   • Ensure ACR file uses a supported format
   • Check that the ACR was generated by a compatible Vega SDK version
   • Try with a different ACR file to isolate the issue

Related topics

• Debug App Crash Using Vega Studio

---

Last updated: Dec 22, 2025