Skip to content

Changelog

ft_sdk

0.1.15 (2026/07/29)

  1. Added DataModifier, which supports modifying or masking fields and tags for Log, Native RUM, and WebView RUM; when the field callback returns null, the original value is retained.
  2. Added LineDataModifier for row-level data patching; the callback receives the merged data and only overwrites fields present in the returned patch, returning null or an empty Map does not modify the data.
  3. Added RUM and Logging data filtering capability, enabled by default; can be controlled via setEnableDataFilter(...), and local rules can be configured via setDataFilters(...). Local and remote rules take effect together, and data that matches a rule is not written to the local cache.
  4. Added runtime upload address switching capability, which can be switched via FTSDK.setDatakitUrl(...) or FTSDK.setDatawayUrl(..., clientToken); remote configuration is automatically refreshed after switching, and the DataWay mode requires a client Token.
  5. Added remote configuration capability; on startup, local cache and already-supported runtime update items are merged, it can be enabled via setRemoteConfiguration(...), and manually refreshed via updateRemoteConfig(...).
  6. Added RUM Action API extensions: addAction supports setting duration and custom properties, startAction supports setting custom properties.
  7. Removed addActionWith..., startActionWith..., and the unfinished public stopAction API; please migrate to addAction and startAction.
  8. Added Resource lifecycle custom property support; the properties of startResource and stopResource are merged with ResourceParams in invocation order.
  9. Removed unused statusCode and contentLength parameters from the public stopResource; please delete the corresponding call parameters.
  10. Changed the overload form of addError; dateline can be placed before errorType, and the Worker callback is no longer a public interface.

0.1.14 (2026/07/17)

  1. Optimized the Error and Resource collection pipeline, removing high-frequency internal Debug logs during normal collection.
  2. Added upload request compression configuration, controllable via setCompressIntakeRequests(...); deflate is enabled by default, falling back to plaintext upload when unavailable.
  3. Added auto-sync and upload control configuration; the initial state can be set via FTSDKConfig.setAutoSync(...), or the sync state can be changed at runtime via FTSDK.setAutoSync(...). Auto-upload uses a 10-second aggregation window by default; when disabled or when immediate upload is needed, call FTSDK.flushSyncData().
  4. Added sync pagination configuration; predefined page size can be set via setSyncPageSize(...), or custom sync entry count via setCustomSyncPageSize(...).
  5. Added upload network configuration; proxy, proxy authentication, and DNS can be set via setProxy(...), setProxyAuthenticator(...), and setDns(...) respectively.
  6. Optimized thread pool and serial database task processing, improving data consistency under high concurrency.
  7. Optimized the idle recycling strategy for ANR and Crash Workers; Workers are rebuilt on demand.
  8. Changed the Native Crash diagnostic log collection condition: it is now collected only when a RUM App ID is configured and FTRUMConfig.setEnableTrackAppCrash(true) is enabled.
  9. Added SDK debug configuration; the log level can be set via FTSDKConfig.setSdkLogLevel(...), and internal log files can be written via FTSDKConfig.setEnableInnerLogFile(...).
  10. Added FTTraceConfig.setTraceHeaderHandler(...), which provides a custom trace context for a single request, allowing the SDK to inject request headers and associate them with RUM Resources.
  11. Changed the RUM and Log cache count configuration: the RUM cache count is now set via FTRUMConfig.setRumCacheLimitCount(...), while the Log cache count continues to use FTLoggerConfig.setLogCacheLimitCount(...).
  12. Changed public exports: The root Index now exports WebView integration, advanced RCP interceptor assembly, and Trace interceptor types, so they no longer need to be imported from internal paths.
  13. Fixed the missing dynamic properties (including user data) when confirming View data.
  14. Fixed the occasional instability of randomly assigned user IDs.
  15. Added @ohos/axios auto-collection compatibility path: For axios versions that do not support interceptorChain, call applyFTAxiosTrack(...) to collect data via request and response interceptors.

More changelogs

ft_sdk_ext

0.1.15 (2026/07/29)

  1. Changed ft_sdk_ext version to 0.1.15 as a version alignment update; interceptor API and behavior are unchanged.

0.1.14 (2026/07/17)

  1. Changed the integration method of the NetworkKit interceptor, using a versioned FTSDKExtensionBridge contract to avoid ft_sdk_ext depending on internal source paths like ft_sdk/src/main/....
  2. Changed the minimum compatible API Level to 22.
  3. Changed the distribution method of the NetworkKit HttpInterceptor API, splitting it into an extension HAR; when using this API, please integrate ft_sdk_ext.
  4. Added createFTHttpInterceptorChain(...), supporting NetworkKit auto-collection.
  5. Added applyFTHttpTrack(...), supporting HTTP auto-collection.
  6. Added applyFTAxiosChainMethodBridge(...), supporting axios interceptorChain auto-collection.

More changelogs

ft_native

0.1.1 (2026/07/29)

  1. Changed ft_native version to 0.1.1 as a version alignment update; Native Crash API and behavior are unchanged.

0.1.0 (2026/07/17)

  1. Added standalone Native Crash collection capability.
  2. Optimized the Native Crash collection logic: it automatically adapts based on the installed ft_sdk dependency, passing only real native crashes to FTNativeCrashAdapter; JavaScript Crash continues to be handled by ft_sdk's Error collection pipeline, avoiding duplicate reporting.

More changelogs

Feedback

Is this page helpful?