Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.3
2018.4
2018.4.10f1
2019.2
Issue ID
1189649
Regression
No
Imported Prefab file (in Library folder) is out-of-sync with source Prefab file (.prefab file)
A prefab with an old library representation will display different states in Prefab Edit Mode and in its instances in the Scene
To reproduce:
1) Open the attached project
2) Create an empty object and create three empty child objects on it
3) Add the script in the project to the parent object
4) Make the parent object a prefab
5) Go to a file viewer app (Win Explorer/Finder/Files), and open the .meta file of the prefab in a text editor and note down the guid there
6) Find the same prefab in Library folder through the guid and copy it in a separate location
7) Go back to Editor
8) In the parent object, attach the child objects to the script component in the inspector
9) Save and close the editor
10) Take the files you saved in step 6, and paste them back into the library, causing it to retain the old reference
11) Reopen Unity
12) Check the parent object in scene both in and out of Edit mode
Expected: It should show an identical setup
Actual: The non-edit mode object has no references attached in the inspector. In edit mode, they are still correctly shown.
Reproduced in 2018.3.0b1, 2018.4.11f1, 2019.2.9f1
Not reproduced in 2019.3.0a1, 2020.1.0a8
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (fix version 2020.2):
Fixed with 2020.2.0a7
Postponed pending the fix of issue: 1215729.
Asset team are currently looking into the same issue in Asset DB V2, when that is fixed we will need to re assess what would be involved in backporting this to builds that rely on Asset DB V1 and go from there