analytics-ios: Crash in queuePayload / persistQueue
I’m not sure if this is a segment bug or an apple bug but i figured i’d put it out there and see if anyone had any ideas as to what might be happening:
Thread 12 Crashed:
0 CoreFoundation 0x0000000182e2e890 __CFTypeCollectionRetain + 40
1 CoreFoundation 0x0000000182d51b44 _CFArrayReplaceValues + 348
2 CoreFoundation 0x0000000182d6196c _CFAppendXML0 + 2360
3 CoreFoundation 0x0000000182d61a88 _CFAppendXML0 + 2644
4 CoreFoundation 0x0000000182d61a88 _CFAppendXML0 + 2644
5 CoreFoundation 0x0000000182d6131c _CFAppendXML0 + 744
6 CoreFoundation 0x0000000182d60978 _CFPropertyListCreateXMLData + 212
7 CoreFoundation 0x0000000182d6ba38 CFPropertyListCreateData + 116
8 Foundation 0x0000000183797b90 +[NSPropertyListSerialization dataWithPropertyList:format:options:error:] + 44
9 Analytics 0x00000001012f83e8 -[SEGFileStorage dataFromPlist:] (SEGFileStorage.m:149)
10 Analytics 0x00000001012f8354 -[SEGFileStorage setPlist:forKey:] (SEGFileStorage.m:140)
11 Analytics 0x00000001012f8120 -[SEGFileStorage setArray:forKey:] (SEGFileStorage.m:105)
12 Analytics 0x000000010130097c -[SEGSegmentIntegration persistQueue] (SEGSegmentIntegration.m:638)
13 Analytics 0x00000001012ff838 -[SEGSegmentIntegration queuePayload:] (SEGSegmentIntegration.m:478)
14 Analytics 0x00000001012ff69c __71-[SEGSegmentIntegration enqueueAction:dictionary:context:integrations:]_block_invoke (SEGSegmentIntegration.m:466)
15 libdispatch.dylib 0x00000001828c14bc _dispatch_call_block_and_release + 20
16 libdispatch.dylib 0x00000001828c147c _dispatch_client_callout + 12
17 libdispatch.dylib 0x00000001828cd4c0 _dispatch_queue_drain + 860
18 libdispatch.dylib 0x00000001828c4f80 _dispatch_queue_invoke + 460
19 libdispatch.dylib 0x00000001828cf390 _dispatch_root_queue_drain + 724
20 libdispatch.dylib 0x00000001828cf0b0 _dispatch_worker_thread3 + 108
21 libsystem_pthread.dylib 0x0000000182ad9470 _pthread_wqthread + 1088
22 libsystem_pthread.dylib 0x0000000182ad9020 start_wqthread + 0
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 15 (14 by maintainers)
@tonyxiao I’m fine to wait for the next major release, it isn’t affecting that many users so i’d say probably not worth a hotfix
@johnryan was planning on incorporating it into the next major release 3.6.0 beta in a few days. Wasn’t planning on patching master due to the unconfirmed nature of the fix. Do you think it’s worth hotfixing master?