Search Issue Tracker
Fixed
Fixed in 2022.3.26f1, 2023.2.20f1, 6000.0.0b14
Votes
0
Found in
2022.3.21f1
2023.2.13f1
2023.3.0b10
6000.0.0b11
6000.0.37f1
Issue ID
UUM-65607
Regression
Yes
“Unable to use a named GUIStyle without a current skin“ error appears when installing/uninstalling a package if the “Search” window has any text in the search field
How to reproduce:
1. Create a new project
2. Go to Menu > Window > Search > New Window
3. Add any text in the search field
4. Open Package Manager and install or uninstall any package
5. Observe the Console window
Expected result: No errors
Actual result: “Unable to use a named GUIStyle without a current skin” error appears
Reproducible with: 2022.2.2f1, 2022.2.21f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10
Not reproducible with: 2021.3.36f1, 2022.2.1f1
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
Note: not reproducible without text in the search field
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note (fix version 6000.0.0b14):
Fixed in: 6000.0.0b14