## 6.3.6 **Release Date: **October 14, 2026 Includes three iOS breaking changes: JWTDecode 4.0.x, no transitive SnapKit, and a SwiftPM 6.0 floor. Also fixes the duplicate suggested-answer bubble. ### New & Fixed * Fixed (iOS): Tapping an assistant suggested answer no longer leaves a duplicate bubble. Confirm now clears pending outgoing rows for that send when the HTTP confirm can't replace them (empty body or stale local ID). * Improved (iOS): Native layout code uses an internal helper instead of SnapKit, which shrinks the dependency graph for CocoaPods hosts. * Improved: Native SDK bump for iOS. The SDK now pins `KustomerChat` 8.3.0 (CocoaPods). * Removed (iOS): Transitive SnapKit dependency from `KustomerChat` (SPM and CocoaPods). ### Behavioral Improvements Breaking changes (iOS): * JWTDecode moves from 3.3.x to 4.0.x. Hosts that pin JWTDecode to `~> 3.3.0` or any 3.x floor fail CocoaPods and SPM resolution. * SnapKit is no longer a transitive dependency. Hosts that used SnapKit only because the SDK pulled it in must declare it themselves. * The SPM distribution package requires SwiftPM tools-version 6.0. Resolving `kustomer-ios` or the SPM package requires a Swift 6 toolchain. CocoaPods hosts follow JWTDecode's podspec Swift versions for that dependency. Other: * APIs changed: NO. Public `KustomerChat` APIs are unchanged. * New fields: None * Android is unchanged and stays on `com.kustomer.chat:ui` 4.6.2. ### Benefits to your app * Customers see a single bubble after tapping a suggested answer on iOS. * Your iOS build carries fewer transitive dependencies. ### Recommended Action * Before upgrading, raise your app's JWTDecode pin to 4.0.0 or later, or remove the explicit pin. * Add SnapKit to your own dependencies if your app code uses it. * Use a Swift 6 toolchain if you resolve through SPM. * Upgrade `@kustomer/chat-react-native` to 6.3.6, then reinstall iOS pods and verify the build. * If you can't make these changes yet, stay on 6.3.5 until you can. ### Technical Details * Native SDK pins: iOS `KustomerChat` 8.3.0 (updated). Android `com.kustomer.chat:ui` 4.6.2 (unchanged). * npm: [https://www.npmjs.com/package/@kustomer/chat-react-native/v/6.3.6](https://www.npmjs.com/package/@kustomer/chat-react-native/v/6.3.6) * GitHub release: [https://github.com/kustomer/react-native-sdk/releases/tag/v6.3.6](https://github.com/kustomer/react-native-sdk/releases/tag/v6.3.6) ### 6.3.5 **Release Date: **October 13, 2026 Removes the Android desugaring requirement and fixes two iOS issues: a duplicate message bubble and the navigation bar on first paint. ### New & Fixed * Fixed (Android): Hosts with minSdk 26+ no longer need to enable core library desugaring. Hosts with minSdk 24 or 25 still enable it. * Fixed (iOS): Tapping an assistant suggested answer no longer shows a duplicate bubble. The pending "sending" row now gets replaced when the send succeeds. * Fixed (iOS): On iOS 26 and 27, the chat widget navigation bar no longer stays in the compact glass layout on first paint. This applies to History/Answers and to Open Chat Assistant by ID. Visible titles and navigation stack are unchanged. * Removed (Android): The implicit requirement that all hosts enable core library desugaring when depending on Android Chat SDK 4.6.0 or 4.6.1. ### Behavioral Improvements * Android builds no longer fail AAR metadata checks when desugaring is off and minSdk is 26+. * iOS shows one bubble per suggested-answer tap. * iOS shows the correct navigation bar layout on first paint. * APIs changed: NO * New fields: None ### Benefits to your app * Upgrade without Android build configuration changes if minSdk is 26+. * Customers see a single message bubble after tapping a suggested answer on iOS. ### Recommended Action * Upgrade `@kustomer/chat-react-native` to 6.3.5. * If your Android minSdk is 24 or 25, keep core library desugaring enabled. * Android hosts with minSdk 26+ can remove desugaring if you enabled it only for the SDK. ### Technical Details * Native SDK pins: Android `com.kustomer.chat:ui` 4.6.2 (updated). iOS `KustomerChat` 8.2.4 (unchanged). * npm: [https://www.npmjs.com/package/@kustomer/chat-react-native/v/6.3.5](https://www.npmjs.com/package/@kustomer/chat-react-native/v/6.3.5) * GitHub release: [https://github.com/kustomer/react-native-sdk/releases/tag/v6.3.5](https://github.com/kustomer/react-native-sdk/releases/tag/v6.3.5) ### 6.3.4 **Release date:** 10/06/2026 Fixes the duplicate reply bubble and compact first-paint navigation bar on iOS, and pins the native iOS SDK to 8.2.4. ### New & Fixed **Fixed** * **\[iOS]** Fixed a duplicate bubble after a customer taps an assistant suggested answer. A successful send replaces the pending row, so one bubble shows. * **\[iOS]** Fixed the first-paint navigation bar on iOS 26 and 27. History, Answers, and Open Chat Assistant by ID no longer stay in a compact layout. **Improved** * **\[iOS]** Updated the native SDK dependency. The package now pins `KustomerChat` 8.2.4 (CocoaPods). ### Behavioral Improvements * **Suggested answers (iOS):** The pending row is replaced when the send succeeds. The conversation shows one customer reply per tap. * **Navigation bar (iOS):** On iOS 26 and 27, History, Answers, and Open Chat Assistant by ID render the navigation bar in its standard layout on first paint. * **Android:** No change. Android remains on `com.kustomer.chat:ui` 4.6.1. * **Public API changes:** NO * **New fields:** None ### Benefits to your app * iOS customers who tap a suggested answer see a single reply in the conversation. * Chat screens on iOS 26 and 27 look correct the first time they appear, including when you open the Chat Assistant by ID. ### Testing & Compatibility * **Native SDK versions:** iOS `KustomerChat` 8.2.4. Android `com.kustomer.chat:ui` 4.6.1. * **iOS versions with the navigation bar fix:** iOS 26 and 27. * **Backward compatibility:** No public API changes. Android behavior is unchanged. ### Recommended Action * Upgrade `@kustomer/chat-react-native` to 6.3.4 if your app ships on iOS 26 or 27, or if you use assistant suggested answers. * Update your iOS pods after upgrading so that `KustomerChat` 8.2.4 is installed. * Verify on iOS that tapping a suggested answer produces one customer bubble. * Android builds need no action. ### Technical Details * Component: `@kustomer/chat-react-native` 6.3.4 * Pinned native SDKs: iOS `KustomerChat` 8.2.4 (CocoaPods). Android `com.kustomer.chat:ui` 4.6.1 (unchanged). * Release type: Hotfix on top of the previous production release * Related: iOS SDK 8.2.4 contains the same two fixes ## 6.3.3 **Release date:** 10/01/2026 **Summary:** Adds a settling delay before retrying chat recovery on iOS after an unexpected disconnect, avoiding premature retries. ### Fixed * **\[iOS]** After an unexpected disconnect, recovery is delayed briefly so Event Engine can settle; when status returns to Connected from an unexpected state, recovery runs again. Expected disconnect → Connected still does not trigger recovery. ### Improved * **\[iOS]** Pins native SDK to KustomerChat 8.2.3 (CocoaPods). Android remains `com.kustomer.chat:ui` 4.6.1 — no change on Android in this release. ### Behavioral Improvements * Timing change only, scoped to the unexpected-disconnect path on iOS; avoids redundant History-fetch storms on reconnect. Catch-up remains gated on reconnect, unchanged from prior releases. APIs changed: No (inferred — no new fields/methods described in source). ### Recommended Action * Upgrade recommended. No code changes required. * If your app layers custom reconnect/retry logic on top of the SDK, confirm it doesn't double-trigger recovery during the new settling delay. ### Technical Details * See iOS Chat SDK 8.2.3 for the underlying native fix. Android native SDK is unchanged at 4.6.1 in this release. ## 6.3.2 **Release date:** 9/30/2026 **Summary:** Fixes Android presence after a reset and consolidates PubNub subscribe connections on both platforms. ### Fixed * **\[Android]** Resetting PubNub now clears the shared client and presence subscription state before teardown — and still clears it if unsubscribe fails — so the next session can go online for presence again. ### Improved * **\[iOS]** Conversation channel group and customer meta now share one long-lived PubNub subscribe client (push registration stays on a separate client). Soft PAM token refresh is unchanged. Reduces duplicate idle subscribe long-poll traffic. * **\[Android]** Conversation channel group and customer meta now share one long-lived PubNub subscribe client (push notification client stays separate). Soft PAM token refresh and catch-up behavior from the prior release are unchanged. Reduces duplicate idle subscribe long-poll traffic. ### Behavioral Improvements * Presence fix changes reset/teardown ordering only; no change to normal online/offline presence behavior. PubNub client consolidation is connection-layer only — no app-visible behavior change. APIs changed: No (inferred — no new fields/methods described in source). ### Recommended Action * Upgrade recommended. No code changes required. * Pins iOS native Chat SDK to **8.2.2** and Android to **4.6.1** — confirm these minimums before upgrading. ### Technical Details * Android presence fix: shared PubNub client and presence subscription state are cleared before teardown, with the same cleanup applied on the unsubscribe-failure path. * See iOS Chat SDK 8.2.2 and Android Chat SDK 4.6.1 for underlying native changes. ## 6.3.1 **Release date: 9/20/2026** **Summary:** Fixes an iOS issue where Support Center UI could build or tear down off the main thread, risking glitches or crashes. ### Fixed * **\[iOS]** Support Center widget construction and UI teardown could run off the main thread. The native Chat SDK now defers Support Center UI entry points (show / open-chat / KB helpers), loading presentation, widget reset/clear, close, and start-completion callbacks onto the main thread, so Auto Layout and navigation setup never run on a background queue. ### Behavioral Improvements * Timing change only: affected UI operations are now always dispatched to the main thread. Safe for host apps that call show/open helpers from background completions. APIs changed: No (inferred — no new fields/methods described in source). ### Recommended Action * Upgrade recommended. No code changes required. * Pins iOS native Chat SDK to **8.2.1** (Android remains **4.6.0**) — confirm your Android native SDK version is still 4.6.0 or later before upgrading. ### Technical Details * Release stage: GA. No plan restrictions, no role/permission changes, no enrollment step — ships to any host app on RN Chat SDK 6.3.1. * Underlying native fix: see iOS Chat SDK 8.2.1. ### 6.3.0 **Release date: **09/23/2026 **Summary:** Pins the iOS native Chat SDK to 8.2.0, raising the required PubNub Swift dependency to 10.2.0. Breaking change for iOS host apps pinning PubNub directly. ### Breaking Changes * **\[iOS]** Host apps that directly pin PubNub must raise that pin to 10.2.0 (was 6.3.x). The native Chat SDK now resolves `PubNubSwift`/`pubnub/swift` 10.2.0, and mismatched pins will fail dependency resolution. There is no `KustomerChat` public API signature break — this is a dependency-version constraint only. ### New & Fixed * **\[iOS]** More reliable realtime connections: status-driven reconnect, softer auth refresh, and catch-up only after a successful reconnect — reducing dropped connections and unnecessary network traffic. * **\[iOS]** Link previews and the New Conversation control now expose stable accessibility identifiers, with VoiceOver labels on link previews including the URL. ### Behavioral Improvements * **APIs changed:** NO — no React Native JavaScript/TypeScript public API changes. * **\[iOS]** Connection recovery is now status-driven instead of timer-driven, so listeners no longer receive redundant catch-up calls after a flaky connection. ### Testing & Compatibility * Native Chat SDK pins: iOS 8.2.0, Android 4.6.0 (unchanged). * iOS minimum remains 15.0; supported range remains iOS 15.0 through iOS 27. ### Recommended Action * **\[iOS]** Before upgrading, raise any direct PubNub pin in your host app to 10.2.0, or let CocoaPods/SPM unify on 10.2.0 automatically. * No JavaScript/TypeScript code changes required. * Android integrators: no action needed — the Android native pin is unchanged. ### Technical Details * Native Chat SDK dependency pins updated: iOS 8.2.0 (from a prior 8.x pin), Android unchanged at 4.6.0. * iOS PubNub dependency: PubNubSwift/pubnub/swift 10.2.0 (was 6.3.x). ### 6.2.0 **Release date:** 09/22/2026 **Summary:** Adds Android support to the React Native Chat SDK, built on Kotlin 2.2, and fixes PubNub reconnection and push-registration bugs on Android. iOS is unaffected. ### New & Fixed * **New:** Android support for the React Native Chat SDK, backed by native `com.kustomer.chat:ui` 4.6.0. * SDK no longer forces a full PubNub reconnect after a brief app hide/show on Android — expected disconnects now resume normally. * SDK ignores spurious network-lost callbacks on Android when another validated internet connection is still active. * Soft auth-token refresh on Android now cancels cleanly instead of restarting a full subscribe cycle after logout or reset. * Push token register, deregister, and reset no longer race on Android — device-token clearing, reset, enrollment, opt-out, and rotation stay in sync, so customers are no longer re-enrolled under the wrong account after reset. ### Behavioral Improvements APIs changed: **NO** — no public React Native API signatures changed in this release. * Android layer stops routine channel-list health probes and removes the 55-minute healthy-reconnect timer, reducing background network activity. * Android layer performs a soft PAM token refresh instead of a full teardown/resubscribe. * Android layer runs history catch-up only after a genuine reconnect, not on every check. * Push registration on Android now early-returns when the device token is unchanged, avoiding redundant calls. ### Benefits to your app * React Native apps can now support Android alongside iOS from a single SDK. * Fewer background network calls and battery draw from PubNub health checks and reconnects on Android. * More reliable push-token handling and reduced risk of messages routing to the wrong customer after a logout/reset. ### Testing & Compatibility * Android native layer: `com.kustomer.chat:ui` 4.6.0. * iOS: `KustomerChat` remains at 8.1.0 (unchanged from 6.1.0) — no iOS action needed. * PubNub Kotlin SDK bumped 9.0.0 → 13.4.3; Kotlin bumped 1.9.24 → 2.2.21 (Android only). ### Recommended Action 1. **Upgrade to React Native 0.77+ for Android**, and set `react.internal.disableJavaVersionAlignment=true` (and, if needed, `kotlin.jvm.target.validation.mode=warning`). Compile with Java 17. If AGP 8.7.x can't dex Kotlin 2.2 metadata, upgrade R8 to ≥ 8.10.21 or upgrade AGP. 2. **Upgrade Kotlin.** Host Android apps must build with Kotlin ≥ 2.2.0 (2.2.21 recommended) — the underlying native library ships Kotlin 2.2 metadata, and Kotlin 1.9.x hosts cannot consume it. 3. **Enable core library desugaring on Android.** Host apps targeting minSdk 24 must enable `coreLibraryDesugaring` and add `desugar_jdk_libs` 2.1.5+ in the host app module. minSdk stays at 24. 4. Roll back to the prior SDK version if your Android host app cannot yet meet the Kotlin 2.2 / desugaring requirements above. iOS-only apps are unaffected and require no action. ### Technical Details * Android support is delivered via native `com.kustomer.chat:ui` 4.6.0, wrapped for React Native. * PubNub cost-cut work is delivered in two waves; the fixes and improvements above are Wave 2 (channel-list probe removal, reconnect-timer removal, soft PAM refresh, conditional history catch-up, quieter expected-disconnect recovery, push early-return) — Android only. ### 6.1.0 **Release Date:** September 18, 2026 ### Summary Adds official iOS 27 support, fixes an example app launch issue on iOS 27, and removes dead pre-iOS 15 code paths. ### New & Fixed * **Added:** Official iOS 27 support. The native Chat SDK now supports iOS 15.0 through iOS 27. * **Fixed:** \[iOS] The native example/host app failed to launch correctly on the iOS 27 SDK. It now adopts the UIScene lifecycle. ### Behavioral Improvements * No user-visible behavior changes in this release. APIs changed: **NO**. ### Recommended Action * Integrators building against the iOS 27 SDK should build with **Xcode 27+**. * Update your Podfile to **KustomerChat 8.1.0** (CocoaPods). Android is unaffected and remains on `com.kustomer.chat:ui` 4.5.6. * No public JS API changes — no code changes required beyond the CocoaPods version bump on iOS. ### Technical Details * Removed dead pre-iOS 15 compatibility branches inside native 8.1.0. The SDK collapses unreachable pre-iOS 15 availability fallbacks now that the deployment floor is iOS 15.0. Intentional iOS 16+/17+/18+/liquid-glass gates remain unaffected. ## 6.0.0 **Release Date:** September 17, 2026 ### Summary Raises the iOS minimum deployment target to 15.0 and fixes Chat identity handling so sessions no longer leak across login/logout. ### New & Fixed * **Fixed:** Chat identity now rebinds correctly after login and logout on iOS. Chat no longer retains the Support Center widget or a local conversation session from the previous identity. * **Fixed:** The `AuthProvider` logout Promise now stays pending until native logout and identity rebind finish, and rejects if either step fails — matching the primary Chat logout bridge's behavior. ### Behavioral Improvements * **iOS:** After an identity change, the next Chat presentation starts under the new identity instead of continuing a previous session. APIs changed: **NO**. No new fields added. ### Recommended Action * **Breaking:** Raise your app's (or Podfile's) iOS deployment target to 15.0 or later _before_ upgrading to this release. Apps still targeting iOS 14 cannot adopt 6.0.0. * Wait for login/logout to fully resolve before opening Chat, so the SDK binds to the correct identity. * Confirm no remaining app dependencies require iOS 14, since support for it has been removed. ### Technical Details * **Removed:** iOS 14 as a supported minimum deployment target. ### 5.3.8 **Release date:** 08/21/2026 Fixes an iOS crash that could occur when users opened chat history with many conversations while message previews were still loading. ### What’s fixed - **iOS conversation list crash:** Opening the built-in conversation list no longer crashes when loading chat history with many conversations while message previews are still loading. ### Behavioral changes Users can open the built-in conversation list on iOS without encountering this crash in the affected scenario. **API changes:** No React Native API changes. ### Recommended action Upgrade to **@kustomer/chat-react-native\@5.3.8** or later if your React Native app: - Uses the built-in chat UI on iOS. - Has experienced crashes when users open the conversation list. After upgrading, reinstall the iOS CocoaPods dependencies. ### Technical details Native SDK versions: - iOS: **KustomerChat 7.2.8** - Android: **com.kustomer.chat:ui 4.5.5** (unchanged) Upgrade the React Native package: ``` npm install @kustomer/chat-react-native@5.3.8 ``` For iOS, reinstall CocoaPods dependencies: ``` cd ios pod install ``` ### 5.3.7 ### **Fixed** - \[iOS] We fixed an iOS issue where a customer’s initial message could be missing when first opening an AI-assisted chat. Initial messages now appear immediately, while assistant greetings continue to display without duplication. No API or integration changes are required. ### **Native SDK Versions** - iOS: Kustomer Chat SDK 7.2.7 - Android: Kustomer Chat SDK 4.5.5 (unchanged) ### **Upgrade** Upgrade the React Native package: ``` npm install @kustomer/chat-react-native@5.3.7 ``` For iOS, reinstall CocoaPods dependencies after upgrading: ``` cd ios pod install ``` ### 5.3.6 Android apps can now use existing React Native history filters and session listener events. This release also improves cross-platform behavior and fixes callback compatibility. **Release date:** 2026-07-13 ### New and fixed #### For customers and product owners - Filter Android chat history by **All**, **Open**, **Closed**, or **Unread** status. - View clearer filter counts and localized filter labels in the built-in chat history. - See a filtered empty state when no loaded conversations match the active filters. - Receive unread-count updates on the iOS main thread for safer interface updates. #### For developers and integrators - Enable the existing React Native history status filter menu on Android. - Set a default history status filter on Android. - Apply custom history filter clauses on both iOS and Android. - Receive opened-session events and session custom-attribute updates from Android. - Receive compatible Android event payloads for date and nested custom-attribute values. - Resolve the Android example app with a gesture-handler version compatible with its React Native version. ### Behavioral improvements - The Android conversation list now includes **All**, **Open**, **Closed**, and **Unread** filters. - Android filter counts and labels more closely match the iOS and web implementations. - Android displays a filtered empty state when active filters exclude all loaded conversations. - Android orders sessions more consistently with the iOS SDK. - Android converts date values to ISO 8601 strings before emitting React Native events. - Android converts nested custom values to JSON strings before emitting React Native events. - iOS delivers total and per-conversation unread-count callbacks on the main thread. **API changes:** No new React Native API surface is documented in this release. Existing history filter options and session listener events now work on Android. ### Benefits to your app - Provide a more consistent chat history experience across Android, iOS, and web. - Let customers find relevant conversations more quickly. - Update iOS interface elements safely from unread-count callbacks. - Process Android custom-attribute events with predictable string formats. - Use the same React Native integration patterns across supported mobile platforms. ### Testing and compatibility | Platform | Native artifact | Version | | -------- | ------------------------------------- | ------- | | iOS | `KustomerChat` through CocoaPods | `7.2.6` | | Android | `com.kustomer.chat:ui` through Gradle | `4.5.5` | - The Android example app uses a gesture-handler dependency compatible with its React Native version. - These notes do not include supported operating-system versions or a test matrix. - Confirm supported platform versions and completed testing before publication. ### Recommended action - Upgrade to React Native SDK v5.3.6 when your Android app needs chat history filters or session listener events. - Upgrade when your iOS app updates interface elements from unread-count callbacks. - Test custom Android event handling if your integration parses date or nested custom-attribute values. - Verify the default history filter and empty-state behavior before releasing the update. ### Technical details - Android native artifact: `com.kustomer.chat:ui` v4.5.5. - iOS native artifact: `KustomerChat` v7.2.6. - The Android example app enables the history status filter menu by default and starts with the **All conversations** filter. ### 5.3.5 **Release date:** 2026-07-09 This release improves the iOS chat layout so long and formatted messages display their complete text. ### New and fixed #### For customers and product owners - Customers can read the complete text of long chat messages on iOS. - Formatted messages now expand correctly in additional message layouts. #### For developers and integrators - The React Native SDK includes iOS SDK v7.2.5. - The release extends the long-message layout fix introduced in iOS SDK v7.2.4. ### Behavioral improvements - Message bubbles expand to fit long message content. - The updated layout handles additional message types, including formatted messages. - Customers no longer see affected messages cut off in the built-in iOS chat interface. **API changes:** No. ### Benefits to your app - Display complete customer and agent messages. - Improve readability for long or formatted content. - Receive the fix without changing your integration. ### Testing and compatibility | Platform | Native artifact | Version | | -------- | ------------------------------------- | ------- | | iOS | `KustomerChat` through CocoaPods | `7.2.5` | | Android | `com.kustomer.chat:ui` through Gradle | `4.5.4` | - These notes do not include supported operating-system versions or completed test coverage. - Confirm compatibility and testing details before publication. ### Recommended action - Upgrade to React Native SDK v5.3.5 if your iOS users receive long or formatted chat messages. - Test representative plain-text and formatted messages before releasing the update. - No migration steps are required. ### Technical details - iOS SDK v7.2.4 introduced the initial long-message layout fix. - iOS SDK v7.2.5 extends the fix to additional message layouts. ### 5.3.4 **Release date:** 6/22/2026 ### Brief Summary This release adds iOS chat history filtering options and session listener events to the React Native SDK. ### New & fixed - Added iOS chat history filtering — Developers can configure which iOS conversations appear in chat history. - Added iOS session listener events — Apps can listen for opened sessions and session custom attribute updates. - Fixed malformed custom filters — The SDK rejects invalid `customHistoryFilter` values instead of applying partial filters. - Fixed invalid runtime option handling — `configure()` safely handles invalid option values, including `null`. ### Behavioral changes - API changes: **Yes**. - New `KustomerChat.configure` options: - `enableHistoryStatusFilter` - `historyStatusFilter` - `customHistoryFilter` - New `KustomerEventEmitter` events: - `onSessionOpened` - `onSessionCustomAttributesUpdated` - `onSessionOpened` now includes conversation `custom` attributes. - `onSessionOpened` includes `customAttributesOutsideActiveFilter` when a custom history filter is active. - Malformed `customHistoryFilter` values are rejected entirely. - Invalid runtime option values do not break `configure()`. ### Benefits to your app - Show users a more relevant iOS chat history by filtering conversations by status. - Scope iOS conversation history with custom key/value filters, such as region or account segment. - React to session changes when a session opens or custom attributes update. - Avoid partial filtering behavior when custom filter values are malformed. ### Testing & compatibility - React Native SDK: `@kustomer/chat-react-native@5.3.4`. - iOS native SDK: `KustomerChat` 7.2.3. - Android native SDK: `com.kustomer.chat:ui` 4.5.4. - iOS: Includes new history filtering options and session listener events. - Android: No new Android-specific behavior in this release. - Backward compatibility: Existing configuration calls continue to work. ### Recommended action Upgrade to `@kustomer/chat-react-native@5.3.4` if your app needs iOS chat history filtering or session listener events. Migration checklist: 1. Update to `@kustomer/chat-react-native@5.3.4`. 2. Reinstall JavaScript dependencies. 3. Run `pod install` in your iOS project. 4. Add the new iOS filtering options to `KustomerChat.configure`, if needed. 5. Add listeners for `onSessionOpened` or `onSessionCustomAttributesUpdated`, if needed. 6. Test chat history filtering with valid and malformed `customHistoryFilter` values. Rollback plan: Revert to the previous React Native SDK version and run `pod install` again. Monitor for unexpected chat history visibility, listener callback behavior, and rejected custom filter values after upgrading. ### Technical details #### Configure iOS chat history filtering ```typescript import { KustomerHistoryStatusFilter } from '@kustomer/chat-react-native'; KustomerChat.configure(apiKey, { enableHistoryStatusFilter: true, historyStatusFilter: KustomerHistoryStatusFilter.open, customHistoryFilter: [{ key: 'region', value: 'us' }], }); ``` ### 5.3.3 **Release date:** 2026-06-18 ### Brief Summary React Native SDK now supports improved chat history filtering, more reliable conversation custom attributes, and stability fixes for iOS and Android. ### New & fixed #### Customer-facing updates - **Added iOS chat history status filtering** — Apps can let users filter chat history by **All**, **Open**, **Closed**, or **Requires attention**. - **Added iOS custom attribute filtering** — Apps can filter chat history by conversation custom attribute key/value pairs. - **Improved conversation custom attributes** — CRM custom fields on conversations are more reliable in chat history and stay in sync during live session updates. - **Fixed cached conversation crashes on iOS** — Opening a cached conversation from a deep link, push notification, or in-app navigation no longer causes a crash. - **Fixed Android navigation crashes** — Apps that use bottom navigation can move between the conversation list and chat more reliably. #### Developer-facing updates - **Added** `KustomerOptions.enableHistoryStatusFilter` — Enables the optional chat history status filter on iOS. - **Added** `KustomerOptions.historyStatusFilter` — Sets the default chat history status filter on iOS. - **Added** `KustomerClient.setHistoryStatusFilter(_:)` — Changes the chat history status filter at runtime on iOS. - **Added** `KustomerOptions.customHistoryFilter` — Applies in-memory chat history filtering by custom attribute key/value pairs on iOS. - **Added** `KustomerClient.setCustomHistoryFilter(_:)` — Changes the active custom attribute filter at runtime on iOS. - **Added** `KUSChatListener.onSessionOpened(session:customAttributesOutsideActiveFilter:)` — Notifies the app when a session opens with custom attributes outside the active custom filter. ### Behavioral improvements - **iOS chat history filter behavior** — When `KustomerOptions.enableHistoryStatusFilter` is enabled, the chat history screen can show the **All**, **Open**, **Closed**, and **Requires attention** filter options. - **iOS default filter behavior** — Apps can set the default status filter with `KustomerOptions.historyStatusFilter`. - **iOS runtime filter behavior** — Apps can update the status filter at runtime with `KustomerClient.setHistoryStatusFilter(_:)`. - **iOS custom filter behavior** — Apps can filter chat history in memory by custom attribute key/value pairs with `KustomerOptions.customHistoryFilter` and `KustomerClient.setCustomHistoryFilter(_:)`. - **Combined iOS filter behavior** — Custom attribute filtering works with status filtering. - **iOS conversation count behavior** — When the status filter is enabled, the chat history header can show a matching conversation count in the format `x of y`. - **iOS session listener behavior** — `KUSChatListener.onSessionOpened(session:customAttributesOutsideActiveFilter:)` fires when a session opens with custom attributes outside the active custom filter. - **iOS input bar behavior** — The message input bar updates correctly when the last row in a thread changes without a full reload. - **iOS chat history performance** — Returning to chat history with many conversations causes fewer UI hitches. - **iOS conversation re-entry behavior** — The input bar state is more reliable when users quickly open and leave a conversation. - **Android bottom navigation behavior** — Chat teardown and listener handling are more reliable when chat is embedded with bottom navigation, including when `KusMainActivity` is re-initialized through `onNewIntent`. ### Benefits to your app - Give iOS users more control over chat history by exposing status-based filtering. - Build custom iOS chat history views that filter conversations by CRM custom fields. - Reduce crash risk when users open conversations from deep links, push notifications, in-app navigation, or Android bottom navigation. - Improve perceived performance for users with large chat histories. - Keep conversation metadata more consistent during active chat sessions. ### Testing & compatibility | Platform | Native artifact | Version | | -------- | ------------------------------- | ------- | | iOS | `KustomerChat` (CocoaPods) | `7.2.3` | | Android | `com.kustomer.chat:ui` (Gradle) | `4.5.4` | - **API changes:** This release adds iOS chat history filter options and the `KUSChatListener.onSessionOpened(session:customAttributesOutsideActiveFilter:)` callback. - **Breaking changes:** None identified. - **Performance:** iOS chat history previews load more efficiently for large histories. Returning to chat history with many conversations causes fewer UI hitches. ### Recommended action - Upgrade if your app uses chat history on iOS and needs status or custom attribute filtering. - Upgrade if your app opens conversations from deep links, push notifications, or in-app navigation. - Upgrade if your Android app embeds chat with bottom navigation or uses AndroidX Navigation `2.9.x` or later. - Monitor crash reporting after release for cached conversation opens, active chat threads, and Android bottom-navigation flows. ### Migration checklist - Update iOS to `KustomerChat` `7.2.3`. - Update Android to `com.kustomer.chat:ui` `4.5.4`. - Enable `KustomerOptions.enableHistoryStatusFilter` if you want to show the iOS chat history status filter. - Set `KustomerOptions.historyStatusFilter` if you want a default iOS status filter. - Use `KustomerClient.setHistoryStatusFilter(_:)` to update the iOS status filter at runtime. - Use `KustomerOptions.customHistoryFilter` or `KustomerClient.setCustomHistoryFilter(_:)` to apply iOS custom attribute filtering. - Implement `KUSChatListener.onSessionOpened(session:customAttributesOutsideActiveFilter:)` if your app needs to detect opened sessions with custom attributes outside the active custom filter. ### ~~Technical details~~ #### ~~Added~~ - **~~iOS:~~**\~\~ Added optional chat history status filtering for **~~All~~**, **~~Open~~**, **~~Closed~~**, and **~~Requires attention~~**.\~\~ - **~~iOS:~~**\~\~ Added optional in-memory custom attribute filtering by conversation custom attribute key/value pairs.\~\~ - **~~iOS:~~**\~\~ Added `~~KUSChatListener.onSessionOpened(session:customAttributesOutsideActiveFilter:)~~`.\~\~ - **~~iOS and Android:~~**\~\~ Improved availability and synchronization of session `~~custom~~` attributes on conversations.\~\~ #### ~~Fixed~~ - **~~iOS:~~**\~\~ Fixed a crash when opening a cached conversation through a deep link, push notification, or in-app navigation.\~\~ - **~~iOS:~~**\~\~ Fixed message input bar updates when the last row in a thread changes without a full reload.\~\~ - **~~iOS:~~**\~\~ Reduced chat history UI hitches when navigating back to a large conversation list.\~\~ - **~~iOS:~~**\~\~ Fixed intermittent incorrect input bar visibility when quickly re-entering a conversation.\~\~ - **~~Android:~~**\~\~ Fixed a `~~ConcurrentModificationException~~` when repeatedly moving between the conversation list and a conversation, especially in host apps using AndroidX Navigation `~~2.9.x~~` or later.\~\~ - **~~Android:~~**\~\~ Fixed an `~~IndexOutOfBoundsException~~` when inserting the **~~new messages~~** marker in the active chat thread under edge conditions, including when the previous message list was empty or out of sync with the rebuilt list.\~\~ #### ~~Improved~~ - **~~iOS:~~**\~\~ Chat history message previews load more efficiently for large histories.\~\~ - **~~iOS:~~**\~\~ Unread badges render more cleanly, and spacing between the header and conversation list is improved.\~\~ - **~~Android:~~**\~\~ Bottom-navigation chat flows have more reliable teardown and listener handling when `~~KusMainActivity~~` is re-initialized, including through `~~onNewIntent~~`.\~\~ ### 5.3.2 **Release date: 2026-06-11** ### Summary Improves Firebase Cloud Messaging reliability by routing incoming data messages through the same native bridge used for push token registration. ### New & fixed - Fixed inconsistent handling of Firebase Cloud Messaging data messages. - Fixed native bridge mismatches that could cause `onRemoteMessage` failures in some production environments. - Unified push token registration and message handling paths. ### Behavioral improvements - Incoming FCM data messages now use the same native bridge implementation as token registration. - Message handling behavior is more consistent across production builds. - Foreground notification processing is more reliable. ### Benefits to your app - Reduces push notification delivery inconsistencies. - Improves reliability of foreground FCM message handling. - Simplifies troubleshooting by using a single native bridge path. ### Recommended action - Upgrade to `@kustomer/chat-react-native@5.3.2`. - Reinstall JavaScript dependencies after upgrading. - Run `pod install` or Gradle sync only if your native dependencies differ from the v5.3.1 pinned versions (React Native version 0.63, supporting up to 0.73. Versions 0.74 and 0.75 are currently in experimental support, and 0.76 is not supported). - Verify foreground FCM message handling when using `@react-native-firebase/messaging`. ### Technical details - `KustomerChat.configure` now routes FCM data messages through the same native bridge used for push token registration. - Removes divergent code paths that could cause bridge communication failures. - Native SDK dependency versions remain: - iOS Chat SDK 7.2.1 - Android Chat SDK 4.5.1 ## 5.3.0 **Release date:** 2026-04-21 ### Summary Bumps native SDK dependencies and fixes CI issues, ensuring consistent history behavior across platforms. ### New & fixed - Fixes CI failures — resolves `npm ci` errors caused by lockfile mismatch. - Ensures consistent history experience — aligns iOS and Android SDK versions. - Improves dependency reliability — full lockfile regeneration prevents install issues. ### Behavioral improvements - Native SDK versions updated: - iOS: 7.2.0 - Android: 4.5.0 - No changes to JavaScript API behavior. - History UI behavior now matches native SDK parity. - API changes: NO JavaScript API changes. ### Benefits to your app - Stable CI/CD pipelines with consistent dependency installs. - Unified behavior across iOS and Android. - Reduced risk of platform-specific discrepancies. ### Testing & compatibility - Verified with `npm ci`, iOS CocoaPods, and Android Gradle. - Backward compatible with existing integrations. - Example app updated to reflect new native versions. ### Recommended action - Upgrade to v5.3.0 if you rely on CI stability or cross-platform consistency. - Run `npm install` or `yarn install` after upgrading. - Run `pod install` (iOS) and Gradle sync (Android). - Confirm native SDK versions resolve correctly. ### Technical details - Updated `package.json` to pin native SDK versions (iOS 7.2.0, Android 4.5.0). - Regenerated `package-lock.json` for dependency consistency. - Updated Podspec and Gradle configs to read from unified version source. ## 5.2.5 **Release date:** 2026-04-20 ### Brief summary Bumps native SDK versions to enable structured link preview enhancements without changing the JavaScript API. ### New & fixed - Updates native SDK dependencies — enables structured link preview support. - No JavaScript API changes — existing integrations remain stable. ### Behavioral improvements - Link preview behavior depends on updated native SDKs. - No changes to JS layer behavior. - API changes: NO ### Benefits to your app - Access to improved link previews without code changes. - Unified native version management via package configuration. ### Testing & compatibility - Compatible with existing React Native integrations. - Requires native SDK availability (iOS 7.1.5, Android 4.4.4). - No performance impact. ### Recommended action - Upgrade to 5.2.5 if you want improved link previews. - Run `npm install` or `yarn install`. - iOS: run `pod install` and verify `KustomerChat 7.1.5`. - Android: sync Gradle and verify `com.kustomer.chat:ui:4.4.4`. - Validate link preview rendering. ### Technical details - Native versions defined in `package.json`: - iOS: 7.1.5 - Android: 4.4.4 - Podspec and Gradle read from a single source of truth. - No changes to JS API surface. ## 5.2.4 **Release date:** 2026-03-13 ### Summary Fixes duplicate AI greeting behavior on iOS and updates native dependencies to improve message accuracy and input stability. ### New & Fixed - Prevents duplicate AI greeting messages on iOS — existing conversations no longer re-inject proactive messages. - Ensures clean message payloads — user replies no longer include duplicated automation messages. - Improves iOS input handling — removes `NextGrowingTextView` dependency in the underlying native SDK. ### Behavioral Improvements - **Automation message injection (iOS)** - **Before:** Opening an existing conversation could re-inject AI proactive messages into `initialMessages`. - **After:** Automation messages are added only when starting a new conversation (`value == nil`). - **Impact:** Existing conversations load without duplicate greetings or message duplication. - **Message composition (iOS)** - User messages now include only intended content, without duplicated automation context. - **Input behavior (iOS)** - Input height dynamically adjusts using native `UITextView` (via underlying iOS SDK). - Improved layout stability during text input. - **API changes:** NO ### Benefits to your app - More reliable conversation history when reopening chats. - Accurate message payloads for analytics and automation workflows. - Improved input performance on iOS devices. - Seamless upgrade with no React Native API changes. ### Testing & Compatibility - React Native version `5.2.4` includes: - iOS SDK `7.1.4` - Android SDK `4.4.3` - Fix validated through native iOS unit tests. - Backward compatible with existing React Native integrations. - No breaking changes identified. ### Recommended Action - Upgrade to v5.2.4 if you: - Use AI Agent proactive greetings. - Support reopening existing conversations on iOS. - No migration steps required. - Validate: - Conversation reopen behavior on iOS - Message send payloads - Monitor for unexpected automation message behavior after upgrade. ### Technical Details - **Fixed (iOS via native SDK)** - React Native consumes updated iOS SDK (`7.1.4`). - Automation messages from `AutomationProvider.getInitialAutomationMessages()`: - Included only when `value == nil` - Excluded when `value != nil` - **Native dependency updates** - iOS: `7.1.4` - Android: `4.4.3` - **iOS Input Refactor (via native SDK)** - Removed `NextGrowingTextView`. - Replaced with `UITextView` with explicit min/max height constraints. ## 5.2.3 **Release date:** March 9, 2026 ### Summary Improves Android chat launching behavior, fixes iOS conversation and attachment issues, and increases total attachment upload size to 50MB. ### New & Fixed - **Android — Chat launches in the current app task.**
Chat now opens using the host Activity when available, preventing duplicate entries in the Recent Apps list. - **iOS — Conversations no longer appear to hang during PubNub read failures.**
The SDK now properly handles read failures to prevent conversations from appearing indefinitely stalled. - **iOS — Attachments no longer create unintended new conversations.**
Uploading an attachment to an existing conversation now correctly attaches to the active thread. - **iOS — Larger attachment uploads supported.**
The SDK now supports up to **50MB total attachment size** per message batch. ### Behavioral Improvements - **Android task behavior updated.**
When a host Activity exists, the SDK launches chat within the same task. If unavailable, the SDK falls back to the Application context with `FLAG_ACTIVITY_NEW_TASK` to prevent launch crashes. - **New configuration option for attachment limits (iOS).**
Added `maxChatAttachmentTotalMB` in `KustomerOptions`. Default value is **50MB**. ### Benefits to your app - Prevents duplicate Android app entries when opening chat. - Improves reliability when PubNub read events fail. - Allows larger file uploads in customer conversations. - Ensures attachments remain associated with the correct conversation thread. ### Testing & Compatibility - **iOS SDK version:** 7.1.3 - **Android SDK version:** 4.4.3 ### Recommended Action - Upgrade if your app experiences duplicate task entries when launching chat on Android. - Upgrade if users experience stalled conversations after PubNub read failures. - Update any attachment workflows to account for the new **50MB total upload limit** if applicable. ### Technical Details - Android launch behavior now prioritizes the host Activity as the launch context. - If no Activity is available, the SDK launches using the Application context with `FLAG_ACTIVITY_NEW_TASK`. - New iOS configuration field:
`KustomerOptions.maxChatAttachmentTotalMB` ## 5.2.2 ### Summary Adds dynamic conversation titles and introduces a legacy preview configuration flag. ### New & Fixed - **Display dynamic conversation titles** — Chat header and conversation list show an optional session name when present. - **Control preview behavior** — New `useLegacyConversationPreview` configuration option restores previous title behavior when enabled. ### Behavioral Improvements - When `session.name` exists, the SDK renders it as Line 1 in: - Chat header - Conversation list row - Line 2 continues to display the last message preview. - Title resolution order is now: 1. `session.name` 2. Title fallback 3. Last responder display name - Session name updates received via `kustomer.app.chat.session.update` immediately update the UI. - When `useLegacyConversationPreview` is `true`, the SDK ignores `session.name` and uses legacy preview logic. **API Changes:** YES - Adds new configuration option: `useLegacyConversationPreview` (Boolean, default: `false`). No breaking changes. ### Benefits to your app - Aligns conversation titles with the Kustomer timeline. - Ensures real-time UI updates when conversation names change. - Provides a safe rollback option to preserve legacy UI behavior. - Maintains consistent behavior with native iOS (7.1.2) and Android (4.4.2) SDKs. ### Testing & Compatibility - Backward compatible. Default behavior enables dynamic session titles. - Setting `useLegacyConversationPreview: true` restores prior behavior. - Tested with native SDK versions: - iOS: 7.1.2 - Android: 4.4.2 - No performance impact observed. ### Recommended Action - Upgrade to v5.2.2 to support dynamic conversation titles. - If your app depends on legacy title formatting, enable: ```javascript KustomerChat.configure(apiKey, { useLegacyConversationPreview: true }) ``` - Verify header and conversation list behavior after upgrading. - Confirm analytics or UI logic does not assume static preview titles. ### Technical Details **Dynamic session name handling** The native SDKs (iOS 7.1.2 and Android 4.4.2) receive optional `session.name` via `kustomer.app.chat.session.update`. React Native reflects native resolution order: ``` session.name → title fallback → last responder display name ``` When a session update includes a name change, the UI updates immediately without requiring manual refresh. **Legacy preview configuration** New configuration option: ```javascript KustomerChat.configure(apiKey, { useLegacyConversationPreview: true }) ``` - Type: Boolean - Default: `false` - When `true`, ignores `session.name` and restores legacy preview title logic. - When `false`, enables dynamic session name resolution. ## 5.2.1 (v5.2.1) \*\*Release Date:\*\*2026-02-13 ### Brief summary Adds automatic URL link previews to iOS and Android chat messages (enabled by default). ### New & fixed (customer-facing) - Automatically renders rich link previews in chat messages that contain URLs. - Enabled by default on iOS and Android. - Supports multiple URLs per message. ### Behavioral changes - **Default behavior change:** Link previews render automatically for messages containing URLs. - Previews appear below the original message. - Multiple URLs generate multiple previews. - Feature can be disabled via configuration. - **API changes:** NO server API changes. ### Benefits to your app - Improves message clarity with rich previews (title, description, image). - Reduces need for users to open links to understand context. - Works automatically without additional integration. ### Testing & compatibility - iOS SDK version: 7.1.1 - Android SDK version: 4.4.1 - Backward compatible. - No server-side changes required. ### Recommended action Upgrade to v5.2.1 if you: - Want automatic URL previews in chat. - Are updating to iOS 7.1.1 or Android 4.4.1. - Want feature parity across mobile SDKs. To opt out: - iOS: Set `Kustomer.options.enableUrlUnfurling = false` - Android: Set `KustomerCoreOptions.enableUrlUnfurling = false` or `KustomerOptions.enableUrlUnfurling = false` No migration steps required. ### Technical details The SDK listens for URL unfurl events and appends preview metadata to the associated message. - Events trigger when a message contains a URL. - Preview metadata includes title, description, image, and link. - Preview rendering is client-side. - No message duplication occurs. - No impact on unread counts, delivery status, or read receipts. Configuration examples for opting out: **iOS** ```swift let options = KustomerOptions() options.enableUrlUnfurling = false ``` **Android** ```kotlin val options = KustomerCoreOptions() options.enableUrlUnfurling = false ``` ## 5.2.0 **Release date:** February 16, 2026 ## Summary ### Added - \[iOS] Added `Kustomer.handoff()` method to import conversation history from external AI systems into Kustomer's chat - \[iOS] Added `KUSHandoffMessage` model (public) for representing messages in handoff requests - \[iOS] Added `KUSHandoffMessageDirection` enum (public) for message direction (inbound/outbound) - \[Android] Added `Kustomer.handoff()` method to import conversation history from external AI systems into Kustomer's chat - \[Android] Added `HandoffParameters` model (public) for handoff request parameters (active, from, messages, optional brand/externalId/lang) - \[Android] Added `HandoffMessage` model (public) for representing messages in handoff requests (date, direction, body) - \[Android] Added `HandoffMessageDirection` enum (public) for message direction (inbound/outbound) ### Native SDK Versions - iOS: 7.1.0 - Android: 4.4.0 ## 5.0.0 **Release date:** January 12, 2026 ## Summary Removes iOS 13 support, fixes iOS 26+ layout issues, and improves Knowledge Base navigation and UI behavior when liquid glass is enabled. ### Fixed - \[iOS] Fixed iOS 26.0+ compatibility issues with tab bar navigation and layout constraints - \[iOS] Fixed back button title display in Knowledge Base categories when liquid glass is enabled - \[iOS] Fixed layout constraints in Chat History view controller to properly handle tab bar visibility state ### Improvements - \[iOS] Updated dependency versions to latest stable releases: - JWTDecode: 3.0.1 → 3.3.0 - ReachabilitySwift: 5.2.3 → 5.2.4 - \[iOS] Improved iOS 26.0+ compatibility with liquid glass design features - \[iOS] Improved Knowledge Base Article Viewer with custom header view for liquid glass enabled state ### Breaking - \[iOS] Removed iOS 13 support - changed minimum deployment target to >= iOS 14 ### Native SDK Versions - iOS: 7.0.0 - Android: 4.3.1 See our [migration guide for details on migrating from iOS 6.x.x](https://developer.kustomer.com/chat-sdk/changelog/ios#migrating-from-6xx-to-700) ## 4.2.1 **Release date:** January 5, 2026 ## Summary Fixes cases of missed messages after background or network interruptions, restores conversation ordering on Android, and ensures recovered messages notify all listeners. ### New & fixed **Reliability & Recovery** - Fixed a cross-platform issue where messages could be sent but not received after backgrounding or network interruptions. - SDKs (iOS & Android) now automatically verify and restore PubNub subscriptions when the app foregrounds, when connectivity returns, or during scheduled pre-expiry checks. - Recovered messages now trigger `onChatMessageReceived` callbacks for all registered listeners (Core SDK and UI SDK). **Android-specific fixes** - Restored conversation sort order (regression from v4.1.1): unread first, then most recent. - Fixed `observeUnreadCount()` not firing immediately after `Kustomer.login()` on Android. **Native SDK versions** iOS: 6.3.1 Android: 4.3.1 - \[iOS|Android] Fixed PubNub connection issues that prevented message reception after background periods or network interruptions - \[Android] Regression from `v4.1.1`, where chat history screen loses sort order of conversations - \[Android] Issue where `observeUnreadCount()` was not working immediately after a `Kustomer.login()` ### Behavioral improvements - Recovered messages are delivered via the same listener callbacks as real-time messages. - Recovered messages may be delivered in short bursts (small spacing) to avoid OS notification suppression. - In-app notifications are suppressed if a push notification for the same message was already shown. - No breaking public API changes. ### Benefits for your app - No missed inbound messages after backgrounding or flaky networks. - Custom UIs receive consistent callbacks for recovered messages. - Conversation lists display correctly on Android. - Reduced duplicate notifications and improved UX. ### Testing & compatibility - Unit and integration tests updated for recovery, reconnection, and sorting scenarios. - Platforms: React Native bridge uses native iOS 6.3.1 and Android 4.3.1 implementations. - No migration steps required for consumers. ### Recommended action Upgrade to v4.2.1 if you: - See missed messages after backgrounding or network changes. - Build custom UIs on the Core SDK. - Rely on correct conversation ordering (Android). - Need robust behavior across iOS and Android. ## Technical Details ### Automatic PubNub Reconnection (EUX-921) **Problem Statement:** When a user's app using the React Native SDK remained in the background for an extended period, the PubNub connection for subscriptions became broken when the app returned to the foreground. Users could send messages but could not receive them due to inactive subscriptions, creating a poor user experience where messages appeared to be sent but responses were not received. **Root Cause:** - PubNub connections may timeout or become stale after extended background periods - iOS terminates network connections after \~30 seconds in background (without special background modes) - Android's Doze mode and App Standby terminate network connections to conserve resources - While PubNub SDK has automatic reconnection configured, it may not detect stale connections immediately after background periods - The connection status may show connected but subscriptions may be broken/inactive - No proactive verification that subscriptions are active and receiving messages when app returns to foreground **Solution Approach:** The native SDKs now automatically verify and reconnect PubNub subscriptions when: 1. The app returns to foreground after being in the background 2. Network connectivity is restored (wifi or cellular) 3. Periodically via scheduled checks before token expiration **Implementation:** **iOS Implementation:** - Uses `ProcessLifecycleOwner` observer to detect app foreground events - Uses `Reachability` monitoring to detect network connectivity restoration - Verifies subscription health using `listChannels` as a lightweight proxy test - Automatically reconnects via `reauthAndResubscribe()` when subscriptions are inactive - Schedules periodic checks: 55 minutes on success, 5 minutes on error - Uses dedicated serial queue (`reconnectionCheckQueue`) with thread-safe flag management **Android Implementation:** - Uses `ProcessLifecycleOwner` observer to detect app foreground events - Uses `NetworkCallback` to detect network connectivity restoration - Verifies subscription health using `listChannels` API call as lightweight proxy test - Automatically reconnects via `initAndSubscribe()` when subscriptions are inactive - Schedules periodic checks: 55 minutes on success, 5 minutes on error - Uses coroutine scope with `Mutex` for thread-safe serial execution **Before (Problem State):** ```mermaid flowchart TD Start([App in Background]) --> Background[Background Period
~30+ seconds] Background --> OSKills[iOS/Android Kills Network
Connections] OSKills --> Foreground[App Returns to
Foreground] Foreground --> CheckStatus[Check Connection Status] CheckStatus --> StatusOK{Status =
Connected?} StatusOK -->|Yes| AssumeOK[Assume Connection OK
No Verification] StatusOK -->|No| Reconnect[PubNub Auto-Reconnect
May Not Detect Stale State] AssumeOK --> Problem[Problem: Subscriptions
Actually Inactive] Reconnect --> Problem Problem --> SendOK[User Can Send Messages] Problem --> ReceiveFail[User Cannot Receive
Messages] %% Styling - Dark mode safe grayscale palette classDef entry fill:#F8F9FA,stroke:#495057,stroke-width:2px,color:#000 classDef process fill:#E9ECEF,stroke:#6C757D,stroke-width:2px,color:#000 classDef decision fill:#CED4DA,stroke:#495057,stroke-width:2px,color:#000 classDef problem fill:#6C757D,stroke:#212529,stroke-width:3px,color:#fff classDef endState fill:#495057,stroke:#343A40,stroke-width:2px,color:#fff class Start entry class Background,OSKills,Foreground,CheckStatus,AssumeOK,Reconnect,SendOK process class StatusOK decision class Problem problem class ReceiveFail endState ``` **After (Solution State):** ```mermaid flowchart TD Start([SDK Initialized]) --> Trigger{Reconnection Trigger} %% Triggers Trigger -->|App Foreground| T1[ProcessLifecycleOwner
onStart / applicationWillEnterForeground] Trigger -->|Network Restored| T2[NetworkCallback / Reachability
wifi/cellular] Trigger -->|Scheduled Check| T3[Scheduled Timer
55 min success
5 min error] Trigger -->|Auth Tokens Fetched| T4[getPubNubAuthTokens
TTL-based scheduling] %% All triggers lead to checkAndReconnectIfNeeded T1 --> Check[checkAndReconnectIfNeeded] T2 --> NetworkHandler[Network Restoration Handler] T3 --> Check T4 --> Schedule[scheduleNextReconnectionCheck] Schedule --> Check NetworkHandler --> Check %% Check flow Check --> Queue{Already Checking?
isCheckingOrReconnecting} Queue -->|Yes| Skip1[Return Success
Skip - Already in Progress] Queue -->|No| SetFlag[Set Flag = true] %% Verify subscriptions SetFlag --> Verify[verifySubscriptionsActive
listChannels test] Verify --> VerifyResult{Result} %% Subscriptions active - done VerifyResult -->|Success: true| Skip2[Reset Flag = false
Schedule Next Check
55 min delay] Skip2 --> Complete1([Complete - Healthy]) %% Subscriptions inactive - reconnect VerifyResult -->|Success: false| Reconnect[Reconnect via
initAndSubscribe / reauthAndResubscribe] %% Other errors - reconnect VerifyResult -->|Failure: Error| Reconnect %% Reconnection path Reconnect --> ReconnectResult{Result} ReconnectResult -->|Success| ScheduleSuccess[Reset Flag = false
Schedule Next Check
55 min delay] ReconnectResult -->|Failure| ScheduleError[Reset Flag = false
Schedule Next Check
5 min delay] ScheduleSuccess --> Complete3([Complete - Reconnected]) ScheduleError --> Complete4([Complete - Retry Scheduled]) %% Styling - Dark mode safe grayscale palette classDef trigger fill:#F8F9FA,stroke:#495057,stroke-width:2px,color:#000 classDef decision fill:#E9ECEF,stroke:#6C757D,stroke-width:2px,color:#000 classDef action fill:#CED4DA,stroke:#495057,stroke-width:2px,color:#000 classDef skip fill:#DEE2E6,stroke:#343A40,stroke-width:2px,color:#000 classDef reconnect fill:#6C757D,stroke:#212529,stroke-width:3px,color:#fff classDef complete fill:#495057,stroke:#343A40,stroke-width:2px,color:#fff classDef verify fill:#CED4DA,stroke:#6C757D,stroke-width:2px,color:#000 class T1,T2,T3,T4 trigger class Queue,VerifyResult,ReconnectResult decision class SetFlag,Schedule,ScheduleSuccess,ScheduleError,NetworkHandler action class Skip1,Skip2 skip class Verify verify class Reconnect reconnect class Complete1,Complete3,Complete4 complete ``` **Key Features:** 1. **Foreground Detection:** - Automatically detects when app returns to foreground - Verifies PubNub subscription health immediately - Reconnects if subscriptions are inactive 2. **Network Connectivity Monitoring:** - Monitors network connectivity changes - Automatically triggers reconnection check when network is restored - Handles first network notification intelligently (skips if SDK already running, runs if SDK stopped) 3. **Scheduled Periodic Checks:** - Automatically schedules reconnection checks before token expiration - Success case: Checks every 55 minutes (before 1-hour token expiration) - Error case: Retries every 5 minutes for faster recovery from transient failures - Creates continuous cycle of proactive health monitoring 4. **Subscription Verification:** - Uses `listChannels` API call as lightweight proxy test - Single source of truth for all health check cases - Handles edge cases: not initialized, disconnected, logged out 5. **Thread Safety:** - Prevents overlapping reconnection attempts - Uses serial execution (iOS: serial queue, Android: coroutine scope with Mutex) - Thread-safe flag management prevents race conditions **Usage:** No code changes required - the SDK automatically handles reconnection. The functionality is internal and called automatically by the native SDKs when: - App returns to foreground - Network connectivity is restored - Scheduled periodic checks trigger **React Native:** ```typescript import { KustomerChat } from 'kustomer-chat-react-native'; // No code changes needed - reconnection is automatic await KustomerChat.configure({ // ... configuration }); // Messages will now be received reliably even after: // - Extended background periods // - Network connectivity interruptions // - App lifecycle changes ``` **Logging:** All reconnection operations are logged by the native SDKs for troubleshooting: **iOS:** - Uses LogV2 with `.pubnubRecovery` tag - Log levels: debug, warn, error **Android:** - Uses permanent production logging - Log levels: debug, error - Logs include method entry, state checks, decision logic, completion results, and error details **Memory Leak Fixes:** Fixed critical memory leaks by properly canceling timers: **iOS:** ```swift // From PubNubManager.swift deinit { // Cancel reconnection check timer to prevent memory leaks reconnectionCheckTimer?.cancel() } func disconnect() { // Cancel reconnection check timer to prevent reconnection attempts after disconnect reconnectionCheckTimer?.cancel() reconnectionCheckTimer = nil } ``` **Android:** ```kotlin // From KusPubnubService.kt // Reconnection check job is properly cancelled in resetPubnub() fun resetPubnub() { reconnectionCheckJob?.cancel() reconnectionCheckJob = null // ... reset logic } ``` **Benefits:** 1. **Improved Reliability**: Messages are always received, even after background periods or network interruptions 2. **Automatic Recovery**: No manual intervention required - SDK handles reconnection automatically 3. **Better User Experience**: Users can send and receive messages seamlessly without connection issues 4. **Proactive Health Checks**: Scheduled checks ensure connection health before token expiration 5. **Thread Safe**: Prevents race conditions and overlapping reconnection attempts 6. **Memory Safe**: Proper timer cleanup prevents memory leaks 7. **Cross-Platform Consistency**: Same behavior on both iOS and Android platforms **Technical Implementation Notes:** - **Simplified Approach**: Both platforms use a single `verifySubscriptionsActive()` test that covers all cases (not initialized, no connection, inactive subscriptions, healthy) - **Subscription Verification**: Uses `listChannels` API call as lightweight proxy test (PubNub SDK doesn't expose subscription state directly) - **Reconnection Strategy**: - iOS: Uses `reauthAndResubscribe()` which internally calls `initAndSubscribe()` - Android: Uses `initAndSubscribe()` directly - **Error Handling**: Errors are handled gracefully with automatic retry scheduling - **Edge Cases**: Handles not initialized, disconnected, logged out scenarios gracefully ### Conversation Sorting Fix (EUX-961) **Problem Statement:** In Android SDK v4.1.1, the Conversations screen displayed conversations in a seemingly random order instead of by date. The expected behavior is that conversations are ordered by date (most recent first) with unread messages at the top. **Root Cause:** **Regression History:** - **Commit:** `5b394631` - "fix: \[KDEV-62273] fix unread message count issues (#607)" - **Date:** March 22, 2024 - **First appeared in:** SDK v4.1.1 **What Changed:**
The commit changed conversation merging logic from: ```kotlin value.addAll(response.dataOrNull!!) _conversationList.postValue(KusResult.Success(value.distinctBy { it.id })) ``` To: ```kotlin val conversationsMap = _conversationList.value?.dataOrNull?.associateBy { it.id } ?.toMutableMap() ?: mutableMapOf() conversationList.forEach { conversationsMap[it.id] = it } val updatedConversations = conversationsMap.values.toList() _conversationList.postValue(KusResult.Success(updatedConversations)) ``` **Why It Was Changed:**
The change was made to fix duplicate conversation issues (KDEV-62273). The previous `distinctBy` approach always picked the first occurrence, which was often the older version. The Map approach correctly updates conversations with the latest version. **The Problem:**
While the Map approach fixed the duplicate issue, it introduced a new problem: `conversationsMap.values.toList()` does not preserve any meaningful order, causing conversations to appear in random order. **Additional Issues:** 1. **Order Loss During Merge:** Converting `Map.values.toList()` loses order 2. **No Re-sorting on Updates:** Sorting only occurred in the ViewModel when both conversations and settings were available, but updates via `addOrReplace()` didn't trigger re-sorting, causing the list order to become stale when conversations were updated via PubNub events 3. **Data Loss Bug:** The `addOrReplace()` function incorrectly handled `KusResult.Error` and `KusResult.Loading` states, causing silent data loss when real-time updates occurred during error states **Solution Approach:** Implemented sorting at the repository level to ensure conversations are always sorted correctly, regardless of how they're added or updated. **Solution Approach:** Implemented sorting at the repository level to ensure conversations are always sorted correctly, regardless of how they're added or updated. This ensures consistent sorting behavior across all conversation update paths. **Implementation Details:** 1. **New Sorting Utility** (`KusConversationSortUtil.kt`): - Created centralized sorting function that sorts by: 1. Unread message count (descending) - conversations with unread messages appear first 2. Last message timestamp (descending) - most recent conversations appear first - Handles null/zero values by treating them as 0 (oldest) - Extracted comparator (`conversationComparator`) for reusability - Single source of truth for sorting logic **Sorting Utility Implementation:** ```kotlin // From KusConversationSortUtil.kt internal object KusConversationSortUtil { /** * Comparator for sorting conversations: * 1. Unread message count (descending) * 2. Last message timestamp (descending) */ val conversationComparator = compareByDescending { it.unreadMessageCount } .thenByDescending { it.lastMessageAt ?: 0L } fun sortConversations(conversations: List): List { return conversations.sortedWith(conversationComparator) } } ``` 2. **Repository-Level Sorting** (`KusUiConversationRepository.kt`): - Updated `fetchConversations()` to sort conversations after merging via Map - Ensures correct order even when fetching multiple pages during pagination - Sorting applied immediately after merging to prevent order loss **Repository Implementation:** ```kotlin // After merging conversations via Map conversationList.forEach { conversationsMap[it.id] = it } // Sort conversations before posting to maintain correct order val updatedConversations = KusConversationSortUtil.sortConversations( conversationsMap.values.toList() ) _conversationList.postValue(KusResult.Success(updatedConversations)) ``` 3. **Real-time Update Sorting** (`KusLiveDataExtensions.kt`): - Updated `addOrReplace()` to re-sort after adding/replacing conversations - Critical for maintaining order when conversations are updated via PubNub events - Fixed data loss bug where Error/Loading states would cause silent data loss **Data Loss Bug Fix:**
The `addOrReplace()` function was updated to explicitly handle each `KusResult` state: - `KusResult.Success`: Preserve existing data - `null` (uninitialized): Use empty list - `Error` or `Loading`: Use empty list (prevents silent data loss) **Before (Data Loss Bug):** ```kotlin // ❌ Silent data loss when Error/Loading state val value = this.value?.dataOrNull?.toMutableList() ?: mutableListOf(conversation) // If value is Error/Loading, dataOrNull returns null, losing all conversations ``` **After (Fixed):** ```kotlin // ✅ Explicit state handling prevents data loss val value = when (val current = this.value) { is KusResult.Success -> current.data.toMutableList() null -> mutableListOf() else -> mutableListOf() // Error/Loading: use empty list } // Re-sort after adding/replacing val sortedValue = KusConversationSortUtil.sortConversations(value) this.postValue(KusResult.Success(sortedValue)) ``` **Before (Problem State):** ```kotlin // Conversations appeared in random order // Map.values.toList() doesn't preserve order val conversations = conversationsMap.values.toList() // Order was inconsistent and unpredictable ``` **After (Solution State):** ```kotlin // Conversations are always sorted correctly // 1. Unread messages first (by unread count descending) // 2. Then by last message timestamp (descending) val sortedConversations = conversations.sortedWith( compareByDescending { it.unreadCount } .thenByDescending { it.lastMessageTimestamp ?: 0L } ) ``` **Sorting Logic:** ```kotlin // From KusConversationSortUtil.kt fun sortConversations(conversations: List): List { return conversations.sortedWith( compareByDescending { it.unreadCount } .thenByDescending { it.lastMessageTimestamp ?: 0L } ) } ``` **Usage:** No code changes required - conversations are automatically sorted correctly in the Chat History screen. **React Native:** ```typescript import { KustomerChat } from 'kustomer-chat-react-native'; // Conversations are now automatically sorted correctly: // 1. Unread conversations appear first // 2. Conversations are sorted by most recent message timestamp // 3. Sorting is maintained during pagination and real-time updates await KustomerChat.openChatHistory(); // Conversations display in correct order ``` **Benefits:** - Conversations consistently sorted by date (most recent first) - Unread messages always appear at the top - Sorting maintained during pagination, real-time updates, and refresh operations - Edge cases handled correctly (null timestamps, empty lists, etc.) - Fixed data loss bug where Error/Loading states would cause silent data loss **Testing:** **Unit Tests:** - Added comprehensive unit tests for sorting utility (`KusConversationSortUtilTest.kt`) - All 6 unit tests passing: 1. `sortConversations sorts by unread count first` - Verifies unread messages appear first 2. `sortConversations sorts by lastMessageAt when unread count is same` - Verifies date sorting 3. `sortConversations treats null lastMessageAt as zero` - Verifies null handling 4. `sortConversations returns empty list for empty input` - Verifies edge case 5. `sortConversations returns single conversation as-is` - Verifies single item handling 6. `sortConversations prioritizes unread count over lastMessageAt` - Verifies priority logic **Integration Tests:** - Added bug reproduction tests in `KusUiConversationRepositoryTest.kt`: 1. **Merge/Pagination Bug Test:** Verifies conversations maintain sort order when merged via Map during pagination 2. **Real-time Update Bug Test:** Verifies conversations re-sort correctly when updated via `addOrReplace()` - Tests follow TDD approach: pass when bug exists, fail when bug is fixed (forcing expectations update) - All tests updated to verify correct sorted order after fix implementation **Test Coverage:** - Sorting logic: 6/6 unit tests passing - Repository integration: 2/2 bug reproduction tests passing - Edge cases: null timestamps, empty lists, single items all handled correctly **Performance Considerations:** - Sorting is O(n log n), which is acceptable for typical conversation list sizes (\< 1000 items) - Sorting happens at repository level, ensuring consistent behavior - No performance regression observed in testing ## 4.2.0 **Release date:** 12-05-2025 ## Summary ### Added - \[iOS] Added `markSessionAsRead(sessionId:completion:)` — marks all messages and CSATs in a conversation as `read`. - \[Android] Added `markSessionAsRead(conversationId: String)` — marks all messages and CSATs in a conversation as `read`. ### Deprecated - \[iOS] Deprecated `markRead(conversationId:)` and `markRead(conversationId:messageIds:satisfactionId:)`. - \[Android] Deprecated `markRead(conversationId, messageIds, satisfactionId)`. ### Native SDK Versions - iOS: 6.3.0 - Android: 4.3.0 ## Technical Details ### Deprecated Methods **iOS – Deprecated API:** ```swift // Deprecated - Use markSessionAsRead instead Kustomer.markRead(conversationId: "conv_123") Kustomer.markRead(conversationId: "conv_123", messageIds: ["msg_1", "msg_2"], satisfactionId: "sat_1") ``` **Android – Deprecated API:** ```kotlin // Deprecated - Use markSessionAsRead instead Kustomer.markRead("conv_123", listOf("msg_1", "msg_2"), "sat_1") ``` > Deprecated APIs remain functional but internally route to `markSessionAsRead`.
They will be removed in a future major release. ### New Methods **iOS – Recommended API:** ```swift // Marks all messages and CSATs as read Kustomer.markSessionAsRead(sessionId: "conv_123") { error in if let error = error { print("Error marking session as read: \(error)") } else { print("Session marked as read successfully") } } ``` **Android – Recommended API:** ```kotlin // Marks all messages and CSATs as read try { Kustomer.markSessionAsRead("conv_123") } catch (e: Exception) { Log.e("Kustomer", "Error marking session as read", e) } ``` **React Native:** This method will be exposed directly in a future React Native SDK release. For now, use the underlying native implementations if needed. ## 4.1.1 **Release date:** 11-24-2025 ## Summary ### Fixed - \[iOS] Fixed an issue where replying to an assistant conversation with an attachment could break the conversation flow. - \[Android] Improved performance when loading large conversation histories after login. ### Native SDK Versions - iOS: 6.2.1 - Android: 4.2.2 ## Technical Details ### iOS – Assistant Attachment Flow **Issue:**
Responding to an assistant conversation with an attachment could break the conversation flow. **Fix:**
Attachment responses in assistant conversations are now handled correctly.
No client-side code changes are required. ```swift Kustomer.openChatAssistant(assistantId: "assistant_123") { error in // Users can now respond with attachments without breaking the flow } ``` ### Android – Conversation Loading Performance **Issue:**
Customers with extensive chat history experienced long loading times after login. **Fix:**
Optimized conversation fetching and loading logic for large conversation histories.
No client-side code changes are required. ```kotlin Kustomer.login("customer_id") { success -> if (success) { // Conversations load more efficiently } } ``` **React Native:** ```typescript // Improvements are applied automatically await KustomerChat.login('customer_id'); ``` *** ## 4.1.0 **Release date:** 11-17-2025 ## Summary ### Added - \[iOS] Added `Kustomer.setup()` with a completion handler guaranteed to fire. - \[iOS] Added all supported languages to `KustomerLanguages`. ### Deprecated - \[iOS] Deprecated `Kustomer.configure()`. ### Native SDK Versions - iOS: 6.2.0 - Android: 4.2.1 ## Technical Details ### Deprecated Method **iOS – Deprecated API:** ```swift // Deprecated - Completion block may not fire Kustomer.configure(with: options) { // Completion handler not guaranteed to execute } ``` ### New Method **iOS – Recommended API:** ```swift // Completion handler guaranteed to fire Kustomer.setup(with: options) { error in if let error = error { print("Setup error: \(error)") } else { print("Setup complete") } } ``` ### Language Support Update **iOS:** ```swift let options = KustomerOptions() options.language = .english // .spanish, .french, .german, etc. Kustomer.setup(with: options) { error in } ``` **React Native:** ```typescript import { KustomerChat } from 'kustomer-chat-react-native'; await KustomerChat.configure({ language: 'en' // or 'es', 'fr', 'de', etc. }); ``` ## 4.0.3 **Release date:** 10-23-2025 ### Added - \[iOS]\[Android] Added Core SDK method `Kustomer.chatProvider.createConversation()`. ### Native SDK Versions - iOS: 6.1.2 - Android: 4.2.1 ## V 4.0.2 **Release date:** 10-17-2025 ### Fixed - \[Android] Crash that occurred sometimes when navigating to or from a KB article ### Native SDK Versions - iOS: 6.1.2 - Android: 4.2.1 ## v 4.0.1 Release date: 10-13-2025 ### Fixed - \[iOS] Crash from triggering `Kustomer.showKbArticle()` or `Kustomer.showKbCategory()` while on a Background Thread ### Native SDK Versions - iOS: 6.1.2 - Android: 4.2.0 ## v 4.0.0 Release date: 10-09-2025 See the [Migration guide](https://drive.google.com/file/d/1uRyDwA_hUFYMqmRShfpaoR_frqhUNYKx/view?usp=sharing) for this release. ### Fixed - \[Android] Bumped Android NDK to v28 and JDK to 17 and enabled new architecture in React Native. ### Native SDK Versions - iOS: 6.1.1 - Android: 4.2.0 ## v 3.1.2 **Release date:** 10-02-2025 ### Fixed - \[iOS] Fixed min target iOS SDK (from iOS 12 -> iOS 13) - iOS 12 support was removed in the native iOS SDK v6.0.0 ### Native SDK Versions - iOS: 6.1.1 - Android: 4.1.1 ## v 3.1.1 **Release date:** 10-02-2025 ### Fixed - \[iOS] An out-of-bounds crash could occur when updating the Chat History conversation. - \[iOS] Logic around how unread counts are calculated. - \[Android] Slow loading of the Chat History screen when the user has a lot of conversations. - \[Android] Slow loading ofthe Chat Conversation screen when the conversation has a lot of messages. ### Added - \[iOS] A clearer message under messages that indicates ifthe message is “Generated by AI”. ### Native SDK Versions - iOS: 6.1.1 - Android: 4.1.1 ## v3.1.0 **Release date**: 9-25-2025 ### Deprecated - (iOS) Removed iOS 12 support - changed minimum target to >= iOS 13 ### Added - (React Native) Added support for AI Agent teams on mobile both on iOS and Android - (Android) Added firstRead support to KusChatMessage, which enables unread count to consider firstRead status in calculations ### Fixed - (iOS) Fixed HTML entities that appeared in French translations - (Android|iOS) Updated German translation for "Chat" tab - (iOS) Conditions that prevented Chat History Screen from displaying most up to data state of conversations - (iOS) Scenario where a previously logged in user's active conversation count could prevent a new logged in user from creating a conversation ### Updated - Min iOS SDK: 13, updated from 12 . ### Native SDK Versions - iOS: 6.1.0 - Android: 4.1.0 ## v 3.0.1 **Release date:** 08-27-2025 ### Fixed (Android) Resolved an issue where calling openChatAssistant on Android SDK 24 to 35 crashes due to missing user data ## v 3.0.0 **Release date:** 07-14-2025 ### Added - (Android) Added support for Android SDK 35, including full edge-to-edge content rendering for a more immersive, modern UI experience. ### Fixed - (Android) Resolved an issue where the article WebView did not extend fully to the top of the bottom navigation, ensuring proper layout and visual continuity. ### Updated - Min Android SDK: 24 (Nougat), updated from 21. - Min JVM: 17 ### Native SDK Versions - iOS: 5.0.12 - Android: 4.0.0 ## v 2.7.2 **Release date:** 07-11-2025 ### Fixed - (iOS) Crash caused by malformed PubNub messages (that can be caused by bad network connections). - (iOS) Bug in Knowledgebase handling, where the SDK would fail to set the proper Knowledgebase if it encountered a badly formatted response from the API. ## v 2.7.1 **Release date:** 06-03-2025 ### Fixed - Compilation error in `openChatAssistant`, preventing iOS from building. ## v2.7.0 **Release date:** 05-16-2025 ### Added - (React Native) Added support for the [openChatAssistant method](https://developer.kustomer.com/chat-sdk/v2-React-Native/docs/kustomer-add-listener) for both Android and iOS. ### Fixed - (iOS) Crash caused by RACE condition during subscribe to PubNub channels. - (iOS) Bug where “No results” graphic would appear in KnowledgeBase, even if featured articles are present. - (iOS) KnowledgeBase will now use the custom domain supplied in the Kustomer app. - (iOS) Bug with `Hide chat history` setting, where (in some cases) a user could still see the back button from Chat and go to History. - (iOS) Issue with `Kustomer.openChatAssistant()` preventing follow-up assistant messages from appearing until the user re-enters the conversation. - (iOS) Wrong link color in outgoing message bubbles. - (Android) Fixed a `ClassCastException` that occurred when applying the dark theme to the article WebView based on device settings. - (Android) Fixed an issue where the article WebView failed to apply the dark theme on Android SDK versions 33 and higher. - (Android) Fixed a `ClassCastException` that occurred when applying the dark theme to the article WebView based on device settings. ### Improved - (iOS) Increased thread safety in multiple areas to reduce crashes caused by concurrency and race conditions. - (Android) The **New Conversation** button is now disabled when there is no internet connection. - (Android) The empty conversation view now properly reflects offline hours based on the business schedule. - (Android) Removed unnecessary `android.permission.CAMERA` permission. The SDK only launches external camera apps using `MediaStore.ACTION_IMAGE_CAPTURE` and does not directly access camera APIs. ### Native SDK Versions - iOS: 5.0.10 - Android: 3.4.4 ## v2.6.0 **Release date:** 1-30-2025 ### Added - (iOS) Added Xcode 16 & iOS 18 support. - (Android) Introduced new Kustomer color branding and logo updates. A new secondary color attribute has been added to control the appearance of selected bottom navigation elements and other secondary components. More details are available in [Customize colors](https://developer.kustomer.com/chat-sdk/v2-Android/docs/customize-colors-updated). - (Android) The Core Android SDK now includes consumer ProGuard files for release builds, ensuring the required ProGuard rules are automatically applied. This removes the need for adopters to manually create or maintain these rules going forward. ### Fixed - (iOS) Fixed an issue where chat history failed to load when a conversation was opened via a push notification while the app was not running. - (Android) Fixed an issue where chat history failed to load when a conversation was opened via a push notification while the app was not running. - (Android) Bug that caused two sequential multi-level list (MLL) steps in a conversational assistant to display the same options, even if they differ. - (Android) Bug that prevented the new callback named `afterCreateConversationOrError` in `startNewConversation` from executing when there is a failure in `describeConversation`. ### Improved - (iOS) Enhanced KustomerCore initialization logic to minimize the risk of race conditions and unintended side effects. - (Android) Enhanced KustomerCore initialization logic to minimize the risk of race conditions and unintended side effects. ### Native SDK Versions - iOS: 5.0.7 - Android: 3.4.1 ## v2.5.0 **Release date:** 11-15-2024 ### Deprecated - (React Native) Deprecated the `phones` and `emails` fields on `describeCustomer`. The new methods to use are `sharedPhones` and `sharedEmails`.This provides clearer visibility on updated customer attributes.
**Note:** The deprecated fields will continue to work and may be removed in a future version. ### Fixed - (React Native) Added experimental support for React Native 0.76. - This requires Bridgeless mode to be disabled. See the [Requirements page](https://developer.kustomer.com/chat-sdk/v2-React-Native/edit/requirements) for more information. - (Android) Fixed an issue where the navigation would reset after attachment selection in Android OS 33+ devices. - (Android) Fixed a SecurityException thrown when monitoring network status via system service callback. - (Android) Fixed an IndexOutOfBoundsException occurring when converting chat responses to chat messages for the UI. - (iOS) Resolved an issue with the startNewConversation method callback, which previously did not execute in error scenarios. The updated callback now fires on both success and error. - (iOS) Fixed a bug that prevented reply types (for example, buttons) from hiding in older messages. This includes an edge case where the same message displayed twice would incorrectly show reply buttons in both the old and new versions. ### Added - (React Native) Added support for the `startNewConversation` method. ### Native SDK Versions - iOS: 5.0.5 - Android: 3.3.1 ## v2.4.0 **Release date:** 11-04-2024 ### Fixed - (React Native) `isChatAvailable` now returns a boolean on both platforms. - (React Native|iOS) Fixed an issue where `openConversation` could fail to open the SDK. - (React Native|iOS) `showKbArticle` and `showKbCategory` correctly open the KB UI. - (React Native|iOS) `setPushToken` will now show an informative error, instead of causing a crash. - (React Native) Updated the accuracy of various TypeScript types for SDK methods. - (React Native) Fixed the parsing of custom attributes within `describeCustomer`. - (iOS) Fixed a crash that would sometimes happen when in an active chat. This was caused by overlapping UITableViewDataSource updates that support the chat view. - (iOS) Fixed issues that prevented CSAT messages from incrementing unread count. - (iOS) Fixed UI issues that made the chat history screen look different than on web and Android. - (Android) Fixed an issue where the unread count indicator failed to update correctly upon receiving an initial outbound message while the app was terminated. - (Android) Fixed an issue where the unread count indicator was not set when a conversation received a satisfaction survey while the app was killed. The unread count is now correctly updated when the chat history is reopened. - (Android) Fixed a NullPointerException in KusChatFragment.getBinding that occurred when the pull-to-refresh action was still running while the chat screen was closed. - (Android) Fixed an issue related to the usage of the OkHttp BOM that caused build failures when using Android Gradle Plugin versions 8.2 or higher. ### Added - (React Native) Added `all` to the `logLevel` type in the `configure()` method. - (React Native) Added a `useIsKustomerLoggedIn` hook. - (React Native) Added an updated Jest testing framework mock for the Kustomer SDK. - (React Native) Added the `describeConversation` method. - (iOS) Optimized Assets/Images in SDK to decrease the SDK's impact on app size. - Removed embedded SnapKit dependency and marked as Implementation ONLY - made size reduction. - (iOS) Removed embedded Reachability dependency and marked as Implementation ONLY - made size reduction. - (iOS) Improved logic that fetches the unread count for messages after the app is brought into the foreground. - Logic now does not mark any messages as read unless there is an actively open chat conversation. - (iOS) Removed embedded Nantes dependency and marked as Implementation ONLY. - (iOS) Removed embedded NotificationView dependency and marked as Implementation ONLY. - Updated Kustomer logos. ### Native SDK Versions - iOS: 5.0.4 - Android: 3.3.0 ## v2.3.0 **Release date:** 09-23-2024 ### Fixed - (iOS) Removed Alamofire and AlamofireImage packages from dependencies, reducing the binary size of the iOS SDK. - (iOS) Fixed an issue where users could see unread message badges when there were no new messages. - (Android) Updated the `KusLogOptions` to use an enum instead of an integer. - (Android) Fixed all of the Android lint errors. - (Android) Addressed a rare `IllegalStateException` error that could be thrown when calling `startNewConversation`. ### Added - (React Native) Added support for `KustomerChat.close()` to programmatically close the Kustomer UI. - (React Native) Added support for `KustomerChat.describeCustomer()`. - (Android) Added support for `Kustomer.isVisible()`, not yet supported in React Native. ### Native SDK Versions - iOS: 5.0.0 - Android: 3.2.0 ## v 2.2.0 **Release date:** 09-09-2024 ### Fixed - (iOS) Chat screen and message bubbles now have no transforms applied to them. This helps mitigate any scrolling bugginess on the chat screen where swipe to dismiss functionality is triggered when scrolling to bottom (most recent) of chat. - (iOS) SDK now explicitly calls all registerForRemoteNotifications() requests on the main thread to avoid any crashes when calling from a background thread - (Android) Fixed an issue where chat assistant rules were not evaluated in some instances. - (Android) Fixed a localization issue in which certain locales set via `KustomerOptions.setUserLocale()` were not parsed correctly. - (Android) Fixed a navigation issue caused by a missing default value.
(Android) Fixed a minor NullPointerException that occurred when parsing the `verifiedAt` field for an identified customer. ## v2.1.4 **Release date:** 08-08-2024 ### Fixed - (iOS) Fixed a crash that occurred when scrolling to the bottom of chat history when loading the next page of conversations. - (Android) Fixed an issue where the unread message count included messages from different brands. - (Android) Fixed a UI glitch that occurred with blank avatars whenever a conversation was opened. ### Added - (iOS) `KustomerUI.Color.quickActionButtonBorder` to style quick reply and MLL buttons in chats. - (Android) Added pull-to-refresh functionality for the chat conversation view. ### Improved - (iOS) Quick Reply buttons and MLL buttons are now rendered using `quickActionButton`, `quickActionButtonText`, and `quickActionButtonBorder colors`. ## v2.1.3 **Release date:** 07-01-2024 ### Fixed - (iOS) Fixed a bug where swiping down to dismiss the MLL options screen left chat unable to reselect MLL options - (Android) Fixed an issue where featured articles failed to load when opened for non-default brands. - (Android) Fixed a minor UI bug in which the "no search results" view text was incorrectly aligned on smaller devices. ### Updated - (Android) Upgraded knowledge base APIs to v4, enhancing the reliability of handling article locales and translations. ## v2.1.2 **Released:** 03-15-2024 ## Added - Added additional information to configure the SDK for Android or using your JS/JT sources. ## Updated - Updated KustomerSDK on iOS to 4.0.1. - Updated KustomerSDK on Android to 2.13.3. ## v2.1.1 **Released:** 02-23-2024 ### Added - Type definitions. ### Improved - Reduced build artifact size for iOS. (PubNub is no longer a static framework) ## 2.1.0 **Released:** 02-09-2024 ### Updated - Updated KustomerSDK on iOS to 4.0.0 - Updated KustomerSDK on Android to 2.13.2 - Called 2.0.1-22 on npmjs.com ## v2.0.2 ### Updated - Updated to react-native 0.72.5