Search Issue Tracker

Active

Under Consideration for 6000.6.X

Votes

0

Found in

6000.0.71f1

6000.3.11f1

6000.4.0f1

6000.5.0a9

6000.6.0a1

Issue ID

UUM-137273

Regression

No

UXML file gets corrupted and "Assertion failed" errors when selecting incompatible asset with Advanced Object Selector in UI Builder "Data Source" Object

UI Builder

-

Steps to reproduce:

  1. Create a new project using Universal 3D template
  2. Go to Edit > Preferences > Search and change the "Object Selector" dropdown from "Classic" to "Advanced"
  3. Create a new UXML Document asset and open it in UI Builder
  4. Add a Visual Element to the Hierarchy
  5. In the Inspector, in Bindings foldout, click on the "None (Scriptable Object) object picker
  6. Select any incompatible item, for example - Font Asset
  7. Save the file
  8. Observe the Console

Actual results: "Assertion failed on expression: 'type != SubFilterType::Exact'", "Assertion failed on expression: '!subFilter.dbPath.empty() || subFilter.type != SubFilterType::Exact'", "An infinite import loop has been detected." errors and UXML files become corrupted

Expected results: Incompatible items should not be available for selection in the 6th step

Reproducible with versions: 6000.0.71f1, 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1

Tested on (OS): Windows 11

Notes:

  • Even with "Classic" Object Selector, some shown options are not valid for the property; therefore, I assume they should not be shown and available for selecting
  • Additionally, the Editor sometimes crashes when trying to close it

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.