Search Issue Tracker
Active
Under Consideration for 1.21.X
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 “addr_repro“ 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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment