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

Solar2D General Questions/Discussion
#61

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

#62

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.

#63

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.

#64

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

#65

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

#66

Build sent, thanks!

#67

Hi Ian, @dvboren,

I have an update for you (although not ideal). We’re going to test this, but we need to obtain one of these phones. That will take some time, then we need to schedule it in for testing. So, this isn’t likely to happen in the immediate future (as in, not this week or anything).

At this point, we also need to confirm that the issue isn’t being caused by something specific to your apps. Although it may not seem likely, sometimes the weirdest, seemingly unrelated thing will cause an app to crash. For example, people are reporting XPeria devices crashing if the Thai language is enabled on their phones: http://talk.sonymobile.com/thread/124269?start=60&tstart=0. So, we need to test some basic Corona-built projects on this phone (like “Hello World”), but of course, we don’t yet have the phone… chicken and egg problem here.

In the meantime, the engineers are advising that you temporarily turn off support for the Xperia Z in Google Play. I know this isn’t the final resolution, but at least it would help prevent bad reviews from users until we can investigate this.

Best regards,

Brent

#68

Thanks Brent - good to know you’ll be looking into it. I am trying to get hold of one of these devices myself still but as yet nobody I know has got back to me to say they own one and shelling out several hundred pounds / dollars every time a different Android issue occurs just isn’t an option for most of us.

If I can get hold of one and I get any feedback I’ll obviously post here but otherwise I look forward to hearing back from you. Will remove that device in Google Play for the moment as suggested. I reckon 90% of my support time is spent messing around with different Android devices and I imagine the same goes for you guys. If only everything were as simple as iOS!

Thanks,

Ian

#69

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?

#70

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

#71

Thanks for all your help with this Brent.

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

#72

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

#73

Thanks Brent.  Another user today with Xperia ZL (same processor as the Z so I guess that was to be expected).

I did turn off support for Xperia Z in Google Play and for existing users I am providing a link to those who contact our support so they can sideload the previous working version of our app.

Any progress on securing an actual device to test on?

#74

Be happy to test on mine, amount of info back depends on how easy it is to set up logging. :slight_smile: (I already have logging working in Eclipse though, will it appear there?)

Note that the Sony phones come with the Sony-modified Android OS on it. The most major difference is the app switcher in the lower right corner.

Mine is AOS 4.1.2 (the version it shipped with).

#75

Hi all,

To speed up this process, we just ordered an Xperia Z outright. I’m not sure when we’ll get to the actual testing after the device arrives.

In the meantime, you should request the crash report from Google Play. It may provide clues as to what went wrong. Something like a Java exception stack trace. Please do this so we can have something more to base the tests off, when the device arrives.

Thanks,

Brent

#76

Hi Brent,

When you say “request the crash report from google play” do you mean something different than the “Crashes & ANRs” reports in the Google Play developer console?  If we are talking about Crashes & ANRs, I have none at all for the current release(corona build 1177) of our app so no clues there. 

-Dave

#77

Hi Dave,

You’re in the correct place (Crashes & ANRs). If the app was purchased from Google Play, then the Android device is supposed to send a crash report to the Google Play Developer Console. If nothing is getting reported, then perhaps the app is not really crashing? Or perhaps Google Play no longer thinks the app was purchased from the store (failed validation)?

Brent

#78

I too am seeing no crash reports in Google for these devices but have had reports from users that this is happening. To be fair I get virtually no crash reports in Google for any of my apps but have received e-mails from customers in the past on various issues with Android so I’m not sure how well Google’s crash reporting actually works.

Thanks for ordering a device - be interested to see what it turns up.

#79

Hi Dave, Ian,

We received the “Xperia Z” and tested two of our sample apps (“ActivityIndicator” and “Bullet”). Both of them work normally, both before and after an OS update (no crashes whatsoever).

At this point, about all we can do is request that you compile a basic, easy-to-reproduce test case and submit it to us. We can check if this functions on our XPeria Z or not.

Thanks,

Brent

#80

Hi Brent - thanks for this. Okay - well according to my customers the app crashes as soon as the icon is tapped so the most realistic test case I can submit is simply to send you the most recent APK for the app. How would you prefer to receive this? Should I do it via the “report a bug” section of the site? Thanks, Ian.