Upload debug files for crash analytics
Updated: Oct 19, 2026
If you have debug symbol files for your Meta Quest app, upload them to view symbolicated stack traces in the
Crash Analytics dashboard.
Your project folders contain debug symbol files after you build an APK. These files match the *.so, *.sym.so, or *.dbg.so filename pattern. Crash Analytics uses them to symbolicate stack traces. For example, if your project creates a library named libunity.so, its debug symbol file might be named libunity.so, libunity.sym.so, or libunity.dbg.so.
| Engine | Location of debug symbol files |
|---|
Native | <project-folder>/obj/local/arm64-v8a/
|
Unity | The arm64-v8a folder in the generated <build-folder>\<build-name>-<build-version>-<build-code>.symbols.zip file. Enable Create symbols.zip when you build, then extract the file. |
Unreal | <project-folder>\Binaries\Android\<project-name>_Symbols_v1\<project-name>-arm64
|
Warning:
Do not rename debug symbol files. Crash Analytics matches the library name in your app to a debug symbol file that ends in .so, .sym.so, or .dbg.so. These are the only supported filename extensions for debug symbol files.If you deleted the debug symbol files after building the project, you can rebuild them only if the project has not changed since you uploaded the app to a release channel. Even a small difference can cause a mismatch between the uploaded app binary and the rebuilt debug symbol files. A mismatch can result in missing symbols in stack traces.
Upload debug symbol files for new builds
You can upload debug symbols with a new binary build by using Meta VR Developer Hub or the Oculus Platform Command Line Utility.
In Meta VR Developer Hub, open the App Distribution tab and select Upload next to the target release channel. Select an APK to open the Upload Build menu. In the Debug Symbols field, select the folder that contains your build’s debug symbol files. You can also enter a pattern in the Debug Symbols Pattern field.
Upload debug symbols for new builds with the command-line utility
Use the standard command for uploading an app to a release channel, and add these parameters for the debug symbol path and filename pattern:
--debug_symbols_dir <directory-path> specifies the directory that contains the debug symbol files.--debug-symbols-pattern <filename-pattern> specifies a pattern that matches the debug symbol filenames. Use an asterisk as a wildcard, such as *.sym.so.
Example
ovr-platform-util upload-quest-build --app_id 12345678901234 --token ABCDEF1234567890abcdef1234567890 --apk c:\myproject\app\build\outputs\apk\myApp.apk --channel store --debug_symbols_dir c:\myproject\obj\local\armeabi-v7a\ --debug-symbols-pattern *.sym.so
Upload debug symbol files for an existing build
You can attach debug symbol files to an app build that you previously uploaded to a release channel. This option provides symbolicated crash analytics without requiring users to update to a new app version.
Before uploading the files, find the Build ID of the APK that you want to attach them to.
In the Recently Uploaded Builds list, find the build and select its version number. The Build Details page opens.
On the Details tab, copy the binary’s Build ID.
Unity: Debug symbols for existing builds
- Open the OVR Platform tool in Unity, via Window > Meta > Tools > Oculus Platform Tool.
- Select Upload Debug Symbols.
- If your project uses Mono scripting, replace Symbol Directory Path with the path to the Mono symbols.
- Select Upload Debug Symbols Only.
- Enter the Build ID for the build.
- Select Upload.
Unreal: Debug symbols for existing builds
- Open the Oculus Platform window in Unreal Engine.
- Select Upload Debug Symbols.
- Select Upload Debug Symbols Only.
- Enter the Build ID for the build.
- Select Upload.
Upload debug symbols for existing builds with the command-line utility
ovr-platform-util upload-debug-symbols --parent <build-id> --app_id <app-id> --app_secret <app-secret> --debug_symbols_dir <directory-path> --debug-symbols-pattern <filename-pattern>
--parent <build-id> specifies the build ID of the binary to attach the debug symbol files to.--debug_symbols_dir <directory-path> specifies the directory that contains the debug symbol files.--debug-symbols-pattern <filename-pattern> specifies a pattern that matches the debug symbol filenames. Use an asterisk as a wildcard, such as *.sym.so.
Verify uploaded debug symbols
Uploaded debug symbol files appear on the Expansion Files tab of the app binary’s Build Details page.