Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0f2
Issue ID
1096938
Regression
No
Adding a Custom Package with a Scriptable Object which has a custom icon, makes the instances have a default icon
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. "Assets" -> "Create" -> "Scriptable Object"
3. Notice a New Scriptable Object is created with a blue circle for its icon
4. Create a New Project and close it
5. Copy "MinimalRepro\Packages\test" to the New Projects Package folder
6. Open the New Project
7. "Assets" -> "Create" -> "Scriptable Object"
Expected Result: The new Scriptable Object has the same blue circle for an icon as in the first project
Actual Result: The new Scriptable Object has the default icon
Reproduced with: 2018.3.1f1
Did not reproduce on: 2019.1.0a13, 2019.1.0a1, 2018.3.0b1, 2018.3.0a1, 2017.4.18f1 (Package folder wasn't implemented yet)
Note:
Doesn't reproduce if using an Assembly Definition to reference the Package
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
- [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
Resolution Note:
Using Assembly Definitions or Unity 2019.1 resolves the issue