Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a18
2021.2.0b6
2022.1
Issue ID
1356059
Regression
Yes
Prefab instances will not be correctly updated because of an editor error when importing a package
How to reproduce:
1. Open the "1356059" project attached in google drive (link in the edits)
2. Open the "Main Scene" Scene in the Assets folder
3. Observe the Console window
Expected result: There are no error messages
Actual result: The "Your prefab instances will not be correctly updated because of an editor error. The data buffer is smaller than the expected minimum based on the TypeTree." error message is thrown
Reproducible with: 2021.2.0a18, 2021.2.0b6, 2022.1.0a5
Not reproducible with: 2019.4.29f1, 2020.3.15f2, 2021.1.16f1, 2021.2.0a17
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a8
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b13