I’m trying to pack all my audio files to addressable bundle to get my build under 200mb.
I’ve setup the bundle and fixed/removed all the duplicate calls from analyze-panel. My problem is that no matter what I do, the .bundle file is created inside the base build at Android.aab\base\assets\aa\Android\bundlename.bundle and thus it is part of the base instead of an additional PAD bundle.
I don’t understand what I’m doing wrong, hopefully it is just some boolean that’s wrong or something, but I’m out of ideas.
I’m running Unity 6000.0.50f1
I’ve disabled/removed all custom manifests, gradle templates, etc
No minify or such on.
Here are screenshots of some of the related settings and analyzers:
I only have one group and always clear cache and click “new build->play asset delivery” before building.
Group settings:
Addressable settings:
Let me know if you need some other info.
Hopefully someone will respond with an answer but I plan to learn addressable bundles this weekend. If I have any better luck, I’ll let you know.
1 Like
I haven’t gotten around to it yet. But I do see that there’s two options. Asset Bundle and Addressables. The unity documentation does mention that Addressables is recommended and more user friendly. Just to be clear on my end, you are implementing Addressables and not Asset Bundles?
Yes, addressables.
For reasons unknown the addressable bundle is created to
Project.aab/base/assets/aa/Android/…*.bundle
When it should be at the same level as base-folder like this:
Project.aab/asset-pack//assets/aa/Android/…*bundle
It must be something small I’m missing.
I’ll try to re-read the docs.
I solved the problem! It was as embarrassing as I feared, lol.
I hadn’t checked the split application binary, because when researching addressables the first time I read somewhere that it is just used for the old APK bundle splitting and that AAB doesn’t use it - and I never tested or questioned that.
1 Like
