Changelog¶
0.4.2 (2026/06/26)¶
- Added blacklist filtering capability, which supports filtering Log and RUM data before writing to the local cache. Rules can be configured in-app via
FTMobileConfig.dataFilters, and can also be automatically pulled from the blacklist in the Guance workspace. Both methods take effect simultaneously. This capability is enabled by default. You can disable SDK-side filtering withenableDataFilter: false, and the filtering rules are executed afterlineDataModifier. - Upgraded compatible versions: iOS SDK 1.6.5, Android ft-sdk 1.7.2, and Android ft-session-replay 0.1.5
- Fixed Android Java 8 compilation compatibility issues
- Fixed the missing RUM
addResourcebridge issue in the Android old architecture
0.4.1 (2026/04/22)¶
-
Added Session Replay capability, released as the standalone
@truewatchtech/react-native-session-replaypackage that can be installed and used separately -
Added Session Replay error sampling capability, and support for dynamically controlling Session Replay through remote configuration
- Session Replay supports privacy configuration for touches, text and input, and images through
touchPrivacy,textAndInputPrivacy, andimagePrivacy. It also adds the native componentFTSessionReplayView, which can mark and protect sensitive areas in the React Native UI during Session Replay recording - Added support for the React Native New Architecture, improving compatibility with the latest React Native application configurations
- Support dynamically updating the data upload endpoint via
FTMobileReactNative.setDatakitURLandFTMobileReactNative.setDatawayURL - Upgraded compatible versions: Android ft-sdk 1.7.0, Android ft-session-replay 0.1.3, and iOS SDK 1.6.2
0.3.16 (2026/03/26)¶
- Adapted to Android ft-sdk 1.6.17 and iOS SDK 1.5.20
- Added
FTRUMConfig.enableTraceWebViewandFTRUMConfig.allowWebViewHostconfiguration items to support WebView collection rule configuration - Added
remoteConfiguration,remoteConfigMiniUpdateInterval, andremoteConfigOverrideRulestoFTMobileConfigto support remote configuration, update interval control, and configuration override rules - Added support for configuring the iOS crash monitoring type via
FTRUMConfig.iosCrashMonitoringType - Support adding context through the
FTMobileReactNative.appendBridgeContextmethod to distinguish data sources or mark specific scenarios
0.3.15 (2025/08/12)¶
0.3.14 (2025/05/16)¶
- Added
FTRUMConfig.sessionErrorSampleRateto support error sampling. When not sampled bysampleRate, RUM data from 1 minute before an error can be sampled and collected when an error occurs - Added
FTMobileConfig.lineDataModifierandFTMobileConfig.dataModifierto support data write replacement and data masking - Adapted to Android ft-sdk 1.6.10 and 1.6.11, and iOS 1.5.15 and 1.5.16
0.3.13 (2025/03/21)¶
- Adjusted Android Java 8 compatibility and removed the Kotlin library dependency
0.3.12 (2025/03/07)¶
- Added RUM
Resourcedata fieldsresource_first_byte_time,resource_dns_time,resource_download_time,resource_connect_time,resource_ssl_time, andresource_redirect_time, supporting enhanced Resource duration display on TrueWatch and aligning the timeline in the Application Performance Monitoring (APM) flame graph FTMobileConfig.enableDataIntegerCompatibleis enabled by default- Adapted to Android ft-sdk 1.6.9, and iOS 1.5.12, 1.5.13, and 1.5.14
0.3.11 (2025/02/05)¶
- Optimized SDK configurations for hybrid native and React Native development
- Support automatic collection of React Native control click events via
FTRumActionTracking.startTracking(), and automatic collection of React Native error logs viaFTRumErrorTracking.startTracking() - When RUM Resource automatic collection is enabled, added
FTReactNativeUtils.filterBlackResource(url)on iOS andReactNativeUtils.isReactNativeDevUrl(url)on Android to filter React Native symbolization requests and Expo log requests in development environments, reducing redundant data
- Support automatic collection of React Native control click events via
- Adapted to iOS SDK 1.5.11
0.3.10 (2025/01/21)¶
-
Changed the way native SDK header files are referenced in the iOS bridge code
-
Added a limit on the number of RUM entries.
FTRUMConfig.rumCacheLimitCountcan be used to limit the maximum number of entries cached in the SDK, andFTRUMConfig.rumDiscardStrategycan be used to specify whether to discard new or old data -
Added support for limiting the total cache size via
FTMobileConfig.enableLimitWithDbSize. When enabled,FTLoggerConfig.logCacheLimitCountandFTRUMConfig.rumCacheLimitCountbecome invalid.FTMobileConfig.dbDiscardStrategycan be used to configure the database discard strategy, andFTMobileConfig.dbCacheLimitcan be used to set the database cache limit - Adapted to Android SDK ft-sdk 1.6.6, 1.6.7, and 1.6.8
0.3.9 (2024/12/24)¶
- Changed part of the Android React Native Bridge from Kotlin to Java to improve React Android compatibility
- Adapted to Android SDK ft-sdk 1.6.5
0.3.7 (2024/12/04)¶
- Fixed the incorrect data type labeling for Android RN errors
- Support setting the jank detection threshold via
FTRUMConfig.nativeFreezeDurationMs - Support
deflatecompression for synchronized data usingFTMobileConfig.compressIntakeRequests - Adapted to iOS SDK 1.5.6 and 1.5.7
- Adapted to Android SDK ft-sdk 1.6.2, 1.6.3, and 1.6.4
0.3.6 (2024/11/06)¶
- Adapted to iOS SDK 1.5.5
0.3.5 (2024/10/23)¶
- Added support for collecting Native Error, ANR, and Freeze
- Changed the default error type for react-native automatic error collection
- For components with the
onPressproperty, added support for defining whether to collect the component's click events by adding the custom propertyft-enable-trackwhenenableAutoTrackUserActionis enabled, and for adding extra Action properties viaft-extra-property
0.3.4 (2024/10/19)¶
- Support globally and dynamically adding globalContext properties
- Support custom error types via
FTReactNativeRUM.addErrorWithType() - Support shutting down the SDK via
FTMobileReactNative.shutDown() - Support clearing unreported cached data via
FTMobileReactNative.clearAllData() - Fixed the issue where the
stackandmessageparameters were assigned in reverse order during automatic react-native Error collection - Adapted to Android SDK ft-sdk 1.6.1
- Adapted to iOS SDK 1.5.4
0.3.3 (2024/10/09)¶
- Adapted to iOS SDK 1.5.3
0.3.2 (2024/08/28)¶
- Fixed the issue where the Android
FTMobileConfig.envconfiguration was invalid
0.3.1 (2024/08/21)¶
- Compatibility fix for the
react/jsx-runtimeerror when the React version is lower than 16.14.0 - Android compatibility with lower react native 0.63 versions
- Modified the regular expression for filtering URLs pointing to localhost and expanded its matching scope
- Adapted to iOS SDK 1.5.2
0.3.0 (2024/08/16)¶
- Added support for data synchronization parameter configuration, request entry data, sync interval, and log cache entry count
- Added remote IP address resolution for RUM resource network requests
- Added line protocol Integer data compatibility mode to handle web data type conflicts
- Added a custom status method for logs
- Modified the react-native action collection method to adapt to the issue where React 17 cannot intercept click events from React.createElement
- In Debug scenarios, RUM Resource collection now filters out hot reload connections pointing to localhost
- Fixed the Android underlying Double adaptation issue