I think this is LiveCode engine problem. It seems to be the use of a NULL pointer, probably from an error that is not expected and never checked. For example, a request for memory might be made and a NULL is returned when none is available. A programmer might be able to prove that an error cannot occur, but the Apple test environment might generate one anyway. Report this to RunRev as Jacque suggested.
In the mean time, you can increase stresses to try to force crashes on your setup. I'm not sure how to do that. You can try very large data. If you are using http, then try opening chargen (port 19) on a system with simple services enabled. You can also try to connect to computers that do not exist or do not a listener (service) on that port of that computer. If you can make lots of connections, do that. It might be a random bug in your code related to native controls or externals. Dar On Mar 17, 2012, at 5:58 AM, Sergio Schvarstein wrote: > I've submitted an app to the AppStore and it was rejected because several > crashes were found. > > This is the Apple rejection message: > > We found that your app crashed on iPhone 4 and iPad 2 running iOS 5.1, which > is not in compliance with the App Store Review Guidelines. > Your app crashed intermittently on both Wi-Fi and cellular networks. > > They've also sent 4 crash reports, which I couldn't descifrate. > > In all my exhaustive tests in several devices and iOS versions I never found > any crash. > > Here are the 4 crash reports: > http://dl.dropbox.com/u/592829/Projects/IndexBook/crash_reports.zip > > Is there any way for knowing the crash origins ? _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
