Build For Content Update

Hi

When I use Build For Content Update.
After that my StreamingAssets folder will be clean up.
All the json file are deleted.
Does someone have the same issue?

Thanks.

 

Hi

I found ContentUpdateScript.BuildContentUpdate have a Cleanup function.
The addressable build path will be delete in the function.
But it seems does not generate new file in build path.
Is it normal or bug?

Thanks.

 

are there errors in your build? If the update build deletes any json files (catalog or settings) they should be re-created.

Of note, are they in StreamingAssets/aa or StreamingAssets/com.unity.addressables? We changed that path in the latest update (see changelog for info on how to best update that).

 

Hi

I do not get any errors.

After update build my StreamingAssets folder is empty.

It does not contains any folder.

In ContentUpdateScript.BuildContentUpdate the json file seems will be create by

But after this line,the cleanup will be called.

Maybe Cleanup need to be called early than create json file.

Thanks.

 

Same issue. Every time i build for content update, the streamingasset/aa folder will be deleted

 

That does seem very broken. and yet that code hasn't changed in a while. I'm not sure how it was working before. We'll get to fixing this one, and hopefully get it dealt with in a patch release soon (soon meaning maybe next week, probably not this week at this point).

-Bill

 

Thank you!!

 

Hi，I do not kown how to post new thread, it will show me the error ,I do not know how to set Tags,is it have some speial tags? who can help me, It's better to show me your printscreen,thank you !

 

Maybe you can try cancel the tag and post again.

 

Hi Bill
can you help me? I don't quite understand some of the parameters about AddressableProfiler, Or You can provide me with a link to the documentation .
Thank you!

 

The 10 is the scale. If your ref count got to 11, that number would grow, and the entire graph would visually shrink.

as to the 8, it means there are 8 references to that thing. Could be you loaded it 8 times. Could be instantiations. Could be that you loaded something else that has that thing as a dependency.