Search Issue Tracker
By Design
Votes
14
Found in
2017.4.0f1
2018.3.0a1
2018.3.11f1
2019.1.0a1
2019.2.0a2
2019.3.0a1
Issue ID
1143071
Regression
No
Assetbundle is not loaded correctly when they reference a script in custom DLL which contains [System.Serializable] in the build
Steps to reproduce:
1. Open "Fogbuzz issue 1143071" from Own Cloud link
2. Navigate to the buildWithoutDLL folder and open "Beweegvloer" build
-- Notice that ps.Paths[0].Tiles == null
Expected results: DLL files with Serializable class are red in when the project is built
Actual results: DLL files with Serializable class are not red when the project is built
Reproducible with: 2017.4.29f1, 2018.4.2f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a5
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (2020.2.X):
Unfortunately we currently do not support serializable objects (also ScriptableObjects, MonoBehaviours, etc.) from assemblies loaded using Assembly.Load.
It is on our to-do list for the future, though!