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
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
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
- Profiling information icon does not update for Light Mode
- [Linux] Type to select functionality is missing for drop down menus
- TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
- VFX Graph link contrasts fail WCAG guidelines
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 :)