Search Issue Tracker
Fixed
Fixed in 6000.6.0a1
Won't Fix in 6000.4.X
Votes
3
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a3
6000.6.0a1
Issue ID
UUM-131781
Regression
No
Newly created organization doesn't appear in the Package Manager "Export" menu
How to reproduce:
1. Create a new Unity project
2. In Unity Cloud, create a new organization
3. Go to Window -> Package Management -> Package Manager -> "+" button -> Create Package
4. Click "Export" and observe the "Authoring Org" dropdown options
Expected results: The new organization is visible there because it is already visible in the Project Settings and Hub
Actual results: New organization is not shown
Reproducible with: 6000.3.3f1, 6000.4.0b3, 6000.5.0a3
Can't test with: 6000.0.65f1 (No such functionality)
Reproducible on: macOS Tahoe 26
Not reproducible on: No other environment tested
Note:
- Creating a new project after creating an organization doesn't solve an issue
- Restarting the project doesn't solve an issue
- Linking the project to the new organization doesn't solve an issue
- New organization also doesn't appear when editing the package in the Inspector
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
- Resize to Fit option for Import Activity window's Columns does nothing
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (6000.4.X):
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.