Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a4
2019.3.0f6
Issue ID
1225161
Regression
Yes
Asmdef Inspector incorrect behaviour
Reproduction steps:
1. Open attached project "TexTileTest.CopyDXT.2019.3.zip"
2. Click on the Scripts/DXT/DXTTools.asmdef in the project so it shows in the Inspector
3. Make a change e.g.Tick the "Stadia" box to include that platform
4. Click on a different file in the project
5. Now you Will see the pop-up dialog, press Apply
6. Switch back to DXTools.asmdef
Expected result: Pressing Apply would apply the changes.
Actual result: Pressing Apply will set the Inspector to your new file, but not Apply the changes to the asmdef, the file is not changed, and when you click back to the asmdef the change(s) are lost.
Reproduces on: 2019.3.0b1, 2019.3.0a4, 2019.3.6f1, 2020.1.0a18
Regression introduced: 2019.3.0a4
Fixed in: 2020.1.0a19
Does not reproduce on: 2019.3.0a3, 2020.1.0a19, 2020.1.0b2, 2020.2.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
Add comment