Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.1.0a1
2019.1.0a2
2019.1.1f1
2019.3.0a1
Issue ID
1153558
Regression
Yes
Selected Asmdef reference gets stuck on the first selection when Asmdef has some references saved before
How to reproduce:
1. Open the attached project ("case_1153558-WrongAsmdef.zip")
2. Inspect the "NewAssembly" assembly definition in the Assets folder
3. Add an assembly definition reference by clicking the "+" button
4. Select any assembly definition from the list by clicking on it or by using the arrow keys
5. Notice how the selected reference is actually reflected in the inspector
6. Click Enter and edit the same assembly definition reference again
7. Notice that only the first selected assembly definition is saved as selected
Expected results: Selected assembly definition reference changes based on what is actually selected
Actual results: Selected assembly definition reference gets stuck on the first selection
Reproducible with: 2019.1.0a2, 2019.1.3f1, 2019.2.0b2, 2019.3.0a2
Not reproducible with: 2017.4.27f1, 2018.4.0f1, 2019.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
Add comment