Android Expansion Files

Solar2D General Questions/Discussion
#1

Hi All,

Need some help with Android expansion files. We’ve submitted our app twice for Alpha testing and it got rejected both times. Issue seems to be caused by the expansion files. I’ve followed the steps in this blog post, https://coronalabs.com/blog/2013/04/17/expansion-file-support-for-android/, which are:

  1. Updating your build.settings

    settings = { android = { usesExpansionFile = true, usesPermissions = { “android.permission.INTERNET”, “com.android.vending.CHECK_LICENSE”, “android.permission.WRITE_EXTERNAL_STORAGE” } } }

  2. Add your Google license key in config.lua

    application = { license = { google = { key = “Your key here” } } }

  3. I also made sure to upload the .obb files in the Google Play Console

Anything that we might have missed? And is it possible to test expansion files locally?

I’ve attached some screenshots of the error encountered by the testers in Google.

#2

I had no problems with expansion file that I uploadded recently on google play, except that a new version should always be uploaded when the app itself is changed. I guess you’ve made sure all above 3 steps are ok, maybe what’s left is:

  1. when you build for android make sure to select google play on target app store

  2. use the correct keystore

#3

The app needs to be published first in alpha before testing as explained here.

#4

@Odisej Thanks for the reply. I’ve made sure I’ve done those steps as well but still no luck. Were you able to test the Expansion files locally (thru sideloading)?

#5

@fungrip Not exactly true. Expansion files can be tested thru sideloading as mentioned here, https://developer.android.com/google/play/expansion-files.html#Testing

And even if that’s not the case, the app is being rejected while in the Draft state.

#6

@adrian This is true if you want to test your implementation manually. But if you want to test it on the Play Store, you need to publish it first, either in Alpha or Beta, the draft build will not be testable. Also, see this forum post. As per the links

 

To test your application’s implementation of the manual download procedure, you can publish it to the alpha or beta channel, so it will only be available to authorized testers. If everything works as expected, your application should begin downloading the expansion files as soon as the main activity starts.

Assuming this feedback that you get is from Pre-launch Report, note that it is an automated test of the draft build. 

#7

I had no problems with expansion file that I uploadded recently on google play, except that a new version should always be uploaded when the app itself is changed. I guess you’ve made sure all above 3 steps are ok, maybe what’s left is:

  1. when you build for android make sure to select google play on target app store

  2. use the correct keystore

#8

The app needs to be published first in alpha before testing as explained here.

#9

@Odisej Thanks for the reply. I’ve made sure I’ve done those steps as well but still no luck. Were you able to test the Expansion files locally (thru sideloading)?

#10

@fungrip Not exactly true. Expansion files can be tested thru sideloading as mentioned here, https://developer.android.com/google/play/expansion-files.html#Testing

And even if that’s not the case, the app is being rejected while in the Draft state.

#11

@adrian This is true if you want to test your implementation manually. But if you want to test it on the Play Store, you need to publish it first, either in Alpha or Beta, the draft build will not be testable. Also, see this forum post. As per the links

 

To test your application’s implementation of the manual download procedure, you can publish it to the alpha or beta channel, so it will only be available to authorized testers. If everything works as expected, your application should begin downloading the expansion files as soon as the main activity starts.

Assuming this feedback that you get is from Pre-launch Report, note that it is an automated test of the draft build.