We just built an app whose built-in assets were large enough that we had to use an expansion file (for the first time) to get it in the Play Store.
I tried manually installing the minimal apk and adb pushing the obb file to make sure it worked, and it worked great. So we submitted it to the store.
It’s made it through the store to availability to testers, and some folks are getting a working app, and others are getting a blank screen because it can’t find our loading screen asset.
This would seem to indicate some problem with the expansion file (since all our assets are in there), but I don’t know where to even begin debugging it.
I did use “adb ls” during the install to confirm the obb file was being downloaded from the play store and that it was exactly the right size in bytes. So presumably I actually have the odb.
But when I launch the app it’s behaving as if it couldn’t get to the assets in the ODB.
It’s failing on my Nexus 10, running Android 4.2.2. I’ve reinstalled and restarted it repeatedly, it always errors out when it fails to find that asset.
It ran fine on a Xoom tablet with Android 4.1.2.
It did the blank screen thing at first with a Galaxy S3 running 4.4.2. But after a few force quits it started working. Then we uninstalled and reinstalled the app and got the same error, unable to find an asset file. Force quitting and reinstalling after this point had no effect, we could not get it to work again.
I’m at a loss as to where to even begin debugging this. Unpacking and making available the contents of the expansion file is out of my control as a programmer, it’s something that Corona is supposed to do for me. It’s particularly difficult because this problem only appeared once we were distributing (for testing) through the Google Play Store, so its’ not like I could quickly insert some debug or anything.
Any advice would be very much appreciated.