(1381973) UIToolkit References to any ressources/files corrupts UI Documents and return null errors

Unity Engine
,
1

Using 2022.1a15.
Case #1381973

  1. What happened
    UI documents are no longer valid if they contain references to other unity ressources (textures, fonts, etc). This a regression from 2022.1a13.

  2. How can we reproduce it using the example you attached

  • Open attached project.
  • Go to /Assets/UI
  • Notice all UI Documents being no longer valid uxml
  • Open any of the UI Documents and remove references to background-images & fonts ressources in the uxml
  • Notice UI Document being valid again

Can also be reproduced with empty a15 project:

  • Create new UI Document via Assets → Create → UIToolkit → UI Document
  • Add an empty visual element to newly created UI Document
  • Add any texture to the visual element’s “Background-Image”
  • Save UI Document
  • Notice UI Document no longer being valid and null-reference errors
2

Just pinging @JuliaP_Unity , to know if it’s known issue or I am doing something terribly wrong.

Seems like a pretty big oversight as it breaks any UITK project in this alpha…

3

Thanks for reporting the bug, it’ll be processed by QA. Just to be clear, you mean 2022.1.0a15 on your first message, correct?

4

Yes, apologies. Edited the original message.

5

You didn’t mention how you modify the UIDocument, is it using the UI Builder?

6

Yes, in the UI Builder. I can see the generated uxml, appears to be the same as a13 - so it doesn’t appear to be a UI Builder code generation issue on first glance.

7

That’s great news then, as it had already been found internally and is being currently worked on :sunglasses:

1 Like
8

Wohoo! Aaah, just wished I could leverage a15’s features sooner rather than later. Oh well, I assume we’re talking about release for a17+ probably right? (In two weeks if there’s no additional delays.)

9

Hard to tell when it’s out, but as QA processes your bug report that should lead you to a trackable link that you can check.

1 Like
10

Sorry to be a bother.

QA came back and said that “Unfortunately we can’t provide you with an issue tracker link due to a duplicate case being private.” Tried a16 and unfortunately the issue is still present. All my UXMLs are broken from a13->a15/a16.

Could you share some insight on when we can expect a fix to land in the alpha for this issue?

Thank you

11

If I’m seeing this correctly the next release should have the fix. This version is being tested already.

We’re sorry for the inconvenience! :sweat_smile:

1 Like