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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.