( 1.1.7 ) Strange downloading behaviour reported in Android with Firebase TestLabs

We are seeing some strange behaviour on some of the Android devices tested in Firebase Testlabs & Google prelaunch-reports.

In our loading process we call `Addressables.DownloadAsync` to preload our asset bundles. We use a single label "preload" for the assets we want to preload.

If you watch the GIF, you can see the downloading phase (when you see the MB downloaded) and you can see it jumps around. We are utilizing the `operation.PercentComplete` to set the percentage.

The google prelaunch-reports give a lot of feedback into how the loading process is operating. I have see this behaviour on a few of the devices ( mostly lower end ) .

K7 2017 device

 

This is completely reproducible in the Firebase Testlab.

 

hmm, that is odd. We'll do some investigating. A few follow up questions:
1. do you know how many bundles are being downloaded in that gif?
2. where are you getting the 7.0mb? GetDownloadSizeAsync?
3. where are you getting the first number (download so far)? Just 7mb * %?

 

We have about 11 bundles, all set with the same label.

3 groups, all set to pack separately. We'll probably change this, nevertheless that's what they're set to now.

Correct. Bytes returned / 1000000

This may be where we are going wrong.
We take the downloadOperation.PercentComplete * TotalDownloadSize.

TotalDownloadSize is from GetDownloadAsync

 

we'll check on things.