Search Issue Tracker
Active
Under Consideration for 1.21.X, 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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
- [Linux] "Error while reading movie" errors are thrown when opening templates
- Standalone Profiler process is hidden in macOS dock
Add comment