Any Documentation For Expansion File Support In Build 2013.1082?

Was this a response to the Not licensed issue? I get the same issue. I use another account for corona sdk but the google account on my device is listed as a test device.

I am doing the same for native android (with extension apk) and here it works

Please help-

Joshua Quick

I entered the code you suggested to test the Google Play licensing connection. all I get with adb logcat is:

IDIA Tegra 3 / OpenGL ES 2.0 16.05001 / 2014.2368

V/Corona  (  749): > Class.forName: CoronaProvider.licensing.google.LuaLoader

V/Corona  (  749): < Class.forName: CoronaProvider.licensing.google.LuaLoader

V/Corona  (  749): Loading via reflection: CoronaProvider.licensing.google.LuaLoader

the screen shows the app icon and name at the top of the screen. there is a really short loader line, and absolutely nothing else happens…

I’m running a fairly robust tablet and the latest build of Corona with loads of ram:

 Platform: ASUS Transformer Pad TF300T / ARM Neon / 4.2.1 / NVIDIA Tegra 3 / OpenGL ES 2.0 16.05001 / 2014.2368

it appears to download the entire 107 MB of the app (obviously including the .obb) from Google Play and says it has been installed, but when I open…nada!

my clients are waiting for this game to be published, and I was able to publish it before from my personal playstore location (after similar problems finally somehow worked their way out–mostly, a lot of Corona SDK version switching and e little error correction that _adb log cat _helped me with.

any help would be much appreciated. I put another print command in the main.lua also at the beginning, but that didn’t print out out through _adb logcat_either. I should mention I’m getting the same dead loading screen results if I add the app directly to the tablet. _adb logcat _shows no errors.

thanks!

p.s., when I tried to download it to an android phone, I get “…requires external storage functionality. Please retry after ensuring that external storage space is available.” I get the same error when I install it to the phone directly. I wasn’t getting this before either.