Search Issue Tracker
By Design
Votes
0
Found in
2022.3.18f1
2023.2.7f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-62206
Regression
Yes
[Android] Create symbols.zip generates a Debugging symbols file when it's set to Public and CrashReportingSettings are enabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to Android Platform
4. Open UnityConnectSettings.asset file (ReproProj/ProjectSettings/UnityConnectSettings.asset)
5. Under CrashReportingSettings, change the m_Enabled field to 1 and save the file
6. Open the Build Settings (File > Build Settings)
7. Set Create symbols.zip to Public
8. Build
9. Set Create symbols.zip to Debugging
10. Repeat step 8
11. Compare sizes of both symbols.zip files
Expected result: Build with Create symbols.zip set to Public has a much smaller symbols.zip file
Actual result: Size is the same
Reproducible with: 2022.1.0a13, 2022.3.18f1, 2023.2.7f1
Not reproducible with: 2021.3.34f1, 2022.1.0a12, 2023.3.0b4
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug.
This is by design and has been working like this since Cloud Diagnostics was released. Cloud Diagnostics requires the Debugging Symbols to be able to symbolicate the crash report stack traces with Line Numbers and Method Names, the public symbols only contain public function names, as such if Cloud Diagnostics is enable but only public symbols are generated it won't fulfill its responsibility.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.