Search Issue Tracker
Fixed
Fixed in 2021.3.24f1, 2022.2.17f1, 2023.1.0b13, 2023.2.0a11
Votes
0
Found in
2020.3.42f1
2021.3.15f1
2022.1.24f1
2022.2.1f1
2023.1.0a23
2023.2.0a1
Issue ID
UUM-21944
Regression
No
"ProjectSettings.asset" changes to an unparsable YAML file when using Scripting Define Symbols
Steps to reproduce:
1. Unzip the “Parse” folder and observe the ProjectSettings.asset file in Parse/ProjectSettings folder where the scriptingDefineSymbols is
2. Open the “Parse” project in a version that has any of Andriod/iOS/tvOS platforms
3. Observe ProjectSettings.asset file where the scriptingDefineSymbols is
Expected result: The file doesn’t change or changes without opening the project only in Andriod/iOS/tvOS platforms
Actual result: The file changes to an unparsable file
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a23
Reproduced on: macOS Monterey 12.2 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment