Symbol file uploads API reference
Find variables and flags you can use to call the API directly or build custom integrations to upload debugging symbols.
Read time 1 minuteLast updated 7 hours ago
If you want to call the Unity Services API directly or build a custom integration to upload debugging symbols, then use the following information to set the required variables and flags.
Note
You can also upload debugging symbols through CI/CD pipelines.
Environment variables
Environment variables are automatically set by the upload scripts. If you want to build a custom integration, then you must set the following variables before you runusymtoolVariable | Required | Value |
|---|---|---|
| Yes | The |
| Yes | |
| No (auto-set by the script) | Path to Unity's bundled |
Usymtool flags
Use the following flags to customize how theusymtoolFlag | Required | Description |
|---|---|---|
| Yes | Sets the path to the directory or file that contains the debug symbols to upload. |
| No | Sets the path to the IL2CPP-generated C++ output directory, which enables C# line number mapping. |
| No | Sets the root path to the IL2CPP files as compiled into the native binary. If blank, it matches on the full paths from |
| No | Reuploads files even if they already exist in storage. |
| No | Processes only files whose names match a regular expression. |
| No | Skips files whose names match a regular expression. |
| No | Sets the log file path. This path defaults to |