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
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 PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
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).