Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2019.2
2019.3
2019.3.0f4
2020.1
Issue ID
1210886
Regression
No
Prefab file contents do not update when it is renamed
Instead of being updated on file rename, serialized contents of a Prefab only update when it is reserialized after an edit or other cause
How to reproduce:
1. Open or create a new project
2. From Hierarchy drag "Main Camera" onto Project window to create a new Prefab
3. In Project window rename the Prefab
3b. Select the menu item "File > Save project" (needed for pending changes to be saved to disk)
4. Open the renamed file in text editor
5. Search for `m_Name` property and inspect its value
Expected result: `m_Name` property in renamed Prefab matches its new name
Actual result: `m_Name` property contains old "Main Camera" value
Reproducible with: 2018.4.16f1, 2019.2.19f1, 2019.3.0f6, 2020.1.0a21
Not reproducible with: 2017.4.36f1 - Prefab file contents update after File->Save project is selected
Note, if not using "File > Save project" lots of Assets types will not have their name in the file updated. For example Materials. However, for Prefabs even doing this still doesn't update the name in the file, which is a Prefab specific bug. Added 3b to repro steps to clarify scope of bug.
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
- Asset corruption when using the Accelerator cache server
- [Linux] Mouse position is incorrect when playing build on a multiple monitor setup in full screen mode
- PlayerSettings.asset displays incorrect appleEnableAutomaticSigning value
- [Linux] Silent crash on TLSAllocator<(AllocatorMode)0>::ThreadInitialize(unsigned long, char const*) when restarting after setting Graphics API to Vulkan
- AssetBundle allocates more memory when loading it a second time
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a12
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.5f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.7f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.32f1