Search Issue Tracker
Fixed in 2018.3.X
Votes
4
Found in
2018.3.0b6
2018.3.4f1
2019.1.0a1
2019.2.0a1
Issue ID
1126037
Regression
No
Prefab instance management script loses references to the main objects in the scene after building and saving the project
How to reproduce:
1. Open the user-submitted project ("WindowsAndWidgets.zip")
2. In the Project Window's Development" folder open the "Scene" scene
3. Build the Project
4. Go to File -> Save Project
Expected result: The project is saved without any issues
Actual result: The references to the window objects are lost and the console throws the "MissingMethodException: UnityEngine.Object UnityEditor.PrefabUtility.GetCorrespondingObjectFromSource(UnityEngine.Object)" error
Reproduced in: 2019.2.0a6, 2019.1.0b4, 2018.3.7f1, 2018.3.0b6
Couldn't test with: 2017.4.20f1 (Project throws dozens of errors, possibly due to incompatible plugins)
Comments (6)
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 [NSApplication endModalSession:] when saving while Play Mode is loading
- Incorrect Preferred Height calculation when a single text line uses different Font Assets
- [ShaderGraph] Redo Collapse Nodes action does not fully collapse the Nodes
- [Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
- Unrecognized identifier DECLARE_STACK_CB error is thrown when VirtualTexture Property is used with Custom RenderTexture target
Xtro
Mar 08, 2019 21:31
The second bug related to this one is fixed in 2018.3.8.
Xtro
Mar 05, 2019 18:29
Still broken on 2018.3.7
Ospa
Mar 05, 2019 09:08
In what 2018.3 version is this fixed? It still happens with the newest 2018.3.7f1 version just released.
JimJC
Feb 19, 2019 20:04
Should be higher priority.
Xtro
Feb 16, 2019 00:24
The new bug after this one is fixed on 2018.3.6.
https://forum.unity.com/threads/bug-unity-2018-3-6-is-still-broken-even-after-fixing-a-similar-bug.630160/
Xtro
Feb 15, 2019 21:54
It looks like this is fixed in 2018.3.6 but actually it's not. I'll send a new bug report.