We’re seeing occasional fatal crashes in production that symbolicated to SunCoFayeClient.connect inside ZendeskSDKMessaging (Sunshine / Faye layer), not our app code — e.g. SunCoFayeClient.swift ~line 155, with thunk for closure, objc_destructInstance / swift_deallocClassInstance, and work on a background queue (EXC_BAD_ACCESS / bad pointer).
Setup: Native iOS app, ZendeskSDKMessaging 2.37.0 (update if we’ve bumped), initialize Messaging after login with channel key + JWT (initialize, loginUser, event observers). Crashes correlate with iOS 26.x (e.g. 26.3.x) on recent iPhones.
We’ve already tried main-thread dispatch for app state updates from SDK callbacks, weak captures in observers, and serializing init, but stacks still point at SunCoFayeClient.connect.
Questions for Zendesk / the community:
- Is this a known issue with a fix in a specific SDK version or release notes we should read?
- Any recommended patterns for iOS 26 (init/teardown order, avoiding overlapping
connect, threading)? - Are others seeing the same stack — if so, what worked for you (SDK bump, workaround, support ticket)?
