Release notes for Connect SDKs
This page has release notes for every Connect SDK: web, native mobile (Android and iOS) and hybrid mobile (Flutter, React Native, Cordova and Capacitor). Choose a platform to see its releases, newest first.
iOS
System compatibility
- Native OS: iOS 15.1–26.5
- Development tools: Xcode 26; Swift/SwiftUI and Objective-C
Oct 27, 2026 · 2.2.15
This release records taps that weren't recorded before, masks text field placeholders, and publishes new CocoaPods versions to Acoustic's spec repo. It also includes all changes from 2.2.2.
Bug fixes
- Fixed text field placeholders being sent unmasked in screen layouts (type 10). A field's
currState.placeholderwas sent as typed in the app even when it matchedMaskValueListor the field itself was masked, so a placeholder holding an email address or a sample card number reached the collector in clear. The placeholder is now masked by the rules that mask the field's text: a masked field, including a secure-entry field, masks its placeholder too, and a placeholder that matchesMaskValueListis masked on its own. - Fixed taps that weren't recorded. SwiftUI draws its controls without a
UIView, so SwiftUI button taps landed on the hosting container and were dropped. A tap on a SwiftUI view marked withconnectIdentifier(_:)now sends a click and a tap gesture with that identifier. Taps on SwiftUI views without one still send nothing. Taps on UIKit controls whose only handlers areUIActions, such asUIButton(primaryAction:), and on iOS 26 tab bar items now send a tap gesture targeting the control, as a target-action button does. Expect more taps and clicks than before. - Fixed SwiftUI screens pushed with
NavigationLinkand named fromonAppearwithsetCurrentScreen(pageName:)sending their screen view under their hosting controller's class name (_TtGC7SwiftUI19UIHostingController…), while the name renamed the screen being left. Each pushed screen's screen view now carries its own name, with the previous screen as referrer. This affected 2.2.2 and later.
Improvements
-
New CocoaPods source. New versions of
AcousticConnectandAcousticConnectDebugare published to Acoustic's spec repo, https://github.com/go-acoustic/PodSpecs. CocoaPods trunk becomes read-only on 2 December 2026 and won't receive later versions. If you use CocoaPods, add these lines at the top of your Podfile:source 'https://github.com/go-acoustic/PodSpecs.git' source 'https://cdn.cocoapods.org/'Existing installs keep working without the change but stop receiving updates. Swift Package Manager (https://github.com/go-acoustic/Connect-SP) is still the recommended integration and isn't affected.
Our environment for this release
- Xcode 26.6
- macOS 26.6.2
- iOS 15.1 to 26.5
- Supported architectures: arm64 and x86_64 on the simulator, arm64 on devices
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens: Progressindicator, AlertViewController, Gestures screenview, and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Oct 6, 2026 · 2.2.2
This release changes what some apps send to the collector, adds SwiftUI view modifiers that identify controls in replay, and fixes screen naming, disable and alert capture issues.
Breaking changes
These changes affect what some apps send to the collector. Review them before you upgrade.
- Screen names from
setCurrentScreen(pageName:). The name now arrives as the current screen'sname. Previously it arrived as the screen view'sreferrer. It names the screen that's appearing or on display, never the next one, so naming a screen in a button handler before presenting it now renames the screen being left. Name each screen from its ownviewWillAppear,viewDidAppearoronAppear. - More layouts with
NumberOfWebViews. Apps that setNumberOfWebViewsinGlobalScreenSettingsnow receive screen layouts for screens without a WebView, which increases message volume. - More screens captured. View controllers declared
private,fileprivate, nested, local or generic in Swift, and SwiftUI sheets and full-screen covers, now send screen views and layouts. Previously they sent none. UNLOADnames. EachUNLOADscreen view now names the screen being left, not the screen being entered.- Alerts. While an alert is on screen with screenshots on, the current screen is no longer sent again about every 0.6 seconds. On React Native, an alert now sends an
UNLOADof the screen and an alertLOAD, like a native alert. - Default capture delay. Apps that don't ship their own
ConnectLayoutConfig.jsonnow capture layouts and screenshots 500 ms after a screen change instead of 1 ms. - Overlay windows. A window raised above your app's content whose root is a plain
UIViewController, such as React Native's Metro loading banner in debug builds, no longer sends screen views or layouts.
New features
- SwiftUI control identifiers. Use the
connectIdentifier(_:)andconnectCapture(identifier:)view modifiers to carry an identifier into layout capture, so replay can identify SwiftUI controls. SwiftUI draws its controls without a backingUIView, so.accessibilityIdentifier(_:)alone never reached the captured layout.connectIdentifier(_:)also sets the view's accessibility identifier;connectCapture(identifier:)leaves that to you.
Bug fixes
- Fixed
Connect.disable()not stopping capture. Screen views, screen layouts, custom events and gestures were still recorded while the SDK reported itself disabled, then sent with the nextenable(), so data from consent and privacy flows that turned capture off still reached the collector. Nothing is recorded betweendisable()and the nextenable()now. A kill switch check still running whendisable()was called could also restart capture, turn it off, or replace the new session's ID; results of checks started beforedisable()are now ignored. Events captured beforedisable()are still sent once capture resumes, and events the kill switch hadn't approved yet are discarded. - Fixed each disable and enable cycle adding another app-became-active observer, which logged an extra client state message per cycle every time the app returned to the foreground.
- Fixed screen layouts (type 10) never being captured for screens without a WebView when
NumberOfWebViewsis set inGlobalScreenSettings. Screen views kept arriving, so replay looked broken. The setting now delays layouts only on screens that contain a WebView. To turn off layout capture, useCaptureLayoutOn. A globalCaptureLayoutOn: 0now logs one console line at startup naming the setting. - Fixed your app's own
webView(_:didFinish:)(WKNavigationDelegate) andtableView(_:didSelectRowAt:)(UITableViewDelegate) never being called when the delegate's class inherits the method from a superclass. The same happened to a subclass of a delegate class the SDK had already set up. Both now reach your implementation once. - Fixed the name passed to
setCurrentScreen(pageName:)arriving as the screen view'sreferrerwhile itsnamestayed the view controller's class. It's now thenameof the current screen view, with the previous screen asreferrer, and it also names that screen's layout and itsUNLOAD. Calling it fromviewWillAppearor SwiftUI'sonAppearnames the screen as it's logged. Calling it fromviewDidAppearrenames the screen view just logged, so one screen view is sent, under the page name. Calling it again with the same name changes nothing. React Native apps without a wrapped navigation container get the same fix. - Fixed SwiftUI apps getting class names such as
_TtGC7SwiftUI19UIHostingController…for pushed and presented screens named withsetCurrentScreen(pageName:)fromonAppear. SwiftUI screens also never sent anUNLOADscreen view. Both now use the page name. Screens you don't name keep their class-based name. - Fixed view controllers declared
private,fileprivate, nested, local or generic in Swift sending no screen view and no layout. SwiftUI.sheetand.fullScreenCovercontent was also missed. Both are captured now. Your app's own Swift classes are named by their Swift type name, for exampleReplayModalViewController. Other screen names are unchanged. - Fixed focusing a text field on iOS 26 being recorded as a screen (
UITrackingElementWindowController). It ended the real screen early, so the next layout was filed under the wrong name. - Fixed each
UNLOADscreen view being named after the screen being entered instead of the screen being left. A view controller that never sent aLOADno longer sends anUNLOAD. - Fixed the next screen view naming a closed modal as its
referrerwhen the presenting screen stayed visible: UIKit.overFullScreen,.overCurrentContext,.pageSheetand.formSheet(including React Native's<Modal transparent>), and SwiftUI.sheetand.fullScreenCover. The referrer is now the presenting screen, and no screen view is sent for the return itself. - Fixed
logScreenLayout…sending an extraLOADscreen view, with itself as referrer, for the screen already on display. Capturing that screen again now adds a layout only. A different name, or a screen that isn't on display, still sends aLOAD. - Fixed a synchronous flush blocking the calling thread for the post timeout plus 2 seconds (302 seconds with the default configuration) when two or more queues were waiting to be sent.
logFatalErrorEvent,logPreconditionErrorEvent,logAssertionFailureErrorEventandlogPreconditionFailureErrorEventflush synchronously on the caller's thread. - Fixed the current screen being sent again about every 0.6 seconds while an alert was on screen and screenshots were on. Alerts are also now recognized when they're a
UIAlertControllersubclass, such as React Native'sRCTAlertController. On React Native, the view controller that hosts an alert in its own window is no longer logged as a screen, and the alert is handled like a native alert: anUNLOADof the screen, then an alertLOADwhile it's shown. - Fixed overlay windows being logged as screens. A window above your app's content whose root is a plain
UIViewController, such as the Metro loading banner in React Native debug builds, no longer sends screen views or layouts. Your app's own view controller subclasses, and plain controllers in windows at the normal level, are logged as before.
Improvements
- Default layout capture delay. The SDK's default
CaptureLayoutDelayis now 500 ms instead of 1 ms, matching Android and the default already used when a configuration omits the key. Apps that don't ship their ownConnectLayoutConfig.json(includingConnectConfig.Layout.basicAnalytics) now capture layouts and screenshots 500 ms after a screen change. A delay set in your own configuration is unchanged.
Our environment for this release
- Xcode 26.6
- macOS 26.6.2
- iOS 15.1 to 26.5
- Supported architectures: arm64 and x86_64 on the simulator, arm64 on devices
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens: Progressindicator, AlertViewController, Gestures screenview, and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Sep 22, 2026 · 2.1.33
Bug fixes
- Fixed
Connect.enable()not restoring event delivery afterConnect.disable(). The SDK reported itself as enabled, started a new session and accepted events, but sent nothing to the collector for the rest of the session. Apps that pause capture on screens showing personal data lost all analytics after the first time they disabled and re-enabled capture. - Fixed a crash when capture was disabled while an upload was in progress. Apps that pause capture around sensitive screens were most exposed.
- Fixed synchronous flushes resending the entire backlog of earlier failed uploads on the calling thread.
logFatalErrorEvent,logPreconditionErrorEvent,logAssertionFailureErrorEventandlogPreconditionFailureErrorEventflush synchronously, and each one could stall the app when the collector was slow or unreachable. The backlog is now sent only by the regular interval flush.
Our environment for this release
- Xcode 26.2
- macOS 26.1
- iOS 15.1 to 26.2
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens: Progressindicator, AlertViewController, Gestures screenview, and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Sep 15, 2026 · 2.1.26
Bug fixes
- Fixed masked text leaking through accessibility data. When an element's value was masked, its accessibility label and hint were still sent unmasked, so text your mask rules were set up to redact could reach the collector in
accessibility.label. React Native apps were affected most, because a<Text>element uses its own content as its accessibility label by default. The label and hint are now masked by the same rules as the value. - Fixed
logSignalpayload fields being wrapped in asignal.data.valueenvelope that Connect behavior signals doesn't recognize, so the values you passed didn't arrive as expected. Values now sit directly undersignal, the same format identity messages already use. ThelogSignalsignature is unchanged. - Fixed gesture events being dropped or duplicated when the tapped control had no CSS ID.
- Fixed a crash on malformed gesture data.
- React Native: Fixed session replay capturing an almost empty control tree for screens shown in a
<Modal>, or for any screen outside thereact-native-screensnavigator. The screenshot looked correct, but almost nothing on the screen could be inspected. - React Native: Fixed duplicate and missing screen views with nested native stack navigators (
createNativeStackNavigator). Leaving a tab that contained a nested stack produced duplicate screen views. Pushing or popping a screen within a nested stack produced no screen view at all. - React Native: Fixed the screen view
referrerpointing to the current screen instead of the previous one in apps that use a wrapped navigation container. This collapsed session replay into a single step.
Our environment for this release
- Xcode 26.2
- macOS 26.1
- iOS 15.1 to 26.2
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens: Progressindicator, AlertViewController, Gestures screenview, and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Jul 3, 2026 · 2.1.15
New features
Push permission API. Request push notification permission and query authorization status directly through the SDK using the new requestAuthorization(options:) and getCurrentAuthorization() methods — without importing UserNotifications or managing UNUserNotificationCenter callbacks. See API reference and Push configuration guide.
Bug fixes
- Closed a version gap on the release channel. React Native apps using useRelease: true were receiving an older Tealeaf build that was missing recent screen-capture fixes, until the release pod caught up to Tealeaf 10.6.337.
- Fixed a crash on iOS 17 and later when the app delegate implements scene lifecycle methods.
- Fixed automatic push mode silently dropping the APNs device token when the app delegate doesn't declare the APNs registration methods itself. This affected React Native bare-workflow and Cordova apps.
- Fixed React Native layout handling in the native SDK.
Migration notes
Tealeaf and EOCore modules are now bundled inside the Connect distribution for Carthage users. If you use Carthage, remove any separate explicit dependencies on go-acoustic/Tealeaf or go-acoustic/EOCore before upgrading. For instructions, see Update the Connect iOS library.
Our environment for this release
- Xcode 26.2
- macOS 26.1
- iOS 15.1 to 26.2
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens: Progressindicator, AlertViewController, Gestures screenview, and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Apr 14, 2026 · 2.0.8
Improvements
- Mobile push notifications are now supported in the Connect iOS SDK. You can enable push notifications for your native iOS app (Swift and SwiftUI) to send targeted messages to your users. For setup instructions, see Enable push notifications in a native iOS app. Push notification support requires a new app key generated through the Mobile app integration in Connect. For details, see Update the Connect iOS library.
- Connect supports Swift 6.
Migration notes
- Objective-C apps: If you have integrated the Connect SDK using Swift Package Manager or Carthage, replace the legacy
TLFApplicationHelperinitialization call withConnectApplicationHelperonce you upgrade to SDK 2.0.8. In some configurations, the SDK may not find its configuration files if this step is skipped. - Swift and SwiftUI apps (Swift Package Manager and CocoaPods): Remove the
EOCoreandTealeafimports from your initialization code after upgrading to SDK 2.0.8. The SDK no longer requires these imports directly. - Swift and SwiftUI apps (Carthage): All three frameworks —
Connect,Tealeaf, andEOCore— are still required at this version. Do not remove the imports or xcframework references.
For details, see Update the Connect iOS library.
Our environment for this release
- Xcode 26.2
- macOS 26.1
- iOS 15.1 to 26.2
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens Progressindicator, AlertViewController, Gestures screenview and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- React Native apps may have issues with dynamic builds. Use the static version instead.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Jan 30, 2026 · 1.0.81
Improvements
Updated the library using the latest Xcode and iOS versions (26.2).
Our environment for this release
- Xcode 26.2
- macOS 26
- iOS 15.1 to 26.2
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens Progressindicator, AlertViewController, Gestures screenview and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- React Native apps may have issues with dynamic builds. Use the static version instead.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Sep 30, 2025 · 1.0.68
Improvements
- Adjusted the library to support React Native for npm plugin.
- Adjusted the library to the new minimal iOS version of 15.1.
Our environment for this release
- Xcode 16.4
- MacOS 15.5
- iOS 15.1 to 18.x
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the Gestures screenview is off when captured using ER because of timing or garbage collection.
- Template issues. The battery icon is not visible in green anymore. The Back link is missing during capture on some screens Progressindicator, AlertViewController, Gestures screenview and picker view.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- If your iOS app is built on the React Native framework, keep in mind that there is an issue with dynamic builds. We will use a static version instead.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Jan 23, 2025 · 1.0.47
Bug fixes
- Fixed a validation issue with XCFramework signature.
- Fixed an issue with Swift Package checksum.
Our environment for this release
- Xcode 16.1
- macOS 15.0.1
- iOS 13.x to 18.x
Supported architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- The library captures gestures even when the gestureRecognizer is set to NO. This is an Apple defect.
- On iPadOS, only single-window applications are supported.
- The pink border on the 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, the Gestures screenview and picker view.
- Template issue. The battery icon is not visible in green anymore.
connectionTyperemains N/A if a device is using Wi-Fi when the app starts.DoPostOnScreenChangeis not working as expected, because of a temp queue.- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- React Native apps may have issues with dynamic builds. Use the static version instead.
- Certain types of alerts may be replayed incorrectly.
- If a View Controller has more than one WKWebViews, gestures may be off by a few pixels.
Android
System compatibility
- Native OS: Android 8–16 (API 26–36)
- Development tools: Android Studio Otter (2025.2.1); JDK 21
Oct 6, 2026 · 11.1.17
View this version on Maven Central
The version moves to 11.1 because Tealeaf and EOCore are now bundled into the Connect artifact. This release also adds Connect-native dialog and layout capture methods, and fixes data loss, masking and gesture capture issues in Views and Compose apps.
To update to this version, see Update the Connect Android library.
New features
- Connect-native capture methods. Added
Connect.logDialogLayout(context, dialog),Connect.canTakeScreenShot(logicalPageName)andConnect.getLayoutInfo(logicalPageName), Connect-native versions of the Tealeaf dialog and layout capture helpers.
Bug fixes
- Fixed Views apps stopping sending data after the first upload. Connect enables itself slightly after the first activity resumes, so it missed that resume, treated an app on screen as being in the background, and stopped sending until the app went to the background and came back. Compose apps weren't affected.
- Fixed taps on Views being lost before the app's first screen view. A tap compared screen names that can be empty at that point, the comparison failed, and the tap was dropped and reported as a Tealeaf library exception.
- Fixed layout capture reloading a WebView page that came from a form POST. Reloading it replayed the request as a GET, so a POST-only endpoint returned 405 and the user's page was replaced. A WebView is now reloaded for capture only when its page is known to have come from a GET; otherwise it's captured in place. A page loaded before the SDK's first layout capture might therefore be captured without its web content.
- Fixed
Connect.logScreenLayout(activity, …)not capturing on a screen that has stopped changing, such as a settled Compose screen. The call waited for a layout pass that never came, so it returnedtruewithout capturing anything. - Fixed signals being dropped on screens that aren't captured. While capture was off for the current screen (its layout config sets
ScreenChangeorCaptureUserEventstofalse, a whitelist-styleGlobalScreenSettingsdoesn't list it, or capture is paused),Connect.logSignalreturnedfalseand identification signals were discarded, although neither carries screen contents. They're now queued, as push and geolocation messages already were. Screen contents on those screens (layouts, screen views, gestures, clicks and custom events) are still not captured, and a disabled SDK still logs nothing. - Fixed a signal logged on a screen that isn't captured waiting in the queue until the user opened another captured screen. It's now sent right away.
- Fixed capture staying off on the next screen after leaving a screen that isn't captured. When an app logged the old screen's
UNLOADafter the new screen'sLOAD, as Compose apps commonly do, capture stayed off until the user opened yet another screen: layouts, gestures and custom events on that screen weren't captured, and signals waited to be sent. - Fixed returning to a screen from one that isn't captured dropping the screen view and layout of the screen the user came back to, as a repeat of that screen's earlier visit. Both are logged now.
- Fixed the same return being dropped in apps that log no
UNLOAD, such as React Native apps. Entering a screen that isn't captured now ends the earlier visit too, so the return's screen view is logged. - Fixed the layout of the screen on display waiting in the queue until the user opened another screen or the app went to the background, so the last screen of a session arrived late. It's now sent on the next upload.
- Fixed
Connect.disable()not stopping Compose capture. Screen views stopped, but Compose layouts, taps and the client state sent with each layout were still captured, and were sent once the SDK was enabled again. - Fixed Compose apps not capturing double tap, long press and pinch gestures. They're now sent as
doubleTap,tapHoldandpinch(open or close), as in Views apps. Previously a double tap was sent as two taps, a long press as a tap, and a pinch wasn't sent. A double tap is now sent as onedoubleTap, with no tap for its first touch, and a pinch is no longer also sent as a swipe. A touch that moves before lifting, such as scrolling a list, is no longer sent as a tap. - Fixed Compose tap timing to match Views. A tap is now queued once it can no longer become a double tap: about 300 ms after the finger goes down, or as soon as the next touch starts. The tap keeps the time, screen and screenshot of the moment the finger lifted, including when the tap opens another screen.
- Fixed password fields being captured as typed. A password
EditText's text reached the collector in every layout message. It's now captured as one dot per character, including when the user has made the password visible. - Fixed
LoggedTextFieldandLoggedOutlinedTextFieldnot being captured with the text they show. A password field usingPasswordVisualTransformationnow arrives as dots instead of the typed password, and masking rules apply to the shown text, as for Views fields. - Fixed Compose masking applying only
MaskAccessibilityLabelList. It now also appliesMaskIdListandMaskValueList: text in aLoggedText,LoggedButton,LoggedTextFieldorLoggedOutlinedTextFieldthat matches a value or ID rule is masked in the captured layout and obscured in the screenshot, as in Views layouts. Text fields are now also masked byMaskAccessibilityLabelList. Generated IDs no longer include text that a masking rule matches; such composables get an ID without their text, for exampletext_1a2b3c4d. So do composables first shown before Connect is enabled, because no masking rules are loaded yet to check their text against. - Fixed Compose masking not following a composable's text as it changes. Text typed into a field that matches a masking rule is now obscured in the screenshots taken after it, including those sent with taps. Previously it was checked only when the composable moved or was resized.
Improvements
- Matching artifact versions. The four artifacts (
connect,connect-push,connect-push-fcmandconnect-push-hms) are published at the same version.
Migration notes
- Tealeaf and EOCore are now bundled in the Connect artifact and no longer published separately. Declare only
io.github.go-acoustic:connect, plus the push modules you use. When you upgrade, remove any explicitio.github.go-acoustic:tealeaforio.github.go-acoustic:eocoredependency: keeping one alongside Connect causes duplicate classes. - The public API is source and binary compatible with 11.0.x. Code that uses
com.tl.uicorcom.ibm.eotypes directly still compiles, but should move to the Connect-native API.
Sample apps
- The Compose and XML sample apps are now in one public repo, go-acoustic/Acoustic-Connect-Mobile-Sample-App-Android (renamed from Acoustic-Connect-Mobile-Push-Sample-App-Android), as the
sample-composeandsample-xmlmodules over a shared module. The separate Acoustic-Connect-Mobile-Push-Sample-App-Android-XML repo is archived. - The XML sample is now analytics-only. Push is shown in the Compose sample.
- The XML sample's application ID has a
.xmlsuffix, so both samples can be installed side by side. - Both samples' Verification screens have a new "Masking applies value, id and password rules" card, and each sample's
ConnectLayoutConfig.jsonhas aMaskIdListentry for its card number. - Fixed both samples reporting an outdated SDK version. They now report the SDK version they build against.
Our environment for this release
- macOS 26.1
- Android Studio Otter | 2025.2.1 Patch 1
- JDK 21
- Android API level 26 to 36
Known issues
- The library may not work correctly in apps that mix the View system and Jetpack Compose.
- Text change events are not supported yet.
Sep 22, 2026 · 11.0.36
View this version on Maven Central
To update to this version, see Update the Connect Android library.
Bug fixes
Fixed analytics data being lost while uploads to the collector were succeeding. The SDK limits how many message batches it keeps on disk. That limit is meant for when the device can't reach the collector, but it was also applied while uploads were working. When an app produced more batches than the limit within one upload interval, the extra batches were discarded without a log entry, and the loss showed up only as gaps in session replay.
The limit now applies only after uploads start failing. While uploads are working, on-disk storage is capped at 10 times the configured limit. If a batch can't be written, the SDK now logs it.
Our environment for this release
- macOS 26.1
- Android Studio Otter | 2025.2.1 Patch 1
- JDK 21
- Android API level 26 to 36
Known issues
- The library may not work correctly in apps that mix the View system and Jetpack Compose.
- Text change events are not supported yet.
Sep 15, 2026 · 11.0.28
View this version on Maven Central
To update to this version, see Update the Connect Android library.
New features
Connect-native API. Every public Connect API that used a Tealeaf or EOCore type now has a form that uses a Connect type instead. The old forms are deprecated but keep working, so you can migrate at your own pace.
| Deprecated | Use instead |
|---|---|
logScreenview(…, ScreenviewType) | logScreenview(…, ConnectScreenviewType) |
logConnection(Connection?) | logConnection(ConnectConnection?) |
logPinchGestureEvent(…, PinchData?, …) | logPinchGestureEvent(…, ConnectPinchData?, …) |
logPerformanceEvent(…, TLFPerformanceNavigationType?, …) | logPerformanceEvent(…, ConnectPerformanceNavigationType?, …) |
getCurrentScreenView(): Screenview? | getCurrentConnectScreenView(): ConnectScreenview? |
Configuration accessors that take EOLifecycleObjectName | The same accessors, taking the module name as a String (for example "Tealeaf") |
ScreenComposableManager.addAccessiblePosition(Position) | ScreenComposableManager.addAccessiblePosition(ConnectPosition) |
New methods on Connect:
onDestroy(activity, logicalPageName)handles teardown and complements the existingonPauseandonResumemethods.canCaptureUserEvents(activity, logicalPageName)reports whether capture is allowed for a screen. Call it beforelogScreenLayout.logKeyboardEvent(context, isShow)logs a keyboard show or hide event.ConnectMonitoringLevel(IGNORE,CRITICAL,IMPORTANT,INFO) supplies the log level forlogCustomEvent. For example, passConnectMonitoringLevel.INFO.value.
One version for all modules. connect, connect-push, connect-push-fcm, connect-push-hms, tealeaf and eocore now all publish at the same version number.
Bug fixes
- Fixed masked text leaking through accessibility data. When an element's value was masked, its accessibility label and hint were still sent unmasked, so text your mask rules were set up to redact could reach the collector in
accessibility.label. React Native apps were affected most, because a<Text>element uses its own content as its accessibility label by default. The label and hint are now masked by the same rules as the value. The accessibility ID is left unchanged. - Fixed form submissions in instrumented WebViews reaching the server as GET requests. A POST-only endpoint would respond with
405 Method Not Allowedand replace the user's page with an error. Navigation is now handled by the WebView itself, so the original method, body and headers are preserved. The SDK also no longer reloads a page produced by a POST when it re-captures a WebView. - Fixed the SDK replacing the app's own
WebViewClientwhen it instrumented a WebView. Once a WebView was instrumented, the app's callbacks stopped firing. Inreact-native-webview, for example, this silencedonNavigationStateChange,onLoadEnd,onError,onHttpErrorandonShouldStartLoadWithRequest. The SDK now wraps the app's client and forwards every callback to it. - Fixed a screen's layout being dropped when a WebView on that screen never finished DOM capture. The layout is now sent after the wait times out.
- Fixed WebViews hosted by React Native never matching their DOM capture to the screen layout.
- Fixed numeric values in
logSignalpayloads being silently dropped. For example,{ total: 24.99 }now arrives as a JSON number, matching iOS. - Fixed a crash that could occur when a view was removed while the SDK was scanning the view hierarchy in the background.
- Fixed the EOCore POM declaring its dependencies under the wrong group ID, which made them unresolvable for apps that depend on
eocoredirectly.
Improvements
The SDK no longer writes the full FCM registration token or the notification payload to debug logs. The token is shortened to its first and last four characters, and payloads are logged as keys only. Tokens of 9 characters or fewer are fully masked.
Migration notes
JDK 21 is now required. The SDK is now built with Java 21 (JVM target 21). It was previously built with Java 17. To build an app against the SDK, you need JDK 21.
Connect is now a single dependency. Tealeaf and EOCore are now internal dependencies of Connect. Declare only connect, plus whichever push modules you use. Tealeaf and EOCore still resolve automatically at runtime, but they are no longer on your app's compile classpath.
No public Connect method was removed or changed. If your code imports com.tl.uic.* or com.ibm.eo.* types directly, choose one of these options:
- Recommended: switch to the Connect-native equivalents listed under New features.
- Declare
tealeafandeocoreexplicitly, at the same version as Connect:
dependencies {
implementation("io.github.go-acoustic:connect:11.0.28")
// Only needed while your code still uses Tealeaf or EOCore types directly
implementation("io.github.go-acoustic:tealeaf:11.0.28")
implementation("io.github.go-acoustic:eocore:11.0.28")
}Our environment for this release
- macOS 26.1
- Android Studio Otter | 2025.2.1 Patch 1
- JDK 21
- Android API level 26 to 36
Known issues
- The library may not work correctly in apps that mix the View system and Jetpack Compose.
- Text change events are not supported yet.
Jul 3, 2026 · 11.0.13
View this version on Maven Central
Bug fixes
Fixed a crash in View-based apps when calling AppCompatDelegate.setDefaultNightMode(). Dark-mode toggling now works correctly when the Connect SDK is enabled.
Improvements
- Improved WebView instrumentation to preserve content loaded via
loadDataWithBaseURL(null, …). Previously, the SDK calledgetUrl()on such pages, received"about:blank"and reloaded the WebView over the app's rendered content. - Push notification setup is now simpler:
firebase-messagingis included as a transitive dependency inconnect-push-fcm, so you no longer need to declare it separately. Leaving the explicitfirebase-messagingdeclaration in place is safe - Gradle deduplicates it automatically. To clean up, update your dependencies as follows:
dependencies {
implementation("io.github.go-acoustic:connect-push-fcm:11.0.11")
implementation(platform("com.google.firebase:firebase-bom:34.14.0"))
implementation("com.google.firebase:firebase-messaging")
}dependencies {
implementation("io.github.go-acoustic:connect-push-fcm:11.0.13")
implementation(platform("com.google.firebase:firebase-bom:34.14.0"))
}Our environment for this release
- macOS 26.1
- Android Studio Otter | 2025.2.1 Patch 1
- Android API level 26 to 36
Known issues
- The library may not work correctly in apps that mix the View system and Jetpack Compose.
- Text change events are not supported yet.
May 7, 2026 · 11.0.11
View this version on Maven Central
To update to this version, see Update the Connect Android library.
New features
- Push notifications. Firebase Cloud Messaging (FCM) and Huawei Mobile Services (HMS) push notifications are now supported. The SDK auto-detects the available provider on the device, with an optional strict-provider override. For setup instructions, see Enable push notifications in an Android app (Firebase).
- Added an auto instrumentation script for Connect Composable wrappers.
- Added a custom Button Composable wrapper.
- Added a gesture event unique ID with Connect Wrappers.
- Renamed
contentDescriptiontomaskLabel()to differentiate the custom property from the Android semantic property. - Added
.connectMask— a new modifier for masking any Composable in session replay. For details, see Enable privacy protection in Android Compose apps.
Bug fixes
Fixed a Compose UI screenshot issue with screen transitions.
Improvements
- Minimum Android version raised from API level 21 (Android 5.0) to API level 26 (Android 8.0).
- SDK modularized into separate artifacts. The library is now split into
:connect(core analytics),:connect-push(shared push infrastructure),:connect-push-fcm(Firebase), and:connect-push-hms(Huawei). Analytics-only integrations continue to use:connect.
Our environment for this release
- macOS 26.1
- Android Studio Otter | 2025.2.1 Patch 1
- Android API level 26 to 36
Known issues
- The library may not work correctly in apps that mix the View system and Jetpack Compose.
- Text change events are not supported yet.
Jun 16, 2025 · 10.4.48
View this version on Maven Central
Bug fixes
Fixed a Compose UI screenshot issue with screen transitions.
Improvements
- Added an auto instrumentation script for Connect Composable wrappers.
- Added a custom Button Composable wrapper.
- Added a Gesture event unique ID with Connect Wrappers.
- Renamed
contentDescriptiontomaskLabel()to differentiate our custom property from the semantic property. - Added a new privacy protection method for Jetpack Compose apps. It's now possible to mask any Composable with a simple
.connectMaskmodifier. For details, see Enable privacy protection in Android Compose apps.
Our environment for this release
- macOS 15.3
- Android Studio Meerkat Feature Drop | 2024.3.2 Patch 1, Android 14 (API level 34). The minimum supported API level - Android 5.0 (API level 21).
Known issues
- We cannot guarantee that the current version of the library is compatible with Android apps using a mixture of the Traditional View-based UI and Jetpack Compose.
- Text change events are not supported yet.
Dec 17, 2024 · 10.4.28
View this version on Maven Central
To update the library in your project, open the app-level build.gradle file and change the version number to 10.4.28.
dependencies {
implementation("io.github.go-acoustic:connect:10.4.28")
}Improvements
- The library now supports Android apps built with Jetpack Compose. You can check out how the library captures user sessions from our sample app or add the library to your own Compose-based app.
- We have simplified dependency requirements in build.gradle.
Our environment for this release
- macOS 15.0
- Android Studio Ladybug | 2024.2.1 Patch 3
- Android 14 (API level 34)
Known issues
- We are working on the processing of gesture events for apps with Compose-based UI. You may see a generic ComposeView control in session replays. Sometimes gesture events might show up under the next screen.
- We do not guarantee that the current version of the library is compatible with Android apps using a mixture of the Android View framework and Jetpack Compose.
NoteWe'll keep adding new versions of the Connect library for native Android apps to Maven Central.
React Native
System compatibility
- Hybrid framework: React Native 0.84–0.87; Expo SDK 56–57
- Native OS: Android 8–16 (API 26–36); iOS 15.1–26
Oct 7, 2026 · 19.1.8
The 19.1 release supports React Native 0.84 to 0.87. It raises the minimum versions of React Native, Expo, Node and the native Connect SDKs, and fixes several screen capture issues on iOS and Android. No JavaScript API changed.
Breaking changes
- React Native 0.82 and 0.83 are no longer supported. The minimum is now 0.84, because the Nitro version this release requires can't build against React Native 0.83's iOS target. If your app uses an older version, stay on the latest 19.0.x release.
- Expo SDK 55 is no longer supported, because it ships React Native 0.83. Use Expo SDK 56 or 57, or stay on SDK 19.0.x.
react-native-nitro-modulesmust be exactly0.37.1. Version 19.0.x required0.35.9. Upgrade it together with the SDK: a mismatched Nitro version stops the SDK from starting.- Android requires Connect Android SDK 11.1 or newer. The supported range is
[11.1.16-beta, 12.0.0), because the bridge uses Connect APIs added in 11.1 and depends on the Android fixes below. With the default configuration, your app picks it up automatically. WithuseRelease: true, your app uses Maven Central releases only, so it needs the 11.1 release there. - iOS requires Connect iOS SDK 2.1.51 or newer. Previously the minimum was 2.1.13. 2.1.51 is the first build with all the iOS fixes below. Newer 2.1.x and 2.2.x builds also work.
- Node 20.19.4 or newer is required. Previously the minimum was 20.0.0.
New features
- React Native 0.87 support, alongside 0.84, 0.85 and 0.86. Each supported version was verified on a new app: installing, building natively on iOS and Android, and starting the SDK and sending an event on both platforms.
- React Native 0.87 needs Node 22.13 or newer. React Native 0.84 to 0.86 still work with Node 20.19.4 or newer.
Bug fixes
- Android: Your app now gets the Connect Android SDK from the same repository as the bridge. Connect betas are only published to a GitHub-hosted Maven repository, which the bridge's build used but your app's build didn't. With the default configuration, your app packaged the newest Maven Central release while the bridge was compiled against a newer beta. On 19.1 this crashed the app with
NoSuchMethodErrorwhen a dialog opened, and logged the error on every screen change.useReleasenow sets the source for both:false(the default) uses the beta repository, andtrueuses Maven Central releases only, so it needs a Connect Android 11.1 release there. - Android: Tap and text input capture no longer looks up the touched view on the JavaScript thread. React Native's renderer requires that lookup on the UI thread, so debug builds logged an
Expected to run on UI thread!assertion on every tap, and the lookup competed with the renderer while it updated views. The lookup now runs on the UI thread, and a view removed before the lookup runs is skipped. - Android:
Connect.AndroidVersionpins now hold. Previously, with push turned on, a pin could be replaced by the newest version in range. A pin outside the supported range now fails during configuration, and the message shows the range. - Android: The postinstall step no longer adds a second
apply from: .../config.gradleline toandroid/app/build.gradlewhen your app already has one. - iOS: Screen capture now uses the react-native-screens screen that's displayed instead of React Native's root view controller. Launch captures and explicit layout captures no longer send a duplicate screen view that refers to itself. One case remains: switching to a tab that contains a nested stack still sends one extra screen view.
- iOS (with Connect iOS SDK 2.1.49 or newer): When an
Alert.alertwas on screen and screenshots were on, the current screen was sent again about every 0.6 seconds until the alert closed. This no longer happens. The view controller that hosts the alert is no longer logged as a screen. Instead, the alert is reported like a native alert: an UNLOAD of the screen, then an alert screen view while it's shown. - iOS debug builds (with Connect iOS SDK 2.1.51 or newer): React Native's development loading banner, shown on every Metro refresh, is no longer logged as a screen. Previously, each refresh sent an extra screen view, a layout and an UNLOAD.
- Android (with Connect Android SDK 11.1.11-beta or newer): A signal logged on a screen with capture turned off is now sent immediately, instead of waiting until the user opens a captured screen.
- Android (with Connect Android SDK 11.1.13-beta or newer): Returning to a screen after visiting one with capture turned off now logs the screen view. Previously it was dropped as a duplicate of the earlier visit.
- Android (with Connect Android SDK 11.1.16-beta or newer): Password fields (
TextInputwithsecureTextEntry) are now captured as one dot per character. Previously, the typed text reached the collector in text change events. - iOS (with Connect iOS SDK 2.1.46 or newer): With
NumberOfWebViewsset, layouts are now captured for screens without a WebView. Previously, the setting stopped layout capture on those screens, so apps that use it may now see more layout messages. Screens with a WebView still capture the layout after the page loads.CaptureLayoutOn: 0still turns off layout capture. - iOS (with Connect iOS SDK 2.1.46 or newer): The SDK no longer blocks your app's own inherited
webView(_:didFinish:)and similar delegate callbacks.
Migration notes
To upgrade from 19.0.x:
- Move to React Native 0.84 or newer, React 19.2.3 or newer and Node 20.19.4 or newer. On Expo, move to SDK 56 or newer. You don't need to change your app code.
- If you pin
Connect.AndroidVersion, pin 11.1.16-beta or newer. A lower pin now fails during configuration. Beta versions are only on the GitHub-hosted repository, so withuseRelease: true, pin a Maven Central 11.1 release in that range instead. - If you pin
Connect.iOSVersion, pin 2.1.51 or newer. - Install both packages together:
npm install react-native-acoustic-connect-beta@^19.1.1 [email protected] - Run
pod installinios/. On Expo, runnpx expo prebuildagain.
Sample apps
- All three sample apps now build on React Native 0.86.3 with React 19.2.3. The Expo sample uses Expo SDK 57.
For changes in 19.0.x, see the release notes for 19.0.34.
Our environment for this release
- Xcode 26.4.1
- macOS 26.3
- iOS 15.1 to 26.x
- Supported architectures: arm64 and x86_64 on the simulator, arm64 on devices
Known issues
- iPad isn't supported on iOS 13 and later, because of changes Apple made in iPadOS.
- Dual SIM features are in beta.
Sep 22, 2026 · 19.0.34
To update to this version, see Update the Connect React Native library.
Bug fixes
On Android, setCurrentScreenName no longer captures a screen layout, which matches iOS. <Connect> calls this method on every touch, so Android sent a layout message of tens to hundreds of KB with each tap. On tap-heavy screens this could overflow the SDK's disk cache and lose screen views and replay data. In our tests, twelve taps on one screen went from 21 layout messages (586 KB) to 4 (67 KB), and every tap was still captured. Layouts are now captured on navigation only.
Migration notes
If you call setCurrentScreenName directly for a screen that <Connect> can't detect, and you relied on the layout it used to capture, call TLTRN.logScreenLayout(name) after it.
Our environment for this release
- Xcode 26.4.1
- macOS 26.3
- iOS 15.1 to 26.x
Sep 15, 2026 · 19.0.28
To update to this version, see Update the Connect React Native library.
Bug fixes
- The
layoutblock in ConnectConfig.json is now applied on both iOS and Android. - Advanced settings in ConnectConfig.json now take effect. Previously they were written to a file the native SDK doesn't read.
- Screen layout capture now honors
CaptureLayoutDelayfrom ConnectConfig.json. Previously the wrapper always captured with no delay, so a capture triggered by React Navigation fired at the start of the screen transition and produced half-rendered layouts in session replay. - Identity signals now default to the method attribute that matches the signal type:
loggedInsendsloginMethodandaccountRegisteredsendsregistrationMethod. PreviouslyloggedInsignals sentregistrationMethodand were rejected by server-side validation. - Android: Signal and event payload values now reach the native SDK with their original types instead of being converted to strings.
- Android: Fixed a build failure with Connect Android SDK 11.0.28 and later, which no longer expose Tealeaf and EOCore classes at compile time.
Improvements
logSignalaccepts nested JSON objects and arrays invalues, so structured payloads no longer need to be flattened.- Top-level numbers in a
logSignalpayload now reach the collector on Android as well as iOS, with Connect Android SDK 11.0.28 or later. TLTRN.logScreenLayout(name)accepts an optional second argument that overrides the configured delay for a single call. Pass0to capture immediately, or a positive number of milliseconds to wait. This helps on screens whose content loads asynchronously.- The default
CaptureLayoutDelayis now 500 ms on both platforms, which is long enough for a typical screen transition to finish. Previously the shipped templates used 1 ms, and apps without a layout block got 1 ms on iOS and 500 ms on Android. - The npm package no longer includes the
SampleUIdemo app, which removes 326 files (about 3.5 MB unpacked). It targeted a React Native version below this SDK's minimum of 0.82. The maintained samples arebare-workflowandexpo.
Migration notes
iOS: The logScreenLayout delay is now in milliseconds, matching Android and CaptureLayoutDelay. Previously the value was passed to the native API as seconds, so a 300 ms delay waited 300 seconds. If you passed a positive delay on iOS and adjusted it to compensate, remove the adjustment.
Our environment for this release
- Xcode 26.4.1
- macOS 26.3
- iOS 15.1 to 26.x
Jul 7, 2026 · 19.0.11
Bug fixes
Fixed an Android build failure under useRelease: true, caused by a required dependency (eocore) that was only available as a beta release, which the production build setting was rejecting.
Migration notes
If you're already on the canonical react-native-acoustic-connect package, updating to 19.0.11 requires no code changes. If you're still on react-native-acoustic-connect-beta, you'll need to switch to the canonical package first — see Update the Connect React Native library.
Jul 3, 2026 · 19.0.9
New features
- Mobile push notifications. Push notifications are now supported on iOS and Android, with rich content — thumbnail images, expandable content, and tappable actions — authored from Connect. For setup instructions, see Enable push notifications in a React Native app.
- Identity signals. Match anonymous app sessions to known contacts in your Connect audience by calling the new
logIdentity()method at sign-in or registration. See User identification signals in a React Native app. - Expo support (SDK 55+). The SDK now supports Expo managed workflow projects, including push notifications. See Integrate the Connect SDK into an Expo app.
- SDK lifecycle control. Two new methods let you stop and restart the SDK at runtime without reinitializing.
disable()stops all data capture and network calls.enable()restarts the SDK using the same ConnectConfig.json configuration. Useful for consent flows, A/B-test gates, or opt-out toggles.
Improvements
- React 19 compatibility.
<Connect>now readsprops.refinstead of the legacyelement.refto support React 19's ref model, and thereact-native-nitro-modulespeer dependency is now constrained to an exact version to prevent build failures. - More reliable navigation tracking.
<Connect>accepts an explicitnavigationRefprop and now polls for the NavigationContainer ref with a 10-second grace window, fixing navigation tracking for apps where the container mounts after providers (async init, splash gate, etc.).
Migration notes
No changes to your existing app code are required. To upgrade from version 18, install [email protected] alongside the SDK. For details, see Update the Connect React Native library.
Our environment for this release
- React Native 0.82.0–0.85.x (new architecture)
- Node.js 20 or later
- iOS 15.1–26.2
- Xcode 26.2
- macOS 26.0.1
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- Session replay accuracy (iOS). Session replay on iOS may show stale screen snapshots and does not track scroll position. Android is not affected.
- Webviews are not captured in session replay. Content rendered inside a
WebViewcomponent is not recorded. - iPad is not supported on iOS 14 and later. Due to changes introduced in iPadOS, the SDK does not support iPad on iOS 14 and later.
- Dual SIM features are in beta. Behavior using multiple carriers may be unreliable.
Apr 30, 2026 · 18.0.23
Bug fixes
- Fixed a crash in the
<Connect>component caused by incompatibility with React 19. - Fixed a build failure caused by an undeclared version constraint on the react-native-nitro-modules peer dependency.
Our environment for this release
- React Native 0.78 or higher using new architecture
- Node.js 20.0.0 or higher
Known issues
- On iPadOS, only single-window applications are fully supported.
- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
- Only older JSC bridge architecture is supported. Expo applications are not supported unless they are ejected as native applications.
Nov 22, 2024 · 16.0.39
The React Native version of the Connect library is available in the npm public registry - react-native-acoustic-connect.
Our environment for this release
- Xcode 16.1
- macOS 15.0.1
- iOS 13.x to 18.x
Supported iOS architectures:
- simulator: arm64 and x86_64
- device: arm64
Known issues
- On iPadOS, only single-window applications are fully supported.
- Reporting of multiple carrier names in JSON for devices with Dual SIM is a beta feature. It is not fully used in reporting.
Flutter
System compatibility
- Hybrid framework: Flutter 3.16–3.27
- Native OS: Android 5–15 (API 21–35); iOS 15.1–26
Mar 11, 2026 · 2.41.0
This release fixes project-level ConnectConfig.json values not reaching the SDK.
Bug fixes
- Fixed
connect_cli/bin/connect_cli.dartso that values fromConnectConfig.jsonat the project level are passed to the SDK.
Our environment for this release
- Flutter SDK 3.27.4
- Visual Studio Code 1.99.3 (Universal)
- Xcode 26.1
- macOS 26.0.1
- iOS 15.1 to 26.x
- Android 21–35
- Supported iOS architectures: arm64 and x86_64 on the simulator, arm64 on devices
Known issues
- Setting the iOS version causes
pod installto fail. - Our sample app is having some build issues due to a new version of Flutter. It will be replaced in a later version.
- Only Android & iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Text change event isn't supported yet.
- Sometimes a masking overlay is carried on to the next screen. This is due to Flutter view tree design.
Mar 5, 2026 · 2.40.0
This release fixes project-level ConnectConfig.json values not reaching the SDK.
Bug fixes
- Fixed
connect_cli/bin/connect_cli.dartso that values fromConnectConfig.jsonat the project level are passed to the SDK.
Our environment for this release
- Flutter SDK 3.27.4
- Visual Studio Code 1.99.3 (Universal)
- Xcode 26.1
- macOS 26.0.1
- iOS 15.1 to 26.x
- Android 21–35
- Supported iOS architectures: arm64 and x86_64 on the simulator, arm64 on devices
Known issues
- Setting the iOS version causes
pod installto fail. - Our sample app is having some build issues due to a new version of Flutter. It will be replaced in a later version.
- Only Android & iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Text change event isn't supported yet.
- Sometimes a masking overlay is carried on to the next screen. This is due to Flutter view tree design.
Jan 20, 2026 · 2.39.0
Improvements
Allowed setting log level for Flutter level logging.
Our environment for this release
- Flutter SDK 3.27.4
- Visual Studio Code 1.99.3 (Universal)
- Xcode 26.1
- macOS 26.0.1
- iOS 15.1 to 26.x
- Android 21-35
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- Our sample app is having some build issues due to a new version of Flutter. They are going to be addressed later.
- Only Android & iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Text change event isn't supported yet.
- Sometimes a masking overlay is carried on to the next screen. This is due to Flutter view tree design.
Nov 11, 2025 · 2.38.0
Bug fixes
Fixed an issue due to which some screens had null instead of a name in session replays. The library had not been updating logicalPageName from AutoLayout/{user.Navigation Route Name}.
Improvements
- Added support for Android build.gradle.kts in addition to build.gradle.
- Added the ability to set a logicalPageName for a route item that does not have a value for property name. The new logic first checks if route.settings.name exists and is not empty. If it is null/empty, it examines the route's runtime type to provide meaningful names:
- ModalBottomSheetRoute → 'ModalBottomSheet'
- DialogRoute → 'Dialog'
- PopupRoute → 'Popup'
- PageRoute → 'Page_{hashCode}'
- Any other route type → '{RouteType}_{hashCode}'
Our environment for this release
- Flutter SDK 3.27.4
- Visual Studio Code 1.99.3 (Universal)
- Xcode 26.1
- macOS 26.0.1
- iOS 15.1 to 26.x
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- Our sample app is having some build issues. They are going to be addressed later.
- Only Android & iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Text change event isn't supported yet.
- Sometimes a masking overlay is carried on to the next screen. This is due to Flutter view tree design.
May 10, 2025 · 2.36.0
Improvements
Added package_info_plus 8.3.0 support.
Our environment for this release
- Flutter SDK 3.27.4
- Visual Studio Code Version: 1.90.2 (Universal)
- Xcode 15.4
- macOS 15.2
- iOS 13.x to 18.x
- Android 21-35
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- Android app will have build issues on AS IDE LadyBug and newer, due to out-of-date packages.
- Only Android & iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Sometimes masking overlay carries to the next screen due to Flutter view tree design.
Feb 25, 2025 · 2.35.0
Improvements
Added Logger 2.0.0 support.
Our environment for this release
- Flutter SDK 3.27.4
- Visual Studio Code 1.90.2 (Universal)
- Xcode 15.4
- macOS 15.2
- iOS 13.x to 18.x
- Android 21-35
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Oct 9, 2024 · 2.33.0
Our environment for this release
- Flutter SDK 3.22.2
- Visual Studio Code 1.90.2 (Universal)
- Xcode 15.4
- macOS 14.5
- iOS 12.x to 15.x
- Android 21-34
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- Only the Android and iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Sometimes masking overlay carries to the next screen due to Flutter view tree design.
Jul 13, 2024 · 2.17.0
This is the first stable release of the Connect library for Flutter apps.
Our environment for this release
- Flutter SDK 3.22.2
- Visual Studio Code 1.90.2 (Universal)
- Xcode 15.4
- MacOS 14.5
- iOS 12.x to 15.x
- Android 21-34
Supported iOS architectures:
- simulator (arm64, x86_64)
- device (arm64)
Known issues
- Only the Android and iOS platforms are supported.
- When Navigation route isn't set, replay shows null screenview.
- Sometimes masking overlay carries to the next screen due to Flutter view tree design.
Cordova
System compatibility
- Hybrid framework: Cordova CLI 12
- Native OS: Android 8–16 (API 26–36); iOS 15.1–26
Oct 20, 2026 · 1.1.0
This release lets you build an analytics-only app with push turned off, and fixes an iOS build issue that removed other plugins' pods.
New features
- Turn push on or off.
PushEnabledinConnectConfig.jsonnow controls push for the whole plugin. It'strueby default, so existing apps keep push as before. (The Capacitor plugin'spushEnabledsetting is off by default.) Set it tofalseto build an analytics-only app:- On Android, the app uses the
connectartifact and doesn't need Firebase. - On iOS, the SDK runs without push. The plugin doesn't add the
ConnectNSEandConnectNCEextensions, the App Group, theaps-environmententitlement or theremote-notificationbackground mode. If another plugin or yourconfig.xmldeclares the background mode, it stays. - Calls to
push.*are rejected withACOUSTIC_PUSH_DISABLED.
- On Android, the app uses the
Bug fixes
- iOS: The hook that rewrites the Podfile kept only the Connect pod and removed pods declared by your app's other plugins. It now keeps them, and it restores pods that an earlier run removed from
pods.json.
Our environment for this release
- Xcode 26.2
- macOS 26.0.1
- iOS 15.1 to 26.x
- Android minSdk 26 and SDK 36
Known issues
- You can't fully test rich push on the iOS Simulator, because simulators don't display the large icon.
- Clicks and typing inside the web page aren't captured automatically. Call
logClickEventandlogTextChangeEventyourself. Connect receives them as custom events. - Native layout masking rules don't mask text inside the WebView. To keep page content out of captures, set
ScreenCaptureEnabled: false. layoutConfigAndroidreplaces the Android SDK's entire layout configuration. How layout rules behave on Android hasn't been verified.- On Android, the SDK drops a screen view while its screen name is still queued. As a result, calling
logScreenViewContextUnloadfor the screen that just loaded is rejected withACOUSTIC_INTERNAL_ERROR. Unload the previous screen instead. - Payloads are shaped differently on each platform:
logCustomEventvalues are nested underdata.valueon iOS but are flat on Android.- A
logSignalpayload is undersignal.data.valueon iOS but at the root ofsignalon Android. - On Android SDK versions before 11.0.24-beta,
logSignaldrops a top-level number. The default version, 11.1.17, sends it.
- On iOS,
logExceptionEventreportsstackTrace: (null)and puts the stack trace text indata.stacktrace.
Oct 15, 2026 · 1.0.34
This release adds the analytics API to the JavaScript bridge, new configuration options for the kill switch, location logging and screen capture, and several iOS and Android fixes.
New features
- Kill switch control. The remote kill switch is now opt-in. Both native SDKs ship with the kill switch on, but this plugin turns it off unless your app opts in with
KillSwitchEnabledandKillSwitchUrlinConnectConfig.json. - Location logging control. Use
LocationLoggingEnabledinConnectConfig.jsonto opt in to or out of location data collection. To keep the native SDK's own default, leave it out or set it tonull. - Pin a native SDK version. Use
AndroidVersionandiOSVersionto pin a specific native Connect SDK version instead of the plugin's default. - Analytics API. The JavaScript bridge now includes these methods, with TypeScript types:
logCustomEvent,logSignal,setCurrentScreenName,logScreenViewContextLoad,logScreenViewContextUnload,logClickEvent,logTextChangeEvent,logExceptionEvent,flushQueues,isSdkEnabledandgetSdkVersion. Text passed tologTextChangeEventis masked by default before it leaves JavaScript. - Screen layout, location and dialog events. The JavaScript bridge also adds
logScreenLayout(name, delayMs?),logLocation(),logLocationUpdate(latitude, longitude, level?)and the dialog eventslogDialogShowEvent,logDialogDismissEvent,logDialogButtonClickEventandlogDialogCustomEvent. Connect receives dialog events as custom events (DialogShowEvent,DialogDismissEvent,DialogButtonClickEventandDialogCustomEvent) with the same event names and keys on both platforms. - Runtime configuration. Use
setConfigItemandgetConfigItemto set and read native SDK configuration items while the app runs. TypeScript types are included. - Turn off screen capture. Set
ScreenCaptureEnabledtofalseinConnectConfig.jsonto turn off layout and screenshot capture on both platforms. Screen views are still sent. Leave it out to keep the SDK default. - Screen capture rules. Use
layoutConfig,layoutConfigIosandlayoutConfigAndroidinConnectConfig.jsonto set the SDK's screen capture rules (AutoLayoutandAppendMapIds). Rules are merged per platform. - Sample app. The Behaviour tab in the demo app now shows the analytics API in use.
Bug fixes
- iOS: The plugin now requests the screen layout (type 10) after the WebView page loads, because Connect iOS SDK 2.1.39 (debug) and 2.2.2 (release) no longer capture it for Cordova screens. This is skipped when
ScreenCaptureEnabledisfalse. - iOS: The default Connect iOS SDK version is now 2.1.51 or newer, so CocoaPods installs the newest release. Previously it was fixed at 2.1.15. The lowest version you can pin with
iOSVersionis now 2.1.51 (previously 2.1.13), the first build with the iOS screen capture and WebView fixes. - iOS: The version numbers of the rich push extensions (
CFBundleVersionandCFBundleShortVersionString) now match your app's version automatically. Apple rejects App Store submissions when an extension's version doesn't match its app's version. - Switching
useReleasebetween debug and release withcordova plugin rmandcordova plugin addno longer causes a build failure. You no longer need to runcordova platform rm iosandcordova platform add iosto rebuild. - Android: Fixed duplicate push token registration logs and a duplicate Cordova bridge callback warning. They happened when automatic setup and an explicit
enable()call both ran push setup. - iOS:
enable()no longer blocks Cordova's thread watchdog. The native SDK now starts one run-loop turn later instead of on the calling thread.
Migration notes
- Connect iOS SDK 2.1.17 (debug) and 2.1.26 (release) and newer send a
logSignalpayload at the root ofsignalinstead of undersignal.data.value. Update anything that reads signals from the collector to accept the new location.
Our environment for this release
- Xcode 26.2
- macOS 26.0.1
- iOS 15.1 to 26.x
- Android minSdk 26 and SDK 36
Known issues
- You can't fully test rich push on the iOS Simulator, because simulators don't display the large icon.
- Clicks and typing inside the web page aren't captured automatically. Call
logClickEventandlogTextChangeEventyourself. Connect receives them as custom events. - Native layout masking rules don't mask text inside the WebView. To keep page content out of captures, set
ScreenCaptureEnabled: false. layoutConfigAndroidreplaces the Android SDK's entire layout configuration. How layout rules behave on Android hasn't been verified.- On Android, the SDK drops a screen view while its screen name is still queued. As a result, calling
logScreenViewContextUnloadfor the screen that just loaded is rejected withACOUSTIC_INTERNAL_ERROR. Unload the previous screen instead. - Payloads are shaped differently on each platform:
logCustomEventvalues are nested underdata.valueon iOS but are flat on Android.- A
logSignalpayload is undersignal.data.valueon iOS but at the root ofsignalon Android. - On Android SDK versions before 11.0.24-beta,
logSignaldrops a top-level number. The default version, 11.1.17, sends it.
- On iOS,
logExceptionEventreportsstackTrace: (null)and puts the stack trace text indata.stacktrace.
Jul 7, 2026 · 1.0.6
Improvements
- Switching between debug and release builds is now a single step: change
useReleasein ConnectConfig.json and runnpx cordova prepare ios/npx cordova build ios. - Updated the native SDK version dependencies for iOS and Android.
- Added the CocoaPods master specs repo as a fallback source in the generated Podfile, improving
pod installreliability.
Our environment for this release
- Xcode 26.2
- macOS 26.0.1
- iOS 15.1 to 26.x
- Android minSdk 26, SDK 36
Jul 3, 2026 · 1.0.1
This is the first release of the Connect library for Cordova apps. It adds mobile push notifications and identity signals to a Cordova app on iOS and Android through one JavaScript API, window.AcousticConnect. For setup instructions, see Get started with the Connect SDK in a Cordova app.
Our environment for this release
- Cordova CLI 12.0.0 or later
- Node.js 20 or later
- cordova-ios 7.0.0 or later, Xcode 15 or later, CocoaPods
- cordova-android 13.0.0 or later, Android Studio SDK 34 or later, JDK 17
Capacitor
System compatibility
- Hybrid framework: Capacitor 8; Node 22
- Native OS: Android 8–16 (API 26–36); iOS 15.1–26
Oct 20, 2026 · 1.1.0
This release adds location logging, dialog events and a command that sets up rich push for iOS.
Requirements: Capacitor 8 and Node 22 or newer.
New features
- Location logging. Log location data with two new methods:
logLocation()andlogLocationUpdate(latitude, longitude, level?). - Dialog events. Track dialogs in your app with
logDialogShowEvent,logDialogDismissEvent,logDialogButtonClickEventandlogDialogCustomEvent. Connect receives them as custom events (DialogShowEvent,DialogDismissEvent,DialogButtonClickEventandDialogCustomEvent) that use the same event names and keys as the Cordova plugin. - Rich push setup for iOS. Run
npx acoustic-connect setup-ios-pushto add the rich push extensions to your iOS app. It works with Swift Package Manager and CocoaPods. With CocoaPods, the command adds the pod to your Podfile, so runpod installafterward. - Signal payloads on iOS. On iOS, a
logSignalpayload is now at the root ofsignal, the same as on Android. This requires Connect iOS SDK 2.1.26 or newer.
Our environment for this release
- Xcode 26.5
- macOS 26.5
- Capacitor 8 and Node 22
- iOS 15.1 or newer (Connect iOS SDK 2.1.51 or newer)
- Android minSdk 26 and SDK 36 (Connect Android SDK 11.1.17)
Known issues
- Push notifications haven't been tested on physical devices for this release. This covers receiving and tapping a notification, rich push, and the manual push calls such as
didRegisterWithToken. Push registration was tested on the Android emulator and the iOS simulator. - The
iosVersionsetting only applies to apps that use CocoaPods. With Swift Package Manager, the plugin uses the newest 2.x version, starting from 2.1.51. - Native masking rules don't apply to web content: the SDK treats the WebView as a single control. To keep page content out of captures, set
screenCaptureEnabled: false. - With Swift Package Manager, your app needs a Run Script build phase that copies
ConnectResources.bundleinto the app's root folder. Without it, the SDK sends only part of its data. For the steps, see the plugin README.
Oct 15, 2026 · 1.0.8
The Acoustic Connect plugin for Capacitor adds Connect analytics, screen capture and optional push notifications to Capacitor apps on Android and iOS.
Requirements: Capacitor 8 and Node 22 or newer.
New features
- Analytics API. The plugin includes these methods, with TypeScript types:
enable,disable,setLogLevel,logIdentity,getSdkVersion,isSdkEnabled,flushQueues,setCurrentScreenName,logCustomEvent,logClickEvent,logTextChangeEvent,logSignal,logExceptionEvent,logScreenViewContextLoad,logScreenViewContextUnload,logScreenLayout,setConfigItemandgetConfigItem. Text passed tologTextChangeEventis masked by default. - Configuration in
capacitor.config. Configure the SDK in theAcousticConnectblock. WhenappKeyandpostMessageUrlare set, the SDK starts when the app launches, so the first screen is captured. To start the SDK only when you callenable(), setautoEnable: false. - Configuration options. You can set:
useReleaseandroidVersionandiosVersion, to pin a Connect SDK versionkillSwitchEnabledandkillSwitchUrllocationLoggingEnabledscreenCaptureEnabledlayoutConfig,layoutConfigIosandlayoutConfigAndroid, for screen capture rules
- Optional push notifications. Push is off by default. To turn it on, set
pushEnabled. On Android, this uses the Connect FCM push artifact and Firebase Messaging. On iOS, the SDK runs with push. With push off, Android builds use the analytics-only artifact and don't need Firebase. - Push API.
AcousticConnect.pushprovidesrequestPermissionandgetPermissionState. For iOS manual push mode (iosPushMode: 'manual'), it also providesdidRegisterWithToken,didFailToRegister,didReceiveNotificationanddidReceiveResponse. - Rich push setup for iOS. Run
npx acoustic-connect setup-ios-pushto add the Notification Service and Content extensions to the Xcode project of a Swift Package Manager app. The extensions use your app's version number, as the App Store requires. - Project check. Run
npx acoustic-connect doctorto check your app's configuration and its Android and iOS projects. It reports problems that would cause build or runtime failures. - iOS dependency managers. On iOS, the plugin links the Connect SDK through Swift Package Manager or CocoaPods.
- Signal payloads on iOS. On iOS, a
logSignalpayload is at the root ofsignal, the same as on Android. This requires Connect iOS SDK 2.1.26 or newer. - Sample apps. Two sample apps are included: DemoCapacitor, and an Angular and Ionic app.
Our environment for this release
- Xcode 26.5
- macOS 26.5
- Capacitor 8 and Node 22
- iOS 15.1 or newer (Connect iOS SDK 2.1.51 or newer)
- Android minSdk 26 and SDK 36 (Connect Android SDK 11.1.17)
Known issues
- Push notifications haven't been tested on physical devices for this release. This covers receiving and tapping a notification, rich push, and the manual push calls such as
didRegisterWithToken. Push registration was tested on the Android emulator and the iOS simulator. setup-ios-pushonly supports Swift Package Manager apps. If your app uses CocoaPods, add the rich push extensions manually.- The
iosVersionsetting only applies to apps that use CocoaPods. With Swift Package Manager, the plugin uses the newest 2.x version, starting from 2.1.51. - Native masking rules don't apply to web content: the SDK treats the WebView as a single control. To keep page content out of captures, set
screenCaptureEnabled: false. - With Swift Package Manager, your app needs a Run Script build phase that copies
ConnectResources.bundleinto the app's root folder. Without it, the SDK sends only part of its data. For the steps, see the plugin README.
Web
Versions and updates
- All versions are on our CDN.
- For instructions, see Update the Connect library to a newer version.
Sep 28, 2026 · 6.4.196
This release fixes a security issue in how the SDK copies remote configuration.
Bug fixes
- The SDK's utility helpers that merge and copy remote configuration now block prototype pollution.
Our environment for this release
- npm 11.6.2
- Node 20.19.0
- macOS 26.0.1
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Jan 13, 2026 · 6.4.189
Bug fixes
- Fixed a console error thrown by Ajax Listener when certain API responses were empty.
- Fixed an Ajax Listener error when the first parameter of fetch was a URL resource object.
Improvements
- New initialization methods matching Connect subscription tiers:
TLT.initPro,initPremium()andinitUltimate() - Ajax Listener option to enable cooperative chaining so the module can better coexist with other tools
- Ajax Listener option to fall back to using the performanceObserver API when other tools block its use of Fetch and XHR
- Ajax Listener URL filter now matches on full HREF rather than pathname only.
- Ajax Listener new debug logging option
- Ajax Listener now captures API query string parameters.
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Nov 3, 2025 · 6.4.177
Bug fixes
- Added the missing flushQueue module to improve screen capture on iOS devices during page unloads.
- Fixed an issue with successive logSignal calls for the same signal in which earlier attribute values had been overwritten with the value from the most recent call.
- Removed unnecessary console statements from non-debug builds.
- It is now possible to add a callback function to
TLT.initLibAdvandTLT.initLib. You can invokeTLT.initLibAdvusing an options object, as well as the existing fixed set of parameters. The option to add a callback makes it easy to run logSignal code only after the Connect SDK has fully initialized and theTLT.logSignalAPI is available.
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Oct 14, 2025 · 6.4.165
Bug fixes
Fixed an issue with Uncaught TypeError: t.publishOwnership is not a function in domCaptureService.
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Jun 13, 2025 · 6.4.160
Bug fixes
We've fixed an issue due to which messages sent using the TLT.logCustomEvent API from a loop resulted in multiple identical messages rather than expected individual messages. The messages are now deeply cloned in order to get a unique object.
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Mar 24, 2025 · 6.4.157
Bug fixes
Refactored the code to remove the use of optional chaining to support ES5.1.
Improvements
Updated to the latest Ajax listener and also published it to the CDN.
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Feb 14, 2025 · 6.4.148
Bug fixes
- Fixed an issue with the
logSignalobject using reference versus object content, which sometimes resulted in loop behavior. - Fixed an issue with the Data Layer module having Uncaught Range Error: Maximum call stack size exceeded.
Improvements
We have added the support of cross-domain iframes and replay on a single page. To enable the new feature for your application, see Capture iframes from other domains (cross-domain).
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
