Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.10f1
Issue ID
1078023
Regression
No
Multiple inspector views into an Assembly Definition file cause unexpected changes after each one asks for apply/reject
How to reproduce:
1. Open the user-submitted project
2. In the Project Window select the "A.asmdef" assembly
3. In one inspector, change its name to from "A" to "A2" and click apply
4. Now select the "B.asmdef" assembly.
5. Drag "A2.asmdef" to the missing reference in one inspector and click apply
6. Press somewhere outside the inspectors.
Expected result: the recently made edit is synced between both Inspectors
Actual result: recent edit prompt will show up, If you press Reject, it will keep the changes. If you press Apply, the changes will be undone (the reference will not be missing, just empty like it was never added).
Reproduced in: 2018.3.0a11, 2018.2.7f1, 2018.1.9f2, 2017.4.11f1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.