Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
1
Found in
2019.2.0b6
2019.2.0b7
2019.3.0a6
Issue ID
1169942
Regression
Yes
Applying Import Setting changes while in Play Mode throws an AssetDatabase.ForceReserializeAssets exception
How to reproduce:
1. Open user-submitted project (Unity2019Test3)
2. Enter Play Mode
3. Select the 'test' asset in the Project window
4. Change some Import Settings(e.g. Max Size) and click 'Apply'
Expected result: the changes are applied, no errors are thrown
Actual result: "Exception: AssetDatabase.ForceReserializeAssets cannot be used when in play mode" error is thrown
Reproducible with: 2019.2.0b6, 2019.2.0b10, 2019.3.0a6, 2019.3.0a10
Not reproducible with: 2017.4.30f1, 2018.4.4f1, 2019.1.11f1, 2019.2.0b5, 2019.3.0a1, 2019.3.0a5
Notes:
Also reproduced with .fbx asset
Comments (1)
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
joshcamas
Aug 20, 2019 04:38
For now, while we're waiting for the fix in 2019.2, manually reimporting the asset in question after this error is thrown works :)