Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
931368
Regression
No
Previously referenced scriptable object in a prefab gets corrupted after building prefab's asset bundle
Steps to reproduce:
1. Open attached project "UnityBug.zip"
2. Right click in the Project View and create two new scriptable objects("Some Scriptable Object")
3. Select "some_prefab" in "Assets/Prefabs/" and reference the first scriptable object to the prefab's script component
4. Open "AssetBundle Browser" window
5. Build "some_prefab" asset bundle
6. Select "some_prefab" in "Assets/Prefabs/" and reference the second scriptable object to the prefab's script component
7. Build "some_prefab" asset bundle
8. Select the first scriptable object and take a look at Inspector window
Actual result: the first scriptable object got corrupted
Reproducible with: 5.6.2p4, 2017.1.0f3, 2017.2.0b3, 2017.3.a1
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
- [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”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment