Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.0f3
Issue ID
998051
Regression
No
DLL is not imported correctly when a project requiring a Library rebuild is opened
Steps to reproduce:
1. Open QA attached project
2. Navigate to Assets/Commonds/Atesh/WindowsAndWidgets/DLLs/
-- Notice the state of 'Atesh.ComponentModel.dll'. It has no component
3. Right-click the file and click 'Reimport'
-- Notice the component for the DLL appears
This also affects build runtime and Cloud Build as the badly imported DLL would cause failed builds
Reproduced on: 2017.2.2f1, 2017.3.1p2, 2018.1.0b9, 2018.2.0a2
Comments (4)
-
Xtro
Mar 09, 2020 01:07
Still broken in 2019.2.15.
-
Xtro
Mar 09, 2020 01:07
-
Xtro
Mar 08, 2020 19:26
Looks like this is fixed in 2019.2.15. I didn't do much testing yet.
-
Xtro
Aug 05, 2018 16:16
2018.2.2 and still not fixed.
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:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.