Search Issue Tracker
Fixed
Fixed in 1.0.0
Votes
0
Found in [Package]
0.50.0
0.51.0
0.51.1
Issue ID
ULOG-1
Regression
No
Unity logging package fails to build with burst and High managed stripping level.
How to reproduce:
1. Open the attached project “NetcodeBurst.zip“
2. Open the Build Settings (Edit > Build Settings…)
3. Open the Player settings and set the “Scripting Backend” to IL2CPP
4. Build
Expected result: The player is built successfully
Actual result: The build fails with “Burst error BC1010: Loading the field _stringLength from the managed object System.String is not supported”
Reproducible with: 1.8.2, 1.8.4 (2022.2.2f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8)
Couldn’t test with: 1.8.1 and lower (2020.3.46f1, 2021.3.24f1, 2022.2.1f1) - due to errors in the Console window
Reproduced on: macOS Monterey 12.6
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.0.0):
Issue fixed; these compilation errors shouldn't come up due to the Logging package regardless of whatever managed code stripping level the user had set.