segmentio
Crash on iOS 16
This is reported on Crashlytics on iOS 16 for 1 user and for the first time. Xcode 13.4.1 build Not sure what makes it
Crashed: com.segment.state.queue EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0014911bad2c1df2
Crashed: com.segment.state.queue 0 libobjc.A.dylib 0x3510 objc_release + 8 1 libobjc.A.dylib 0x3510 objc_release_x0 + 8 2 libswiftCore.dylib 0x3cb334 swift_arrayDestroy + 124 3 libswiftCore.dylib 0x241bd0 __SwiftDeferredNSArray.withUnsafeBufferOfObjects<A>(_:) + 128 4 libswiftCore.dylib 0x240b90 @objc __SwiftNativeNSArrayWithContiguousStorage.countByEnumerating(with:objects:count:) + 184 5 Segment 0x1ac00 -[NSArray(SerializableDeepCopy) serializableDeepCopy:] + 164 6 Segment 0x1a9d0 -[NSDictionary(SerializableDeepCopy) serializableDeepCopy:] + 400 7 Segment 0x15ebc __25-[SEGUserInfo setTraits:]_block_invoke + 32 8 libdispatch.dylib 0x24b4 _dispatch_call_block_and_release + 32 9 libdispatch.dylib 0x3fdc _dispatch_client_callout + 20 10 libdispatch.dylib 0x14994 _dispatch_lane_concurrent_drain + 996 11 libdispatch.dylib 0xc250 _dispatch_lane_invoke + 496 12 libdispatch.dylib 0x6fa8 _dispatch_queue_override_invoke + 500 13 libdispatch.dylib 0x15a6c _dispatch_root_queue_drain + 396 14 libdispatch.dylib 0x16284 _dispatch_worker_thread2 + 164 15 libsystem_pthread.dylib 0xdbc _pthread_wqthread + 228 16 libsystem_pthread.dylib 0xb98 start_wqthread + 8
We've also started seeing this issue popup a lot more frequently. Also iOS16 only.
Getting the same error on our end. Also iOS 16 only
Did you find any solution ?
One thing to note, we're on the verge of deprecating Analytics-iOS and Analytics-Android in favor of Analytics-Swift and Analytics-Kotlin. Might be worth it to investigate upgrading in the meantime.
https://github.com/segmentio/analytics-swift
One thing to note, we're on the verge of deprecating Analytics-iOS and Analytics-Android in favor of Analytics-Swift and Analytics-Kotlin. Might be worth it to investigate upgrading in the meantime.
https://github.com/segmentio/analytics-swift
Thanks for looking into this. As this is happening in the production build and our release is pending due to this issue. We are looking for a quick fix for the ios 16 build. Also, we are on to migration to Analytics-Swift.