If you have the debuggable library files (also known as debug symbol files) for your Meta Quest app, you can upload them to see symbolicated stack traces in the Crash Analytics dashboard.

Debug symbol files are saved in your project folders when you build your APK files. They typically match the filename pattern *.so, *.sym.so, or *.dbg.so, and these are the files we use in Crash Analytics to symbolicate stack traces. For example, if the library your project creates is called libunity.so, the symbolicated version of it might have the same name, libunity.so, or it might be named libunity.sym.so or libunity.dbg.so.

If these debug symbol files have been deleted since the last time you built the project, it is sometimes possible to rebuild them, provided that you have changed absolutely nothing in the project since the time you uploaded the app into a release channel. Even a small difference can create a mismatch between an uploaded app binary and the rebuilt debug symbol files, which can result in missing symbols in stack traces.

You can upload debug symbols at the same time as you upload a new binary build using Unity, Unreal, or the Oculus Platform Command Line Utility.

The OVR Platform Tool in Unity is configured to automatically upload debug symbols for your app whenever you upload an APK file to a release channel. The Debug Symbols Directory defaults to the standard symbol path for your project built with IL2CPP scripting backend. If your project is built using the Mono scripting backend, you can select the relevant symbol path. For more information, see Upload App to the Store.

The Oculus Platform Tool in Unreal Engine is configured to automatically upload debug symbols for your app whenever you upload an APK file to a release channel. The Symbol Directory Path defaults to the standard symbol path where UE4 stores symbols for your project. You can clear the path setting if you don’t want to upload symbols, or if your symbols are stored elsewhere, you can specify a new path for where your symbolicated libUE4.so file is located. For more information, see Upload Apps from the Unreal Editor.

The syntax is the same as uploading a new app to a channel by itself, but you also append the following two parameters to specify the debug symbol file path and filename pattern:

--debug_symbols_dir <dirpath> Specifies the path of the directory that contains the debug symbol file or files.

--debug-symbols-pattern <filenamePattern> Specifies a file name pattern that matches the filenames of all the debug symbol files. You may use an asterisk to indicate a wildcard, for example: *.sym.so

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

You can attach debug symbol files to an app build previously uploaded to a release channel. This is useful if this is the first time you’ve had the opportunity to upload debug symbol files for your app but you don’t want to force all your users to update to a new app version just so that you can get symbolicated crash analytics.

You will need the Build ID of the APK to which you want to attach the debug symbol files.

ovr-platform-util upload-debug-symbols --parent <buildId> --app_id <Id> --app_secret <app-secret> --debug_symbols_dir <dirPath> --debug-symbols-patternfilenamePattern

--parent <buildID> Specifies the build ID of the binary to attach the debug symbol files.

--debug_symbols_dir <dirPath> Specifies the path of the directory that contains the debug symbol file or files.

--debug-symbols-pattern <filenamePattern> Specifies a file name pattern that matches the filenames of all the debug symbol files. You may use an asterisk to indicate a wildcard, for example: *.sym.so

Any debug symbol files you upload appear in the Build Details page of your app binary, under the Expansion Files tab.