Only some users brought this up. I don’t know exactly if it is due to an apk with a different version number then the .obb expansion pack. I was just curious if it makes any difference to the corona sdk when it runs the apk which .obb expansion file version number is set to the apk? If it doesn’t make a difference then good, if it is essential that what is uploaded is the same apk and .obb expansion version number then good if it’s indicated in the corona reference docs.
Had a few more customers with this issue and the apk and .obb are the same version.
Basically they have already downloaded and installed the game, their version is obviously verified so why does this screen even appear if their app is already licensed and the expansion file is already downloaded?
If they attempt to press restart download of course they only get the Download error. Error contacting server.
Just want to find some solutions i can tell these customers. I have already mentioned to them that google stores the info on their device so they should not need a connection after the initial game launch. I’ve tried many times to install and disable wifi, switch on airplane mode, clear google play store cache and the app always launches perfectly. So any help/suggestions I could tell these people as to what my be the problem?
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
Only some users brought this up. I don’t know exactly if it is due to an apk with a different version number then the .obb expansion pack. I was just curious if it makes any difference to the corona sdk when it runs the apk which .obb expansion file version number is set to the apk? If it doesn’t make a difference then good, if it is essential that what is uploaded is the same apk and .obb expansion version number then good if it’s indicated in the corona reference docs.
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
I have noticed this issue with one of my app builds (uploaded with an expansion file) as well. In my case, the screen is not broken (like in defossez.aurelien’s image). But, I am curious as to why this screen even happens upon first app launch (assuming wi-fi is turned off).
I’ve read in some sources that “On most devices, Google Play downloads the expansion file(s) at the same time it downloads the APK, so your application has everything it needs when the user opens it for the first time. In some cases, however, your application must download the files from Google Play when your application starts.”
Assuming this were the case, I would hypothesize that the .obb file would not yet be downloaded to the respective directory on my Samsung Tab 3 immediately upon app installation (and before first app launch) because “In some cases, however, your application must download the files from Google Play when your application starts.”. Nonetheless, the .obb file exists in the proper directory, which is confusing because why am I being asked to download the resource files then? FYI, once I turn the wi-fi back on and press the “Restart Download” button, the app works as normal from that point forward. It does not even seem to take any time (like 1 sec) to download whatever it’s looking for… if it were downloading the .obb, I’d assume it would take a very long time because it is a pretty large file. This seems to support my observation that the .obb file is already downloaded.
My expectations for the app would be that the expansion file would download and install with the APK from the Play Store. Even if I don’t have Wi-Fi upon my first app launch, I would expect that my app should start as normal and not get this screen. Would you mind helping me understand why my expectation might be wrong? Also, is there a solution to this issue?
I am using Corona build 2014.2511.
Had a few more customers with this issue and the apk and .obb are the same version.
Basically they have already downloaded and installed the game, their version is obviously verified so why does this screen even appear if their app is already licensed and the expansion file is already downloaded?
If they attempt to press restart download of course they only get the Download error. Error contacting server.
Just want to find some solutions i can tell these customers. I have already mentioned to them that google stores the info on their device so they should not need a connection after the initial game launch. I’ve tried many times to install and disable wifi, switch on airplane mode, clear google play store cache and the app always launches perfectly. So any help/suggestions I could tell these people as to what my be the problem?
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
I have noticed this issue with one of my app builds (uploaded with an expansion file) as well. In my case, the screen is not broken (like in defossez.aurelien’s image). But, I am curious as to why this screen even happens upon first app launch (assuming wi-fi is turned off).
I’ve read in some sources that “On most devices, Google Play downloads the expansion file(s) at the same time it downloads the APK, so your application has everything it needs when the user opens it for the first time. In some cases, however, your application must download the files from Google Play when your application starts.”
Assuming this were the case, I would hypothesize that the .obb file would not yet be downloaded to the respective directory on my Samsung Tab 3 immediately upon app installation (and before first app launch) because “In some cases, however, your application must download the files from Google Play when your application starts.”. Nonetheless, the .obb file exists in the proper directory, which is confusing because why am I being asked to download the resource files then? FYI, once I turn the wi-fi back on and press the “Restart Download” button, the app works as normal from that point forward. It does not even seem to take any time (like 1 sec) to download whatever it’s looking for… if it were downloading the .obb, I’d assume it would take a very long time because it is a pretty large file. This seems to support my observation that the .obb file is already downloaded.
My expectations for the app would be that the expansion file would download and install with the APK from the Play Store. Even if I don’t have Wi-Fi upon my first app launch, I would expect that my app should start as normal and not get this screen. Would you mind helping me understand why my expectation might be wrong? Also, is there a solution to this issue?
I am using Corona build 2014.2511.
I’m running 2511 and having the same problem with some users - the vague “Download Error - Error contacting server”. It seems that only some users face the problem, and it all started only after moving to an expansion file (> 50MB).
I really hope the Corona guys look at this and take a seriously as it’s impacting my ability to do business.
Nathan.
We need a reproducable test case in a filed bug report. Even though if this is sporatic and only affecting some users, it could be networking problems between their computers and Google’s servers which we have no control over.
Rob
Thanks Rob - I’ll push the user for more detail.
The user is able to use the game on his tablet, but he’s consistently getting this issue coming up on Samsung Galaxy S3 mini running Kitkat 4.4.4
Are you using Graphics 1 compatibility mode or is this a Graphics 2.0 build?
Compatibility.
Well the original topic “file download screen broken” appears to be a problem for people using graphicsCompatiblity = 1 in their config.lua’s to keep using the old layout. We don’t plan on fixing that. The answer is to move to Graphics 2.0.
But if this issue is different and it’s just about the communications issues, we will need a reproducible test case to give engineering.
Rob
My user does have good connectivity, but I guess there’s a chance it’s related to graphics compatibility. I’ll try to get him to do some more testing.
Nathan.
I’ve come across all these kind of problems (didn’t download and get the ugly restart download screen which doesn’t work, the licensed but doesn’t work, the version that worked and then after updating it is no longer licensed, the list goes on), and in most cases its due to the users.
Top of the reasons are not being connected (or having a solid connection) to the internet when they first launch the game, although I’m not sure if this is also the case with updates of a game.
Other reasons can include the connection to google servers which is usually terrible, users having messed up their files when they rooted their devices, right up to not having enough space on their device (even ahad a user complain so much until he finally realised his device date was wrong hence the reason he got a not licensed issue).
Key in replying to the users is to give them the basic 3 steps, download, install, launch first time (while connected). If they have issues, clear their google store cache first, then try the steps again.
But, since i only use graphics2.0 some of the issues you are facing might just be relating the graphics compatibility.
Hi,
I use Graphics 2.0 and still get this error.
Even in my first I used Graphics 2.0.
It seems to me that this thread is trying to solve two issues. One is the information screen being drawn partially off screen. The other is apparently networking related. We believe the first issue is happening with apps running in Graphics 1 compatibility mode. The second one sounds like communications issues between the user and Google.
In either case, Engineering is going to need a reproducable test case filed as a bug report.
Rob