Live Update file in bundle resources folder

[AarrrBee]

I’m looking to remove a collection loaded via a proxy from the initially-loaded set of data, and load it with Live Update, to keep the initial download size below the threshold required for a web platform (HTML5 build)

Using the Zip → Save in Bundle Folder option works great, as the zip file is included in the final build folder. I can upload the whole folder, and trivially mount the zip file with liveupdate.add_mount(). Here’s what that looks like (screenshot of a modified version of a defold/examples project that I’m using for testing):

Ideally, I’d do the same for other build targets, to avoid having two different versions of the collections file (one version with a proxy marked ‘excluded’). However, bundling e.g. a Mac version , the file is excluded. I’m guessing this is because there’s an additional bundling step? Can I force it to be included somehow?

[AGulev]

You are able to build for mac without live update:

So everything will be in the main bundle without live update resources (even if you have “excluded” on a collection)

[AarrrBee]

You’re right. So I misunderstood the meaning of ‘Publish Live Update content’.
I thought that the Live Update policy was set in liveupdate.settings and excluding collections, and then in this window I was making a build with or without the LU resources:

Checked - “Build the application, which may be configured to load LU resources, and build the LU resources”
Unchecked - “Build the application, which may be configured to load LU resources, but don’t build the LU resources”