Search Issue Tracker
Fixed in 2021.3.24f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Add comment