Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135090
Regression
No
Multi select is not handled correctly when exporting Packages in the "Project" window
Steps to reproduce:
- Create a Unity project
- Go to a "Project" window
- Select "Packages"
- Right-click and select "Create UPM Package..."
- Enter the package name "Test" and click the "Create" button
- Create one more custom "Test2" package in the same way
- Return to a "Project" window
- Find newly created "Test" and "Test2" packages
- Select them both
- Right-click and select "Export -> Export Package..."
- In the "Export Package" pop-up, select org and click "Export"
- Select the location where the packages should be exported
- Open the selected location and observe the result
Actual results: Only one package is exported
Expected results: All the selected packages should be exported
Reproducible with versions: 6000.5.0a7
Not reproducible with versions: 6000.5.0a6, as the group export function landed just in the 6000.5.0a7 build
Tested on (OS): macOS - Tahoe 26.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment