Search Issue Tracker
Fixed
Fixed in 2.1.1
Votes
2
Found in [Package]
2.1.0
Issue ID
SEQ-1423
Regression
Yes
[Sequence] "Found icon file with unexpected path" error when switched to light theme
Reproduction steps:
1. Open an empty project
2. In Window > Package Manager, add the package by name “com.unity.sequences“
3. In Edit > Preferences search for “theme” and change to Light theme
4. Enter the Play Mode
5. Observe the Console
Expected result: No errors are seen
Actual result: Error "Found icon file with unexpected path: Packages\com.unity.sequences\Editor/Editor Default Resources\Icons\Light\CollectionType\Custom Performance.png." is seen
Reproducible with: 2.0.0 (2022.1.24f1), 2.1.0 (2022.3.6f1, 2023.1.7f1, 2023.2.0b3)
Not reproducible with: 1.1.0 (2021.3.29f1), 2.0.0-pre.2 (2022.1.24f1)
Reproduces on: Windows 10 Enterprise 21H2
Notes:
- Path contains spaces, but regex in Packages/com.unity.sequences/Editor/Core/Utilities/IconUtility.cs line 90 ignores spaces in file name that's why Debug.Assert on line 107 throws an error
- Reproduces with Windows Standalone Platform
- Reproduces with Android Platform
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Bricat
Oct 30, 2023 23:23
cannot use light mode as it is totally Brocken mixed with dark and light mode here and there. same console msg
Ronsu900
Aug 11, 2023 07:04
I have a similar error on 2022.2.21 with the same steps.