Bug NullRef ScriptableObject inside baked managed component in build in 2022.2.2 unity

In my project I have managed component which includes

ScriptableObject

and

Material

. This component baked by using

Baker.AddComponentObject

. All works well before 2022.2.2 unity version.

The problem is:

ScriptableObject

is always nullref in build, but other instances isn't null. Problem happens in build only.

Also problem fixed by adding one another

ScriptableObject

to class which now becomes nullref in build and previous one loaded well. So my suggest is there is something wrong with memory layout in 2022.2.2, burst package was updated in this version.
Note: this workaround requires extra SO be serialized and at least one entity in subscene should have not null instance for this SO (any other can remain null instance)

Feels like complete magic

Resolved: Fixed in 2022.2.3 unity version. The thing was

[FormerlySerializedAs]

with the same field name.

 

I had taken the liberty of submitting the bug report for this project.
Case IN-29284.

 

Hmm. Was it just 2022.2.2? I'm pretty sure a similar issue exists in 2022.2.1 (maybe even 2022.2.0)
I've seen multiple reports of assets assign on managed components and not being included in the build (and can repo it myself.)

 

I have some similar build-only issues in 2022.2.0f1/1f1/2f1. I thought it was just to do with sub-assets and WeakObjectReference (ECSB-145), but now I’ve also seen similar broken SO deserializations in managed components. In the one case I’ve had to use them, a SO containing a list of SO only deserialized one object properly while leaving the rest null. There’s definitely something screwy going on here.

 

I'm sure it was fine with SO a version before (2022.2.1) because there was issues with builds for my project which I solved and all was fine in build. Right after switching to 2022.2.2 build works wrong because of bad SO thing

 

where can I inspect this? I never submited bug report

 

Unfortunately, only the ones who submit the reports and Unity can see them.

 

This was not resolved by any mean. I've just upgraded to 2022.2.4 and changed a bit of my ScriptableObject setup then the build stops working again.

But now I know where to look for the bug so I went checking the refs to my ScriptableObjects: all of them are null at runtime.

 

The current workaround is baking SO into blob assets. It's fine for now, but I imagine it can be complicated at the later stage of the project.

 

@Tony_Max I think this bug is fixed in Unity 2022.2.5 according to the changelog

I've reverted my workaround, made a change to the SO setup, and the build still runs correctly.