Android builds differ vastly in size depending on machine

Unity Engine
1

We are usually building our Quest app from a build machine, but today I tested building on multiple machines (trying to reproduce a build bug) and was very suprised about the difference in build size.

From exactly the same commit, with exactly the same set of files, there’s a 50MB difference in build size between two machines both running exactly the same Unity + Android platform versions (same Windows versions, fresh installs of Unity 2019.3.0b11 + accompanying full Android toolchain).

5200607--517142--upload_2019-11-22_0-16-32.png

APK Analyzer shows that one apk (the smaller one) is split into parts while the other isn’t:

5200607--517154--upload_2019-11-22_0-22-0.png
5200607--517154--upload_2019-11-22_0-22-0.png1186×818 65.9 KB

I tested both on the Quest and they are absolutely identical in terms of functionality and content. Any idea what’s going on?

2

@LeonhardP I’m not 100% sure but I think this is a new issue in 2019.3 (at least I haven’t seen it before).

3

Hi @fherbst ,

To better trace down this issue, can you tell us:

  • Are you using the asset database V1 or V2 for this project?
  • Are you using a cache server? (Unity Accelerator)

If you are using V2 and the new cache server, can you try to see if you can reproduce the behaviour while using ADBv1?

Thanks for reporting the issue.

4

AssetDatabase V2, not using Cache Server / Accelerator.

The machine with the smaller build is actually the one where the project has been on for much longer (since January, in fact) and was on V1 at some point in the past (but there have been quite a number of full library reimports in the meantime).
The machine with the larger build has that project on for just a couple of weeks now (and never had a version with V1).

I’m not sure I will have time to do full V1 reimports on those as it’s a pretty big project (> 40 GB) … Does the above help already?