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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
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.