Skip to content

September 22 2026 Connect Module 2.1.33

Choose a tag to compare

@connect-sdk connect-sdk released this 22 Sep 11:45
· 57 commits to main since this release
Connect Release
Note (2.1.0): Tealeaf and EOCore are no longer published as standalone frameworks.
They are now bundled inside the Connect distribution (CocoaPods and SPM). Clients
who have an explicit separate dependency on pod 'Tealeaf', pod 'EOCore', or the
standalone Tealeaf/EOCore SPM packages must remove those separate dependencies —
the Connect dependency already includes both.

import Tealeaf, import EOCore, and all TLF* / EOCA* APIs remain available
through the Connect dependency unchanged.

Features:
- Tealeaf and EOCore consolidated into a single Connect.xcframework artifact simplifying SDK integration
- ConnectPush: added `requestAuthorization()` to request push notification permission at runtime (CA-144303)
- ConnectPush: added `getCurrentAuthorization()` to query current push authorization status (CA-144303)

Bug Fixes:
- Fixed crash in ConnectDelegateProxy replacement mode on iOS 17+ when AppDelegate implements scene lifecycle methods.
- Fixed React Native layout handling in native SDK.
- Fixed session replay capturing an almost-empty control tree for React Native `<Modal>` screens. A screen presented outside the react-native-screens navigator — a core RN `<Modal>`, or any app not using react-native-screens — resolved its layout capture root to a childless leaf view, so the screenshot looked correct but virtually nothing was inspectable in replay (CA-152632).
- Fixed automatic push mode silently dropping APNs device token when host AppDelegate does not pre-declare the APNs registration selectors (affects React Native bare workflow, Cordova). ConnectDelegateProxy now swizzles UIApplication.setDelegate: at +load time to inject forwarding-stub APNs methods before UIKit caches the delegate's optional-selector bitmask.
- Fixed masking never being applied to the captured accessibility object. An element's accessibility label and hint were serialised verbatim even when its value was masked, so text the mask lists were configured to redact could still reach the collector in `accessibility.label`. The accessibility mask lists could not cover this themselves: `MaskAccessibilityIdList` and `MaskAccessibilityLabelList` select which elements are masked, and the redaction lands on the value. This affected React Native most, where a `<Text>` node's accessibility label defaults to its own content, so it applied to any masked text without an explicit label. The label and hint are now masked by the same decision that masks the value (CA-157176).
- Fixed duplicate and missing screen views on React Native nested stacks. Leaving a tab backed by a nested `createNativeStackNavigator` fired `viewDidAppear` three times ~1ms apart for the same react-native-screens screen, emitting a duplicate VISIT each time; separately, a push or pop *within* a nested stack produced no VISIT or UNLOAD screenview at all in either direction, so those navigations were missing from replay entirely (CA-157703).
- Fixed the screenview `referrer` self-referencing the current screen on React Native apps using a wrapped navigation container. Every type-2 screenview named the incoming screen as its own referrer instead of the previous screen, collapsing session replay into a single step. The React Native bridge advances the current screen name before the native view controller lifecycle captures the previous one; the capture now happens before the overwrite. Android was unaffected (CA-155041).
- Fixed `logSignal` payload fields being wrapped in a `signal.data.value` envelope that the Connect behavior signals pipeline does not understand, so caller-supplied values did not arrive as expected. Values are now placed directly under `signal`, matching the format identity messages already use. The public `logSignal` signature is unchanged (CA-148864).
- Fixed `Connect.enable()` not restoring event delivery after `Connect.disable()`. Disabling a module stopped the shared EOCore queue service, but EOCore itself stayed enabled, so re-enabling short-circuited past the branch that restarts that service. The SDK reported itself enabled, started a new session, passed the kill switch and accepted events, while the flush timer and server connection stayed torn down and nothing was posted to the collector for the rest of the session. Apps that toggle capture around screens showing personal data lost all analytics from their first disable/enable cycle onward (CA-158635).
- Fixed a crash when capture was disabled while an event post was in flight. `EOQueueService` cleared its server connection on disable while the interval flush could be part-way through posting on its own queue, releasing the connection under the running call and faulting on the next message send. Apps that toggle capture around screens showing personal data were most exposed, since a disable can land at any point in the flush interval. The connection is now retained for the duration of a post, and the cached-queue list is locked on every path rather than only the asynchronous one (CA-158635).
- Fixed every synchronous flush replaying the whole persisted backlog of previously failed posts on the calling thread. `logFatalErrorEvent`, `logPreconditionErrorEvent`, `logAssertionFailureErrorEvent` and `logPreconditionFailureErrorEvent` flush synchronously on the caller's thread, and each such flush recovered every queue that an earlier post had failed to deliver, so the work grew with the backlog and could stall the app on a slow or unreachable collector. Recovery of the persisted backlog is now left to the interval-driven flush (CA-158635).
- Fixed gesture analytics being dropped or duplicated when a tapped control's `cssId` serialized as `NSNull`. The position-based de-duplication logic treated `NSNull` as a valid string, threw, and was silently skipped. A related unguarded chained lookup of the gesture's control type could also throw uncaught on malformed gesture data and crash the process (CA-151560).

Improvements:
- None

Our environment for this release:

- Xcode 26.2
- MacOS 26.1
- iOS 15.1 to 26.2
- Supported architectures:
	- simulator
		- arm64
		- x86_64
	- device
		- arm64

Known Issues:

- Captures gesture even when the gestureRecognizer is set to return 'NO', this is an Apple defect.
- After iOS 13, library no longer supports iPad because of Apple changes in iPad OS.
- The pink border on Gestures screenview is off when captured using ER, because of timing or garbage collection.
- Template issue - The back link is missing during capture on some screens ProgressIndicator, AlertViewController, Gestures screenview and picker view.
- Template issue - Battery icon not visible in green anymore.
- Improvement :- 'connectionType' remains N/A if device is on WiFi on app start.
- DoPostOnScreenChange is not working as expected, because of temp queue.
- Reporting of multiple carrier names in JSON if the device has Dual SIM is a beta feature.
- React Native has an issue for dynamic builds. We will use static version instead.
- Certain Alerts may appear correctly during replay.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels
- iPadOS Multi Window apps are not YET supported.