Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.12f1
6000.4.2f1
6000.5.0b2
6000.6.0a3
Issue ID
UUM-139714
Regression
No
"Invalid image specified" warnings are thrown when clicking anything in the UI Builder after changing the assigned to Visual Element Vector Image Asset type
How to reproduce:
1. Open the attached project "VectorBug"
2. Create the new UI Document and open it
3. Add a new Visual Element -> Background -> Change the "Image" field to "Vector" -> Assign the "Test-SVG"
4. In the Project window, select the "Test-SVG" Asset
5. In the Inspector, change the "Generated Asset Type" to "Texture2D" and click "Apply"
6. Click anything in the UI builder and observe the results
Expected results: No warnings are thrown
Actual results: "Invalid image specified" warnings are thrown with each click
Reproducible with: 6000.3.12f1, 6000.4.2f1, 6000.5.0b2, 6000.6.0a3
Can't test with: 6000.0.71f1 (No Vector Image import support)
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
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
- UI counter displays incorrect collectible count when using "Remaining_Collectibles_UI" Prefab in "Get Started With Unity" template
- Camera Output Texture does not revert back to previously set Render Texture when camera selection in UI Builder canvas background is changed
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
Resolution Note:
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.
Resolution Note (6000.6.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.