Added support for FTRUMConfig.sessionErrorSampleRate error sampling, allowing data sampling of rum data from 1 minute prior when an error occurs if not sampled by sampleRate.
Added FTMobileConfig.lineDataModifier, FTMobileConfig.dataModifier to support data replacement on write, enabling data desensitization.
Added new RUM Resource data fields: resource_first_byte_time, resource_dns_time, resource_download_time, resource_connect_time, resource_ssl_time, resource_redirect_time. Enhanced display support for Resource timing in Guance and alignment with APM flame graphs.
Enabled FTMobileConfig.enableDataIntegerCompatible by default.
Optimized SDK configuration for native and React Native hybrid development:
Support automatic collection of React Native component click events via the FTRumActionTracking.startTracking() method, and automatic collection of React Native error logs via the FTRumErrorTracking.startTracking() method.
When enabling automatic RUM Resource collection, added methods FTReactNativeUtils.filterBlackResource(url) for iOS and ReactNativeUtils.isReactNativeDevUrl(url) for Android to filter React Native symbolized requests and Expo log requests in the development environment, reducing redundant data.
Modified the way native SDK header files are referenced in iOS bridge code.
Added functionality to limit RUM entry counts, supporting restriction of SDK cache entry limits via FTRUMConfig.rumCacheLimitCount and specifying whether to discard new or old data via FTRUMConfig.rumDiscardStrategy.
Added support for limiting total cache size via FTMobileConfig.enableLimitWithDbSize. After enabling, FTLoggerConfig.logCacheLimitCount and FTRUMConfig.rumCacheLimitCount will be invalidated. Supports setting db discard strategy via FTMobileConfig.dbDiscardStrategy and db cache limit size via FTMobileConfig.dbCacheLimit.
Supported collecting Native Errors, ANRs, and Freezes.
Changed the default error types for automatically collected errors in react-native.
For components with the onPress attribute, added support to define whether to collect click events after enabling enableAutoTrackUserAction through a custom attribute ft-enable-track, and add extra Action properties through ft-extra-property.