Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.17f1
6000.0.0b13
Issue ID
UUM-68107
Regression
No
Scripts are not properly serialized in the Player when using Assembly Definitions
How to reproduce:
1. Open the “SerializationError“ project
2. Open the “SampleScene”
3. Switch the Player build to “Development Build” (File > Build Settings)
4. Build And Run
5. Observe the Player
Expected result: No errors are thrown and multiple “Spawner” GameObjects are instantiated
Actual result: The “A scripted object (probably ExampleMonobehaviour?) has a different serialization layout when loading. (Read 32 bytes but expected 48 bytes)” error is thrown and no GameObjects are instantiated
Reproduced with: 2021.3.36f1, 2022.3.22f1, 2023.2.17f1, 6000.0.0b13
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Not reproducible in the Editor
2. All errors logged in the Playe are provided in the internal comments
3. Could not reproduce in a new project
4. Not reproducible when removing the “Assets/TestAssembly/TestAssembly.asmdef” Asset
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.