Search Issue Tracker
Won't Fix
Won't Fix in 2.1.X
Votes
0
Found in [Package]
1.21.20
2.1.0
Issue ID
ADDR-3674
Regression
No
Debug.Log messages fail to appear in the editor console when specific methods are invoked from a custom editor script
Reproduction steps:
1. Open the attached project “ReproProject”
2. From the menu, select "ReproduceIssue > ReproduceWithBuildPlayerContent"
3. Observe the Console for Debug.Log messages
4. Select "ReproduceIssue > ReproduceWithRequestScriptCompilation”
5. Repeat step 3
Expected result: The messages "Before calling AddressableAssetSettings.BuildPlayerContent" and "After calling AddressableAssetSettings.BuildPlayerContent" are displayed
Actual result: Either the message "After calling AddressableAssetSettings.BuildPlayerContent" or no message is displayed.
Reproducible with: 1.19.19, 1.21.20 (2021.3.37f1), 1.21.20 (2022.3.26f1, 2023.2.19f1), 2.1.0 (2023.2.19f1, 6000.0.0b16), 2.0.8 (6000.0.0b16)
Reproduced on: Windows 11 23H2 (22631.3007), Windows 11 (10.0.22631) 64bit (user’s)
Not reproduced on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The logs are cleared as per design. So we have decided to close the case.
Resolution Note (2.1.X):
The logs are cleared as per design. So we have decided to close the case.