Skip to content

Changelog

ft_mobile_agent_flutter

0.5.7 (2026/07/09)

  1. Compatible with Android ft-sdk 1.7.3, Android ft-native 1.1.3, and iOS FTMobileSDK 1.6.5.
  2. Added support for Flutter Session Replay via ft_session_replay_flutter.
  3. Added blacklist filtering capability to filter Log and RUM data before writing to the local cache. Rules can be configured in-app via FTMobileFlutter.sdkConfig(dataFilters: ...) or automatically pulled from the Blacklist in the Guance Workspace. Both methods take effect simultaneously. This capability is enabled by default. It can be disabled with enableDataFilter: false to turn off SDK-side filtering. Filtering rules are applied after lineDataModifier.
  4. Added remote configuration APIs: FTMobileFlutter.sdkConfig(enableRemoteConfiguration, remoteConfigMiniUpdateInterval, remoteConfigOverrideRules), FTMobileFlutter.updateRemoteConfig() and FTMobileFlutter.updateRemoteConfigWithMiniUpdateInterval(...).
  5. Added Android cache total size and FileStore configurations: enableLimitWithCacheSize, cacheLimit, cacheDiscard, enableFileDataStore, needTransformOldCache, fileDataStoreShadow.
  6. Added FTRUMManager().setConfig(enableTraceWebView, allowWebViewHost) to support configuring Android SDK WebView data collection and the allowed hosts for collection.
  7. Added FTRUMManager().setConfig(enableNativeSwiftUIUserView) to support automatic tracking of native iOS SwiftUI views.
  8. Added Flutter LongTask support: FTRUMManager().setConfig(enableLongTask, dartLongTaskThreshold) enables detection of long tasks on the Dart main isolate, and FTRUMManager().addLongTask(stack, duration) enables manual reporting of LongTask.
  9. Added FTRUMManager().addAction(actionName, actionType) for high-frequency Action writing scenarios, without associating with Resource, LongTask, or Error events.
  10. Added FTMobileFlutter.sdkConfig(customHttpOverrides) to pass a custom HttpOverrides when HTTP auto-collection is enabled, reducing conflicts with the app's custom network proxy logic.
  11. Added FTMobileFlutter.shutDown() to shut down the SDK.
  12. RUM Resource reporting now includes resourceType and new metric fields such as requestSize, resourceHttpProtocol, reusedConnection, and connectionReuse.
  13. Fixed an issue where the Error stack trace could be misaligned when calling FTRUMManager().addError(...), and an issue where attributes could be lost when calling FTRUMManager().startAction(...) on Android.

0.5.7-pre.4 (2026/07/09)

  1. Added blacklist filtering capability to filter Log and RUM data before writing to the local cache. Rules can be configured in-app via FTMobileFlutter.sdkConfig(dataFilters: ...) or automatically pulled from the Blacklist in the Guance Workspace. Both methods take effect simultaneously. This capability is enabled by default. It can be disabled with enableDataFilter: false to turn off SDK-side filtering. Filtering rules are applied after lineDataModifier.
  2. Added Android cache total size and FileStore configurations: enableLimitWithCacheSize, cacheLimit, cacheDiscard, enableFileDataStore, needTransformOldCache, fileDataStoreShadow.
  3. Added FTRUMManager().setConfig(enableNativeSwiftUIUserView) to support automatic tracking of native iOS SwiftUI views.
  4. Added Flutter LongTask support: FTRUMManager().setConfig(enableLongTask, dartLongTaskThreshold) enables detection of long tasks on the Dart main isolate, and FTRUMManager().addLongTask(stack, duration) enables manual reporting of LongTask.
  5. RUM Resource reporting now includes resourceType and new metric fields such as requestSize, resourceHttpProtocol, reusedConnection, and connectionReuse.
  6. Updated the Android Maven repository address to mvnrepo.guance.com.

0.5.6 (2025/06/16)

  1. Added FTRUMManager().setConfig(sessionOnErrorSampleRate) to support error sampling. When data has not been sampled by setSamplingRate, RUM data from up to 1 minute before the error can be sampled and collected when an error occurs.
  2. Added FTMobileFlutter.sdkConfig(dataModifier, lineDataModifier) for data replacement before writing, supporting data masking.
  3. Compatible with Android ft-sdk 1.6.11 and iOS 1.5.16.

More changelogs for ft_mobile_agent_flutter

ft_session_replay_flutter

0.1.0 (2026/07/09)

  1. Added FTSessionReplayManager().setConfig(FTSessionReplayConfig(...)) and SessionReplayCapture to support Flutter Session Replay data collection.
  2. Added Session Replay privacy configuration fields: touchPrivacy, textAndInputPrivacy, imagePrivacy.
  3. Added FTSessionReplayConfig(enableSwiftUI) to enable native iOS SwiftUI Session Replay recording.
  4. Upgraded the Android dependency ft-session-replay to 0.1.6, using ft-sdk:1.7.3 and ft-native:1.1.3.
  5. iOS dependencies are FTMobileSDK 1.6.5 and FTMobileSDK/FTSessionReplay 1.6.5.
  6. When Session Replay configuration is applied after SessionReplayCapture has already been mounted, the component re-registers the recording state to avoid missing replay data due to initialization timing.

0.1.0-pre.1 (2026/07/09)

  1. Added FTSessionReplayConfig(enableSwiftUI) to enable native iOS SwiftUI Session Replay recording.
  2. Upgraded the Android dependency ft-session-replay to 0.1.6-beta01 while continuing to use ft-sdk:1.7.3 and ft-native:1.1.3.
  3. Updated the Android Maven repository address to mvnrepo.guance.com.

0.1.0-dev.1 (2026/07/03)

  1. Added the standalone Flutter Session Replay plugin package ft_session_replay_flutter; Session Replay is no longer provided by ft_mobile_agent_flutter.
  2. The new package provides FTSessionReplayManager, FTSessionReplayConfig, SessionReplayCapture, SessionReplayPrivacy, and privacy configuration enums for touch, text input, and images.
  3. Android dependencies are ft-session-replay:0.1.6-alpha02, ft-sdk:1.7.3, and ft-native:1.1.3; iOS dependencies are FTMobileSDK 1.6.5 and FTMobileSDK/FTSessionReplay 1.6.5.
  4. It is recommended to initialize in the order FTMobileFlutter.sdkConfig(...), FTRUMManager().setConfig(...), FTSessionReplayManager().setConfig(...), and wrap the Flutter view tree to be recorded with SessionReplayCapture.
  5. When Session Replay configuration is applied after SessionReplayCapture has already been mounted, the component re-registers the recording state to avoid missing replay data due to initialization timing.

More changelogs for ft_session_replay_flutter