Search Issue Tracker
Fixed
Fixed in 2021.3.19f1, 2022.2.5f1, 2023.1.0a25
Votes
0
Found in
2021.3.11f1
2022.1.18f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-16426
Regression
No
Warning “warning: Expected (<resource> | <url>) but found 'none'“ is thrown when setting Font Asset to None in UI Builder window
Steps to reproduce:
1. Open the user’s project
2. Open TestUIDocument.uxml (Assets → UIAssets)
3. Expand TestStyle.uss and select .style1
4. Set Font Asset to None in the UI Builder Inspector
5. Save and observe the Console
Expected result: No warning
Actual result: Warning “Assets/UIAssets/TestStyle.uss (line 3): warning: Expected (<resource> | <url>) but found 'none'“ occurs
Reproducible with: 2021.3.11f1, 2022.1.18f1, 2022.2.0b10, 2023.1.0a13
Could not test with: 2020.3.40f1 (Console error)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Workaround:
1. Open TestStyle.uss
2. Delete “-unity-font-definition: none;” line of code
Notes:
- Throws “IndexOutOfRangeException: Index was outside the bounds of the array” error at the 4th step (Often)
- Same issue with Font
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
- SHADERPASS has incorrect value when using Shader Graph for Built-In target
- [VFX] Gizmo still incorrectly rendered for a hidden property
- Nested object label indentation is incorrect when using the UI Toolkit Inspector
- Crash on tlsf_free when UI Elements are moved to the side by scrolling
- Setting VideoPlayer.time and pausing results in incorrect player.frame values
Resolution Note (fix version 2021.3.19f1):
Fix for 2021.3.X: Warning “warning: Expected (<resource> | <url>) but found 'none'“ is thrown when setting Font Asset to None in UI Builder window