Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0b2
2019.3.1f1
2020.1.0a2
Issue ID
1217256
Regression
Yes
"Unrecognized block header in profiler data file, stopping deserialization" error after deploying on Android while profiling
Steps to reproduce:
1. Open attached "tdd-asteroids.zip" Unity project
2. Build and run on Android with Autoconnect Profiler enabled
3. Build and run again
Actual Results: "Unrecognized block header in profiler data file, stopping deserialization" error is thrown in the console
Expected Results: No errors are thrown
Reproduced on: 2019.3.0b2, 2019.3.1f1, 2020.1.0a2, 2020.1.0a22
Didn't reproduce on: 2017.4.36f1, 2018.4.17f1, 2019.2.20f1, 2019.3.0b1, 2020.1.0a1
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Unlogical-Game-Studios
Feb 24, 2022 15:13
Got this error massage in Unity 2021.2.12f1 while profiling a Mac OS X build(intel).