Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.4.0b2
6000.5.0a3
Issue ID
UUM-130376
Regression
Yes
“com.unity.xr.Interaction.toolkit” is displayed as a package name in Package Manager
Reproduction steps:
1. Create a new project
2. Window > Package Management > Package Manager > Unity Registry
3. Select AR or VR under Features foldout
4. Select Packages Included section and observe XR Interaction Toolkit package
Actual result: “com.unity.xr.Interaction.toolkit” is displayed
Expected result: “XR Interaction Toolkit” is displayed
Reproducible with: 6000.4.0a4, 6000.4.0b1, 6000.5.0a3
Not reproducible with: 6000.0.64f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0a3
Reproduced on: Ubuntu 24.04, macOS Tahoe 26.1 (M4)
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.5.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.