Game that I'm working on recently went from iPad-Only to Universal iOS and this error started appearing ALOT via Flurry Crash Reports (haven't had any reports yet through itunesconnect).
[NSURLConnection][1] is for loading the contents of a URL but I've no idea why it would be doing this so much suddenly :( Can anyone else shed any more light on what the crash report says?
Hardware Model: iPhone4,1
Process: gamename [3530]
Path: /var/mobile/Applications/324961FD-D913-49F2-AA00/gamename.app/gamename
Identifier: com.gamename
Version: 1.2
Code Type: ARM
Parent Process: launchd [1]
Exception Type: SIGSEGV
Exception Codes: SEGV_ACCERR at 0x0
Crashed Thread: 0
Thread 0 Crashed:
0 gamename 0x001a427c __mh_execute_header + 1671804
1 gamename 0x00f3133c +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2323000
2 gamename 0x00f319b0 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2324652
3 gamename 0x00f42134 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2392112
4 gamename 0x00f42218 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2392340
5 gamename 0x01155dbc +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 4570296
6 gamename 0x007b9718 __mh_execute_header + 8050456
7 gamename 0x001d0bfc __mh_execute_header + 1854460
8 gamename 0x001d1ebc __mh_execute_header + 1859260
9 gamename 0x00e92790 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 1672844
10 gamename 0x00f3e230 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2375980
11 gamename 0x00f3e1ec +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2375912
12 gamename 0x00f30ad4 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2320848
13 gamename 0x00f30aec +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2320872
14 gamename 0x00e7becc +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 1580488
15 gamename 0x00e7c298 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 1581460
16 gamename 0x00f03010 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 2133772
17 gamename 0x00cff288 +[NSURLConnection customSendAsynchronousRequest:queue:completionHandler:] + 20868
18 gamename 0x00cbdee8 -[UnityAppController repaint] + 212
19 gamename 0x00cbddb8 -[UnityAppController repaintDisplayLink] + 56
20 QuartzCore 0x32b2ddf3 + 98
21 QuartzCore 0x32b2db9d + 344
22 IOMobileFramebuffer 0x358fa75d + 104
23 IOKit 0x31330451 _IODispatchCalloutFromCFMessage + 248
24 CoreFoundation 0x30605ef9 + 136
25 CoreFoundation 0x30610ab7 + 34
26 CoreFoundation 0x30610a53 + 346
27 CoreFoundation 0x3060f227 + 1398
28 CoreFoundation 0x30579f4f _CFRunLoopRunSpecific + 522
29 CoreFoundation 0x30579d33 _CFRunLoopRunInMode + 106
30 GraphicsServices 0x354d2663 _GSEventRunModal + 138
31 UIKit 0x32ec516d _UIApplicationMain + 1136
32 gamename 0x00010c20 __mh_execute_header + 19488
33 libdyld.dylib 0x3b3c9ab7 + 2
Update: It appears after looking around a fair bit and what the game is actually doing that this is the FlurrySDK, going to update that and see if it stops...
[1]: https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSURLConnection_Class/index.html
↧