Search Issue Tracker
Won't Fix
Votes
25
Found in
2019.2.8f1
Issue ID
1215261
Regression
No
Builds with Steamworks.NET don't show the errors files and lines details in the stacktrace
1. What happened
A build with Steamworks.NET doesn't show the errors files and lines details in the stacktrace.
2. How we can reproduce it using the example you attached
Build and execute the attached project. A script will be spamming a set of Debug.LogError that will have the full details in editor, and lack them in the build.
-
danp
Jan 03, 2021 07:04
I'm getting no line numbers in development build. Building from script locally. StandaloneOSX.
-
davidrochin
Dec 31, 2020 18:31
In my case, something is removing my PDB files from my "Game_Data\Managed" folder. I suspect Steam's Content Builder is the culprit here.
-
davidrochin
Dec 31, 2020 18:24
I'm experiencing this too
-
drHogan
Mar 17, 2020 13:57
We do experience the problem also without using Unity Cloud builds as long as Steamworks.NET is present.
-
alan-lawrance
Mar 15, 2020 20:40
An important part of the repro steps is that it only occurs with Unity Cloud builds.
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
- Crash on memcpy when importing lightmaps after GI bake
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
Resolution Note (2021.2.X):
I am sorry to inform you that the development team will not be fixing this issue. Since Steam strips the .pdbs during upload, there is not much we can do on the Mono side to show line numbers in the stacktrace.