Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.18f1
Issue ID
UUM-61890
Regression
Yes
The asset bundle building progress bar does not disappear when the bundle has already been built
Reproduction steps:
1. Open the attached project “MonoScriptCrash“
2. Copy the contents of the “ExtraAssets folder” into the Assets folder
3. Click Tools > Generate Files and Copy button in the Top Menu bar
4. Observe the asset bundle building progress window
Expected result: The asset bundle building progress bar disappears after the completed build of the asset bundle
Actual result: The asset bundle building progress bar popup does not get closed after 6 minutes when the bundle has already been built
Reproducible with: 2022.2.0a12, 2022.3.18f1, 2023.1.0a15
Not reproducible with: 2021.3.33f1, 2022.2.0a11, 2023.2.5f1, 2023.3.0a19
Fixed in: 2023.1.0a16
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Note: The Editor is fully functional and interactable even if the progress bar is still present
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.