Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2019.4.39f1
2020.3.35f1
2021.3.3f1
2022.1.3f1
2022.2.0a15
Issue ID
UUM-1632
Regression
No
Unwanted line reordering in the ProjectSettings.asset file when ticking and unticking any listed options under UWP Settings > Capabilities
Steps to reproduce:
1. Make a copy of the ProjectSettings.asset file located in the ProjectSettings folder of the attached project
2. Open the attached project
3. Under Edit > Project Settings > Player > UWP Settings > Capabilities, tick and untick any of the listed options
4. Close the project
5. Compare the differences between the original and the current ProjectSettings.asset files, using any suitable tool
Expected results: no differences exist between the two files
Actual results: several lines have been moved around in the ProjectSettings.asset file
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.3f1, 2022.1.3f1, 2022.2.0a15
Note: Repeating the process will modify the ProjectSettings.asset file every time
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
This is due to the underlying storage for those settings. Unfortunately the serialization and storage container won't change in a near future nor it's serialization so closing as it won't be touched in the near term.
Resolution Note (2022.2.X):
This is due to the underlying storage for those settings. Unfortunately the serialization and storage container won't change in a near future nor it's serialization so closing as it won't be touched in the near term.