Search Issue Tracker
Fixed in 2022.3.9f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a1, future release
Votes
15
Found in
2021.3.27f1
2022.1.0b1
2022.3.1f1
2023.1.0b19
2023.2.0a18
2023.3.0a1
Issue ID
UUM-37939
Regression
Yes
UWP ARM64 build fails when Script Debugging is enabled
How to reproduce:
1. Open the attached project "project2022.zip"
2. Build the project for UWP with Development Build and Script Debugging enabled
3. Open the built Solution
4. Build Solution with Release ARM64 settings
Expected results: Build is successful
Actual results: Build fails with multiple syntax errors
NOTE: This is being caused by an issue in the IL2CPP copy of the Mono code and has been fixed in the IL2CPP repo in this PR:
[https://github.cds.internal.unity3d.com/unity/il2cpp/pull/5346]
It just needs merging in all the Unity branches affected.
Reproducible with: 2022.1.0b1, 2022.3.1f1, 2023.1.0b19, 2023.2.0a18
Not reproducible with: 2021.3.27f1, 2022.1.0a16
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
Add comment