You can also check with your fb and twitter friends maybe they have one
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
I too have a user reporting the same error on the Sony Xperia Z. I just recently (2 days ago) published an update to my app using build 1177 to address the text wrapping issues in Android 4.3. AFAIK, the previous version of our app was working fine using build 1137. I have asked the user for a few more details, e.g. Android version, and will add them here when I hear back.
Aha! I was starting to think I was going mad. Yes - exactly the same as me, app was working fine using a previous Corona build but we released an update using a more recent build and now the error occurs.
Corona - this must be an issue with a recent build and as the Xperia Z is a fairly popular device is there any chance of looking into this in more detail?
As with dvboren, we wanted to use the more recent build to address the text wrapping issues in Android so wouldn’t want to go back to using 1137 to get it to work as that means the text wrapping won’t work.
Thanks,
Ian
Not sure if it is relevant and I have yet to hear back from the user, but it looks like Sony started a phased rollout of Jelly Bean 4.2.2 on the Xperia Z within the past month or so.
http://blogs.sonymobile.com/2013/07/25/on-android-jelly-bean-4-3/
http://www.engadget.com/2013/06/25/sony-starts-upgrading-international-xperia-z-to-android-4-2-2/
Just had 2 more users report this. Also on Xperia Z running Android 4.2.2.
Yes I’ve had another too. Corona - is there anything you guys can do on this? It would appear to be an issue with the more recent builds.
Any ideas much appreciated.
It looks like Sony has a device loan program. Corona staff, maybe this is something you guys could look into? I think If I got one it would just crash as the users have described and I still wouldn’t know what was going on (maybe I could get something out of logCat). Hopefully you guys have more insight into this.
http://developer.sonymobile.com/services/borrow-a-phone/
According to my stats I have around 150 Xperia Z users. I really don’t want to see 150 one star reviews. Corona, Help!
Agreed - I have a lot of Sony Xperia Z users too - most of them won’t have bothered writing to me for an explanation - they’ll just be getting annoyed and thinking the app is badly made and poor reviews will no doubt follow.
I’d be happy to get a loan device but I’m in the UK and it doesn’t look like they cover anywhere outside the US. As dvboren says though - it may well not show anything anyway.
If there’s anything you guys can do that would be fantastic.
Thanks,
Ian
Hi Ian, @dvboren,
I’ve reported this to the engineers, but we need to “isolate” the issue here to determine the best approach. You said that this happens on “more recent builds”… but what about 1137 (most recent public)? Does it occur or not? Obviously, building with daily builds comes with a certain understanding of risk (and yet, I realize you’re concerned with the Android 4.3 text issue which was resolved in recent dailies).
So my understanding thus far:
-
This only occurs on XPeria Z on apps built with “recent builds”.
-
This does not occur on XPeria Z with apps built using #1137.
-
The OS causing the problem seems to be Sony’s flavor of Android 4.2.2, correct?
We’re going to need some kind of test case regardless, so we can see how you’re setting up the project config, the build settings, which kind of launch images you’re including, etc. Can one of you please compile this?
Thanks,
Brent
Update: I followed up with one of the users and provided them a previous version of our apk (Corona build 986). It works fine.
So to confirm your understanding:
-
So far this has only been reported by Xperia Z users. 3 reports for me and 3+ for Ian.
-
I re-checked my release notes and I was mistaken – our previous version for android was built with build #986. I have a different app that was on #1137 and I have had no complaints (165k downloads). I can’t be 100% sure that 1137 is ok, only that 986 is.
- The user I have been working with is on Sony Android 4.2.2. I can’t be sure it isn’t happening on earlier versions.
FWIW, I was able to install the latest available Sony Add-on in SDK Manager. Unfortunately the SDK is out of date 4.1.2 (API 16). When tested with Sony 4.1.2 add-ons in the emulator, our app worked fine – no errors in logcat. Not sure when Sony will provide an update for their Add-on SDK to bring it up to 4.2.2 and I’m not sure the problem would happen in the emulator anyway.
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.
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
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.
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! 
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
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.
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
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
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.
Hi everyone,
Just wondering if there has been any update on this at all?
I still haven’t managed to get hold of an Xperia Z device.
Brett - have you guys had a chance to look into this at all?
Happy to send you some code - how would you like to receive it? I can e-mail a zip file over?
Cheers,
Ian