Search Issue Tracker
Fixed
Votes
0
Found in
Issue ID
1201409
Regression
No
[Hub] Hub UI does not reflect the uninstalling state when multiple Unity versions are queued for uninstalling
How to reproduce:
1. Open Unity Hub
2. Make sure that you have at least 2-3 Unity versions installed through Hub
3. Queue multiple Unity versions to be deleted through Unity Hub
4. Notice the "Uninstalling (queued)" messages under selected versions
5. Wait for the first version one to be uninstalled
Expected results: Next Unity version starts to be uninstalled, and UI reflects that
Actual results: All queued Unity versions lose the "Uninstalling (queued)" markings, even though they are still queued.
Reproducible with: 2.0.4, 2.2.2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in Unity Hub 2.4.0
Versions queued for uninstalling are not showed when process starts, as they are being uninstalled in parallel after certain point, but all queued versions are uninstalled correctly. This may look confusing from UI perspective, and might be revisited in Hub v3