In-game expansion file download screen broken

When the game is too big and needs and expansion file, a Corona screen may appear to download it when you first launch the game.

This screen is broken and all the object positions are incorrect (see screenshot). Part of the name of my game appears (KAWAII KILLER).

Screenshot_2014-05-18-13-12-02.png

This screen appears when the device has no internet connexion when first launching the game.

Steps to reproduce:

  • Download and install a Corona app with an expansion file (.obb)

  • Remove any internet connexion (either WiFi, 3G, or any other way to connect to the web)

  • Launch the game

Log:

V/Corona &nbsp;(32071): \> Class.forName: network.LuaLoader V/Corona &nbsp;(32071): \< Class.forName: network.LuaLoader V/Corona &nbsp;(32071): Loading via reflection: network.LuaLoader I/Corona &nbsp;(32071): Platform: SM-T210 / ARM Neon / 4.1.2 / GC1000 core / OpenGL E S 2.0 V/Corona &nbsp;(32071): \> Class.forName: CoronaProvider.licensing.google.LuaLoader V/Corona &nbsp;(32071): \< Class.forName: CoronaProvider.licensing.google.LuaLoader V/Corona &nbsp;(32071): Loading via reflection: CoronaProvider.licensing.google.LuaLo ader V/Corona &nbsp;(32071): WARNING: Asset file "android.app@2x.icon://" does not exist.

The last line, about the “android.app@2x.icon://” asset file, shows  up everytime I click on “Restart Download” (which also shows a “Error contacting server” native dialog).

The error is not coming from my code, because not a single line of the game is executed at this step.

The Simulator version is the following: 2014.2189 (2014.3.6)

I have in my project folder the following icons (as it may come from this):

Icon.png Icon-72.png Icon-hdpi.png Icon-ldpi.png Icon-mdpi.png Icon-xdpi.png

Should I add @2x and @4x icons or something?

build.settings

settings = { orientation = { default = "landscapeRight", supported = { "landscapeRight", "landscapeLeft" } }, iphone = { plist = { UIStatusBarHidden = true, UIPrerenderedIcon = false, UIApplicationExitsOnSuspend = false, UIAppFonts = { "KawaiiKiller.ttf", "KawaiiBold.ttf" } } }, android = { googlePlayGamesAppId = "xxxxxxxxxxx (private)", usesExpansionFile = true, usesPermissions = { "android.permission.INTERNET", "android.permission.VIBRATE", "android.permission.WRITE\_EXTERNAL\_STORAGE", "com.android.vending.CHECK\_LICENSE" } }, plugins = { ["CoronaProvider.gameNetwork.google"] = { publisherId = "com.coronalabs", supportedPlatforms = { android = true } } } }

config.lua

application = { content = { width = 200, height = 320, scale = "letterBox", fps = 60, imageSuffix = { ["@2x"] = 2, ["@4x"] = 4 } }, license = { google = { key = "xxxxxxxxx (private)" } } }

What version of Corona SDK are you running?

Sorry, forgot to mention that (I’ll edit my post).

Version 2014.2189 (2014.3.6)

Am I really the only one having this bug?

I tried to do some stuff, like adding @2x icons, but it changes nothing.

Are you running with graphicsCompatibility = 1 in your config.lua?

Rob

Hi @defossez.aurelien,

This was fixed in build #2248, but you won’t have access to it until the next public build. And, there will still be an issue if you’re using V1 compatibility mode.

Best regards,

Brent

Thanks for the answer, I look forward to this update. Do you have an ETA of this next release for the public?

I don’t use v1 compatibility mode (I posted my config.lua file).

Thanks,

Aurélien

Hi Aurélien,

I don’t have an ETA on the next public build, but it shouldn’t be incredibly too far away. I’ll see what I can find out from engineering.

Brent

What version of Corona SDK are you running?

Sorry, forgot to mention that (I’ll edit my post).

Version 2014.2189 (2014.3.6)

Am I really the only one having this bug?

I tried to do some stuff, like adding @2x icons, but it changes nothing.

Are you running with graphicsCompatibility = 1 in your config.lua?

Rob

Hi @defossez.aurelien,

This was fixed in build #2248, but you won’t have access to it until the next public build. And, there will still be an issue if you’re using V1 compatibility mode.

Best regards,

Brent

Thanks for the answer, I look forward to this update. Do you have an ETA of this next release for the public?

I don’t use v1 compatibility mode (I posted my config.lua file).

Thanks,

Aurélien

Hi Aurélien,

I don’t have an ETA on the next public build, but it shouldn’t be incredibly too far away. I’ll see what I can find out from engineering.

Brent

We just had the same issue - I also see an alert message “Download Error” as the title and “Licensed” as the text. You can’t get past this screen. I’m downloading the latest build (from 4th July) to see if it’s fixed.

We just had the same issue - I also see an alert message “Download Error” as the title and “Licensed” as the text. You can’t get past this screen. I’m downloading the latest build (from 4th July) to see if it’s fixed.

I just saw the same issue using build 2466 and a 50MB expansion file.

I could not reproduce it, but it looked janky enough that I just decided to cut some graphics instead to get below 50MB.

It would be great to understand how and when this happens. I think it reflects poorly on your app to have something like this appear…

Some of my customers are getting the same issue. I build with .2499 latest build. I am wondering if it has anything to do with updating an apk but selecting an older expansion file? For example upload a new apk version 10, but Google gives option to use expansion file from previous upload apk version 9. Is this what causes the download error: licensed and hang the game on the above mentioned screen?
If someone can confirm whether we must always upload the expansion file with a new apk (ie apk and expansion file version 10) regardless of whether the expansion file has any changes in it or not? It’s strange that Google lets u select an older expansion file with a newer apk version if it’s not going to work. The reason not to upload the new expansion file is of course due to Google servers not always being able to upload and process correctly, so in a way it makes sens if ur expansion file has not changed to be able to set the new apk to use an older already uploaded expansion file.

Why not try uploading an expansion pack of the same version number and seeing if that solves it?

Rob