Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.21.20
2.0.8
Issue ID
ADDR-3645
Regression
No
The Addressable Profiler Module does not show Asset Groups when the Group has finished loading
How to reproduce:
1. Open the “AddressableTest“ project
2. Open the “BootScene“
3. Navigate to Window → Asset Management → Addressables → Groups
4. In the “Addressables Groups“ window, select Build → New Build → Default Build Script
5. Enter Play Mode
6. Open Profiler through Window → Analysis → Profiler
7. In the Profiler, select the “Addressables Assets“ module
8. Observe the Groups in the Profiler’s Detailed view
Expected result: The “Group scene“ and “Group Assets“ remain visible after loading
Actual result: The “Group scene“ are and “Group Assets“ not shown after they finish loading
Reproducible with: 1.21.20 (2022.3.21f1), 2.0.8 (2023.2.14f1, 2023.3.0b10)
Could not test with: 2021.3.36f1 (Detailed view is unavailable )
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note: 2023.2.14f1 and 2023.3.0b10 Editor versions do not show the Groups at all
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.