Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4.15f1
2020.1.4f1
2020.2.0a21
2020.2.2f1
2021.1
2021.2
Issue ID
1309567
Regression
Yes
Changes to Assembly Definition Asset are not saved after pressing the Apply button in the Unapplied import settings pop-up
How to reproduce:
1. Open the user's attached project
2. In the Project window select Scripts > NewAssembly
3. In the Inspector check the "Allow 'unsafe' Code" checkbox
4. In the Project window select NewBehaviourScript
5. In the Unapplied import settings pop-up select "Apply"
6. Reselect the NewAssembly and observe the Inspector
Expected result: The "Allow 'unsafe' Code" checkbox is checked
Actual result: The "Allow 'unsafe' Code" checkbox is not checked
Reproducible with: 2019.4.15f1, 2019.4.21f1, 2020.1.4f1, 2020.1.17f1, 2020.2.0a21, 2020.2.6f1, 2021.1.0b8, 2021.2.0a7
Not reproducible with: 2018.4.32f1, 2019.4.14f1, 2020.2.0a20, 2020.1.3f1
Notes:
- The issue is reproducible on Mac
- The issue is not reproducible on Windows
- This affects all Assembly Definition settings
- The issue doesn't reproduce when pressing the Apply button in the Inspector
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
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
- Crash on VFXMemorySerializer::StoreObjects when converting to Subgraph Block
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a13