Search Issue Tracker
Not Reproducible
Votes
3
Found in [Package]
1.21.18
Issue ID
ADDR-3545
Regression
No
"Build report xxxxx not found" error is seen in the Profiler when Loading AssetBundles
How to reproduce:
1. Open the “IN-57235“ project
2. Open the “Startup“ Scene
3. In the Menu press Window → Analysis → Profiler
4. Enter Play Mode
5. In the Profile window, navigate to the Addressable Assets Module
6. Select anywhere within the module and observe the Profiler Window
Expected result: No errors are seen
Actual result: An error is seen
Reproducible with: 1.21.18 (2022.3.9f1)
Could not test with: 1.21.18 (2021.3.31f1, 2022.3.11f) , 2.0.3 (2023.1.17f1, 2023.2.0b14, 2023.3.0a11) (due to errors)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Error: Build report 59a80a192bf196d23e6200a78f3ae7d6 not found. Build report data is required to display correct frame data.
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
The repro project does not work when entering play mode due to attempting to load remote bundles from a server that appears to be offline. The bug also references a fix to the code but only specifies the line number of a file, which appears to not match the intended change. In AssetBundleProvider.cs, there is a line near the suggested area with the following code:
#if ENABLE_ADDRESSABLE_PROFILER
AddBundleToProfiler(Profiling.ContentStatus.Active, m_Source);
#endif
While the suggestion to move this down about 4 lines seems like it could fix any issues, I am hesitant to move it without knowing for sure since the repro is not working.