Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.3.X
Votes
0
Found in
2017.3.0b2
Issue ID
954642
Regression
No
Assembly Definition Files could not find References in the Editor
Adding the references using the editor, it would not be able to find them and throw the exception
To reproduce:
1. Download attached project "Digimon 3D.zip" and open in Unity
2. Open "Application" scene
3. Open "Digimon 3D" folder and select "Digimon 3D.asmdef" file
4. In Inspector window fill Missing Reference fields with these files:
TheDialgaTeam.Modules.System.asmdef
TheDialgaTeam.Modules.UnityEngine.asmdef
TheDialgaTeam.MVCC.asmdef
5. Click "Apply" button
Expected Result: Files will be applied in References fields
Actual Result: All those selected files will disappear from References fields and Console will be spammed with the exceptions:
AssemblyDefinitionException: Could not find assembly reference 'TheDialgaTeam.Modules.System'
AssemblyDefinitionException: Could not find assembly reference 'TheDialgaTeam.Modules.UnityEngine'
AssemblyDefinitionException: Could not find assembly reference 'TheDialgaTeam.MVCC'
Notes:
- This issue appears on Windows and OSX
- It works fine in Visual Studio
Reproduced on Unity 2017.3.0b1, 2017.3.0b2 and 2017.3.0b3
Could not check for regression on 2017.2, because files becomes corrupted
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment