Random Crash - Hasn't happened in months and now it does

Solar2D General Questions/Discussion
#1

Hi,

I’ve had users start to complain about a new crash recently. The app times out upon launch and it crashes. This happens even with airplane mode on. Previously, the app has never crashed for any of these users. Here’s a console log from one of them:

http://i.joeylau.me/2014/09/2014-09-16_23-30-06.txt

The very bottom of the file has the error. It’s:

libMobileGestalt copySystemVersionDictionaryValue: Could not lookup ReleaseType from system version dictionary

Why would this randomly start happening out of the blue? Players have had the app for a while with no previous issues. Is this a bug introduced in a daily build maybe?

The players say that the game will crash for a few days with this error, and then it magically starts working again (for some of them). Seems to be completely random. Happens on all iOS devices, iOS 6 and 7.

Any help would be appreciated!

#2

I doubt the libMobileGestalt error is your crash.  You’re getting killed (signal 9) before hand because the app is taking too long to start.  Signal 9 or SIGKILL is issued either by the OS or by the USER to kill the app immediately and not politely.  Since a user can’t issue a SIGKILL on an iOS device, the OS is doing it.  Your app was dead and out of memory before the libMobileGestalt error happened.

Now the real question is why did your app not launch in time?  But before I get there you asked “a bug introduced in a daily build maybe”?  Well is this user using a build you’ve made with a daily build lately?  When was the last time you published the app to the store?  What version of Corona SDK was that built with?  Corona can’t change apps already in the store.  Only you can do that by submitting a new build.

Since Airplane mode is on, then this points to some networking thing as the cause.  What plugins are you using?  Are you doing anything in your main.lua before you draw anything?  Have you done anything to disable our internal analytics? 

Rob

#3

I doubt the libMobileGestalt error is your crash.  You’re getting killed (signal 9) before hand because the app is taking too long to start.  Signal 9 or SIGKILL is issued either by the OS or by the USER to kill the app immediately and not politely.  Since a user can’t issue a SIGKILL on an iOS device, the OS is doing it.  Your app was dead and out of memory before the libMobileGestalt error happened.

Now the real question is why did your app not launch in time?  But before I get there you asked “a bug introduced in a daily build maybe”?  Well is this user using a build you’ve made with a daily build lately?  When was the last time you published the app to the store?  What version of Corona SDK was that built with?  Corona can’t change apps already in the store.  Only you can do that by submitting a new build.

Since Airplane mode is on, then this points to some networking thing as the cause.  What plugins are you using?  Are you doing anything in your main.lua before you draw anything?  Have you done anything to disable our internal analytics? 

Rob