My iOS app uses AFNetworking (2.6.1), and my highest ranking crash is :
Crashed: com.apple.NSURLSession-work
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0004000128ab38a0
This is how most stack traces look like in Crashlytics:
Thread : Crashed: com.apple.NSURLSession-work
0 libobjc.A.dylib 0x180e29bc8 objc_msgSend + 8
1 CFNetwork 0x181df6518 SessionConnectionLoadable::_loaderClientEvent_DidReceiveConnectionCacheKey(HTTPConnectionCacheKey*) + 56
2 CFNetwork 0x181e75178 ___ZN19URLConnectionLoader36protocolDidReceiveConnectionCacheKeyEP22HTTPConnectionCacheKey_block_invoke + 40
3 libdispatch.dylib 0x1811fd630 _dispatch_call_block_and_release + 24
4 libdispatch.dylib 0x1811fd5f0 _dispatch_client_callout + 16
5 libdispatch.dylib 0x181209634 _dispatch_queue_drain + 864
6 libdispatch.dylib 0x1812010f4 _dispatch_queue_invoke + 464
7 libdispatch.dylib 0x18120b504 _dispatch_root_queue_drain + 728
8 libdispatch.dylib 0x18120b224 _dispatch_worker_thread3 + 112
9 libsystem_pthread.dylib 0x181411470 _pthread_wqthread + 1092
10 libsystem_pthread.dylib 0x181411020 start_wqthread + 4
I don't use kvo, and my app uses location and stays in the background at all times.
Any ideas on how to debug / recreate (I can't manage to recreate the issue in a simulator or on a device) ?
Even catching the exception, without knowing where it is or how to handle it correctly would suffice in this case...
Related
After new iOS release in our app become crashing with PHCompositeMediaResult. What I see in Crashlytics.
[PHCompositeMediaResult isPlaceholder]
[PHCompositeMediaResult isDegraded]
[PHCompositeMediaResult isCancelled]
Any idea what can we do with this?
Edit
Stacktrace:
Crashed: com.apple.photos.imageManagerCache
0 libobjc.A.dylib 0x1b12b8190 objc_msgSend + 16
1 CoreFoundation 0x1b146ec04 -[__NSDictionaryM objectForKeyedSubscript:] + 180
2 Photos 0x1bc7f385c -[PHCompositeMediaResult isPlaceholder] + 36
3 Photos 0x1bc84b978 -[PHCachingImageManager _canPopulateCacheForResult:] + 56
4 Photos 0x1bc84e588 __90-[PHCachingImageManager additionalWorkForImageRequestCompletedWithResult:request:context:]_block_invoke + 64
5 libdispatch.dylib 0x1b1260658 _dispatch_call_block_and_release + 24
6 libdispatch.dylib 0x1b12611cc _dispatch_client_callout + 16
7 libdispatch.dylib 0x1b120d524 _dispatch_lane_serial_drain$VARIANT$mp + 608
8 libdispatch.dylib 0x1b120df18 _dispatch_lane_invoke$VARIANT$mp + 420
9 libdispatch.dylib 0x1b1217400 _dispatch_workloop_worker_thread + 588
10 libsystem_pthread.dylib 0x1b12b0fa8 _pthread_wqthread + 276
11 libsystem_pthread.dylib 0x1b12b3ae4 start_wqthread + 8
This appears to just happen in iOS 13.0.0. I don't have any instances of it happening on 13.1, 13.1.1, or 13.1.2... So it was probably a bug in the OS that they quickly figured out and fixed. Hopefully not many users stay on 13.0.0 for long. Maybe the "what to do about this?" answer is just to do nothing.
Crashed: com.IPTV.TVLService.GuideProgramService
0 libobjc.A.dylib 0x182a05b90 objc_msgSend + 16
1 CoreFoundation 0x18326f654 CFBasicHashCreateCopy + 668
2 CoreFoundation 0x183291248 CFDictionaryCreateCopy + 148
3 CFNetwork 0x18396fa70 URLResponse::createArchiveList(__CFAllocator const*, long*, void const***, long*) + 228
4 CFNetwork 0x18396f764 URLResponse::copyPropertyList(__CFAllocator const*) + 68
5 CFNetwork 0x1839c1610 ___ZN12__CFURLCache23CreateAndStoreCacheNodeEP16__CFURLCacheNodePK20_CFCachedURLResponsePK10__CFStringPK13_CFURLRequestPKvbRb_block_invoke + 796
6 libdispatch.dylib 0x182dd94bc _dispatch_call_block_and_release + 24
7 libdispatch.dylib 0x182dd947c _dispatch_client_callout + 16
8 libdispatch.dylib 0x182de54c0 _dispatch_queue_drain + 864
9 libdispatch.dylib 0x182ddcf80 _dispatch_queue_invoke + 464
10 libdispatch.dylib 0x182de7390 _dispatch_root_queue_drain + 728
11 libdispatch.dylib 0x182de70b0 _dispatch_worker_thread3 + 112
12 libsystem_pthread.dylib 0x182ff1470 _pthread_wqthread + 1092
13 libsystem_pthread.dylib 0x182ff1020 start_wqthread + 4
I am new to iOS development.
How to understand what's causing issue? Please help me with any document or book that help me to learn solving this issues for future.
It seems like your app crashed in thread com.IPTV.TVLService.GuideProgramService and whether this thread is a custom thread or not?
Are you develop on tvOS?
There is something you should offer to make your question clear.
Thanks in advance if anybody can resolve my problem.
I am using NSURLSession API for network calls.
App is crashing on iOS9+ version.
See below crash thread:
Crashed: com.apple.NSURLSession-work 0 libobjc.A.dylib
0x1812f5b88 objc_msgSend + 8 1 CFNetwork
0x1822d6d4c + 56 2 CFNetwork
0x18235b718 + 40 3 libdispatch.dylib
0x1816c94bc + 24 4 libdispatch.dylib
0x1816c947c + 16 5 libdispatch.dylib
0x1816d54c0 + 864 6 libdispatch.dylib
0x1816ccf80 + 464 7 libdispatch.dylib
0x1816d7390 + 728 8 libdispatch.dylib
0x1816d70b0 + 112 9 libsystem_pthread.dylib
0x1818e1470 _pthread_wqthread + 1092 10 libsystem_pthread.dylib
0x1818e1020 start_wqthread + 4
I am getting the below error for swift app i made for IOS. I had setup notification using this example. How do I debug this and know what the issue is?
Crashed: com.apple.UNSNotificationRegistrarConnection
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000013000001328
Crashed: com.apple.UNSNotificationRegistrarConnection
0 libobjc.A.dylib 0x180cf9b9c objc_msgSend + 28
1 UserNotificationServices 0x183038b54 __destroy_helper_block_27 + 40
2 libsystem_blocks.dylib 0x1811298e8 _Block_release + 156
3 libdispatch.dylib 0x1810cd47c _dispatch_client_callout + 16
4 libdispatch.dylib 0x1810d94c0 _dispatch_queue_drain + 864
5 libdispatch.dylib 0x1810d0f80 _dispatch_queue_invoke + 464
6 libdispatch.dylib 0x1810cd47c _dispatch_client_callout + 16
7 libdispatch.dylib 0x1810db914 _dispatch_root_queue_drain + 2140
8 libdispatch.dylib 0x1810db0b0 _dispatch_worker_thread3 + 112
9 libsystem_pthread.dylib 0x1812e5470 _pthread_wqthread + 1092
10 libsystem_pthread.dylib 0x1812e5020 start_wqthread + 4
I am getting a crash report from my app in production. The stack trace doesn't include any of my code, rather points to code in RestKit itself where it is crashing. The crash itself is hard to reproduce on my side, and seems like some user in production is hitting an edge case. Below is the stack trace:
Thread : Crashed: NSManagedObjectContext 0x1743ecd00
0 libobjc.A.dylib 0x000000019361c0b4 objc_retain + 20
1 MyApp 0x00000001001e64c4 __78-[RKManagedObjectRequestOperation obtainPermanentObjectIDsForInsertedObjects:]_block_invoke (RKManagedObjectRequestOperation.m:873)
2 CoreData 0x0000000181b7d218 developerSubmittedBlockToNSManagedObjectContextPerform + 200
3 libdispatch.dylib 0x0000000193c55954 _dispatch_client_callout + 16
4 libdispatch.dylib 0x0000000193c5f1e4 _dispatch_barrier_sync_f_invoke + 76
5 CoreData 0x0000000181b7d0d8 -[NSManagedObjectContext performBlockAndWait:] + 244
6 MyApp 0x00000001001e62d8 -[RKManagedObjectRequestOperation obtainPermanentObjectIDsForInsertedObjects:] (RKManagedObjectRequestOperation.m:870)
7 MyApp 0x00000001001e34e4 __79-[RKManagedObjectRequestOperation performMappingOnResponseWithCompletionBlock:]_block_invoke345 (RKManagedObjectRequestOperation.m:643)
8 MyApp 0x000000010021c31c -[RKResponseMapperOperation willFinish] (RKResponseMapperOperation.m:317)
9 MyApp 0x000000010021c980 -[RKResponseMapperOperation main] (RKResponseMapperOperation.m:404)
10 Foundation 0x0000000182c601cc -[__NSOperationInternal _start:] + 636
11 Foundation 0x0000000182d21f28 __NSOQSchedule_f + 228
12 libdispatch.dylib 0x0000000193c55954 _dispatch_client_callout + 16
13 libdispatch.dylib 0x0000000193c600a4 _dispatch_queue_drain + 1448
14 libdispatch.dylib 0x0000000193c58a5c _dispatch_queue_invoke + 132
15 libdispatch.dylib 0x0000000193c62318 _dispatch_root_queue_drain + 720
16 libdispatch.dylib 0x0000000193c63c4c _dispatch_worker_thread3 + 108
17 libsystem_pthread.dylib 0x0000000193e3522c _pthread_wqthread + 816
18 libsystem_pthread.dylib 0x0000000193e34ef0 start_wqthread + 4
The crash message itself is:
Crashed: NSManagedObjectContext 0x17198900
EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x915da43f
Any hints/directions as to how I can go about debugging this issue?
Thanks.
Ran into this, had setup the core data stack twice on accident, removing the second initialization fixed the issue.