Difference machine building app and addressables

Unity Engine
,
1

I’ve been using addressable for awhile now but this is first time I’ve met this issue but I totally understand it.
So I’ve setup a automation system at my mac to use gitlab-runner to automate building my application. But at difference machine (window OS) I’m use to edit, build and upload addressable for that application. Everything work fine until I have to include 1 addressable group to built-in application.
Well the things is that that application cannot read the built-in addressable group anymore. The bundle name change in the catalog so I change the name format of that bundle from append to file name to file name only and encountered the CRC miss match.
What is the optimal way to resolve this kind of situation? Is addressable have some kind of ignoring the CRC?

I’m using Unity2020.1.9f1 and Addressable 1.13.1
Cannot update the package since I have a lot of fix and workaround and can’t afford to fix them if upgrading the addressable package (Well at least for now)

These are the error from Android Studio logcat:

2

Bouncing this off the team for some guidance!

1 Like
3

There is an option to turn off CRC checking, in the Group Settings under Content Packing & Loading Schema, in Advanced Options, that you could try.

4

There’re some issues about the CRC miss match, will disable this will cause any trouble? I’m currently suffer some kind of CRC miss match when load resource from remote. Can I disable CRC for remote assets too?

5

You can disable it for remote assets, but if you don’t validate the CRC when the download happens then you don’t know if that bundle was corrupted for any reason. When you turn it off for local bundles, you can probably be more confident that any cached data has already been verified and isn’t corrupted. So it just depends on how secure you need it to be, but you could try it and see if it’s helpful

1 Like