Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.3.10f1
6000.4.0b11
6000.5.0a8
6000.6.0a1
Issue ID
UUM-135761
Regression
No
Strip button in the Web Stripping Tool's Select Submodules window does not start the stripping process
Steps to reproduce:
- Open the attached project
- Switch to the Web platform if it isn't already selected
- Open the Web Stripping Tool window (Window -> Web Optimization -> Submodule Stripping)
- Scroll down the Submodules list
- Press the Select Submodules button
- In the Select Submodules window, modify which submodules are selected
- Press the Strip button that's next to the Submodule name column
Actual results: Nothing happens
Expected results: Window is closed, presenting the functioning Strip button in the Main Strip Submodules window, or it starts the stripping process
Reproducible with versions: 6000.2.0a10(1.0.0), 6000.3.10f1, 6000.4.0b11, 6000.5.0a8(1.2.0, 1.2.1)
Can’t test with versions: 6000.0.69f1 (Web Stripping Tool package not available)
Tested on (OS): macOS 26.3, Windows 11
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.