App has "encountered a lua error or been corrupted" on Android

Solar2D General Questions/Discussion
#81

Hi Ian,

How large is the APK? If it’s like 50+ MB, better that you zip it up and send it to me via e-mail…

Thanks,

Brent

#82

Tested the Corona 1177 build version on my Xperia Z OS 4.1.2 and it works fine navigating to misc. knots and watching the animation clips. 

#83

Henrik, Thanks so much for testing.   I’m not sure if I’m glad it worked for you or not.  It kind of muddies the water a bit! :slight_smile:

Brent,  the app is large at 40MB,  I can give you a url to download the apk from.   I’d rather not post it here since it is a paid app.  How do I go about emailing you the information? What email address should I use?

Thanks,

Dave

#84

No problem Dave - btw, I just upgraded to 4.2.2 without reinstalling the app, and it worked fine.

The installation process told me that it was optimizing my 88 apps. It also said it updated the Media database. Now, that worked for me without a hitch, but presumably something could have gone wrong during the updating process for the customers who have problems. But that would presumably have been righted when reinstalling the 1177 build app, which I assume is the first thing they tried. So.

Either way, the problem doesn’t seem related to Corona SDK build or OS version.

#85

Hi Dave, Ian,

If you have download links for these APK(s), please send it to me at brent [at] coronalabs [dot] com.

Thanks,

Brent

#86

Hi Dave, Ian,

We tested the APK (Knots3D) on our in-house Xperia Z running 4.2.2. There was no crash whatsoever. We ran it multiple times with power suspend, home, and exit; it all works fine. Our assumption is the crash “may happen” on startup.

So at this time, we must consider the case closed, since we can’t reproduce the crash using your actual APK on the same device with the same OS and version. Also, as you reported, there are no ANR reports coming into Google Play Developer Console. Unfortunately, I have no clear idea what is causing the crash reports from your customers… perhaps some customization/hack they did to their phones.

If I’m missing some key aspect here in the test report, please let me know a.s.a.p.

Best regards,

Brent

#87

We are getting this issue reported with both Forever Lost 1 & 2, I actually can’t remember what build# we used for them but it’s been a month or two since we released an update so it was a change a while ago. Are you able to download the game directly from Google Play or should we send you a build? Again, not sure what build# we used though.

#88

Hi Graham/Simon,

Can you send us a new build using #1137? I think this is the best way to test it… I believe you have my e-mail address.

Thanks,

Brent

#89

I hate to float the stupid question of the day.  I don’t know what all carriers carry this phone, but could we be running into a carrier specific bug?  They do like to instal their own stuff, make their own OS tweaks, and delay updates until they make sure the updates work with their own stuff.

Just because we have one to test, doesn’t mean we have the exact environment the others have.  Could we be hitting a memory limit?  It would be nice if we could learn more about the carrier’s and OS versions too.

#90

I can’t make a build right now as I’m not in the office, should be able to soon. For now this is some info from one of our users with an xperia z:

Sony Xperia Z, model no C6603

Android 4.2.2 (core version 3.4.0-g3865184) build no 10.3.1.A.0.244

Uses “Telenor N” as carrier. Norway.

If there is any more info you require please ask. I will see if anyone else can get us some info as well.

#91

Brent,

I have e-mailed you my APK. Sorry for the delay - I’ve been away for a few days.

Looks like a fair few people are having this issue but appreciate if the apps are running fine on the device for you it’s tough to work this one out.

Would you be able to test mine too?

Thanks,

Ian

#92

Hi Ian,

The APK you sent was apparently not the correct one (file size was too small for a Corona app). I e-mailed you separately about this.

Thanks,

Brent

#93

Build sent, thanks!

#94

I’ve just had another Xperia Z user with this issue.  I think that is 6 reported cases so far for Knots 3D.  I have gone back and emailed all 6 requesting additional information e.g. country, carrier, android version, exact Xperia Z model number (Xperia C6603, Xperia C6602, Xperia Z LTE, Xperia Z HSPA+).  I don’t know if I will receive any responses since all of the emails are non-English(Spanish, Italian, German and Chinese)  and there may be a language barrier to overcome, even with Google Translate.

Brent, Any update on Ian’s or Glitch Game’s apks on your Xperia Z device?

#95

Hi guys,

I submitted both .apk files to the engineers. We cannot reproduce the crash on our in-house Xperia Z… both projects run exactly as expected, and load normally.

At this point, the issue is more “muddy” than ever. The reports seem to be coming from Europe and perhaps China. Do you have any reports from U.S. or Canadian users? I wonder if this is a carrier-specific issue…

Brent

#96

Thanks for all your help with this Brent.

My users are all UK based and I’m waiting to hear on carrier.

#97

Just had another user report the issue, this is the info for their phone: The OS Version of the phone is 4.2.2 Country is Germany. Carrier : O2 Model number of the phone : c660 Chipset of the phone : Qualcomm MDM9215M / APQ8064 GPU: adreno 320

#98

Hi all,

Did anyone ever get to the bottom of this?

I’ve just had another user report it on the Google Nexus 7 but - and this is the interesting bit - only on a restricted profile he set up for his daughter.

So the app runs fine on his profile, but not on his daughter’s restricted profile, where he gets the Lua error as soon as the app launches.

My app allows the recording of audio so I’m wondering if the restricted profile blocks access to the mic and that’s what’s happening here although that wouldn’t explain any of the other instances of this… hmmmm.

Cheers,

Ian

#99

Hi all,

Did anyone ever get to the bottom of this?

I’ve just had another user report it on the Google Nexus 7 but - and this is the interesting bit - only on a restricted profile he set up for his daughter.

So the app runs fine on his profile, but not on his daughter’s restricted profile, where he gets the Lua error as soon as the app launches.

My app allows the recording of audio so I’m wondering if the restricted profile blocks access to the mic and that’s what’s happening here although that wouldn’t explain any of the other instances of this… hmmmm.

Cheers,

Ian

#100

Hi all,

This has happened again - this time another Google Nexus 7 user running our app in a restricted profile for one of their children.

The app works fine in all my tests on all devices (iOS and Android). It even works fine on  my  Google Nexus 7 when I set up a restricted profile. I have never been able to recreate this error on any device.

But - as per the rest of this thread, I have heard from several other customers who have experienced this issue in the past.

Even weirder, apparently after rebooting the device for a second time the app then worked. They’d already tried rebooting once and that hadn’t helped.

Any ideas…?

Thanks!

Ian