Skip to content

Troubleshooting

SDK Initialization Exception Verification

When the compilation and runtime platform is Android:

Check Logcat to confirm if there are logs with Level as Error and Tag prefixed with [FT-SDK]

14:46:04.825 [FT-SDK] com.demo E Please install the SDK (call FTSdk.install(FTSDKConfig ftSdkConfig) when the app starts)

When the compilation and runtime platform is iOS:

In Debug environment, after configuring the Guance SDK and running the application for the first time, please check your debugger console in Xcode. The SDK will use assertions to verify multiple configurations and crash with relevant warnings if any configuration is incorrect.

For example, if the datakit metrics write address is not set during SDK configuration, the program will crash and output a warning⚠️ in the console.

*** Assertion failure in +[FTMobileAgent startWithConfigOptions:], FTMobileAgent.m:53
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Please set the datakit metrics write address'

Enabling Debug Mode

You can enable the debug functionality of the SDK through the following configuration.

let config: FTMobileConfig = {
    serverUrl: Config.SERVER_URL,
    debug: true
};
FTMobileReactNative.sdkConfig(config);

It is recommended to disable this configuration when releasing the Release version

When the compilation and runtime platform is Android: Check Logcat logs with Tag prefixed with [FT-SDK]

When the compilation and runtime platform is iOS:

The debug logs of the SDK are identified with the prefix [FTLog].

  • When using xcode, you can directly view the debug logs of the SDK in the xcode debugger console.

  • When running with terminal commands yarn ios or yarn react-native run-ios, you can view the SDK debug logs in the Console on Mac.

To use the Console:

Select Action and check Include Brief Information, Include Debug Information.

Select the debugging device, click the Start button, and enter the search condition [FTLog] in the search box on the right side. You can then view the SDK debug logs.

console_app_use

Android Logcat and iOS Xcode Console log examples

SDK Running Normally but No Data

  • Troubleshoot Datakit to ensure it is running normally

  • Confirm that the SDK upload address datakitUrl or datawayUrl is configured correctly and initialized properly. In debug mode, check the synchronization logs in Android Logcat or iOS Xcode Console.

  • Check if Datakit is uploading data to the corresponding workspace and whether it is offline. This can be confirmed by logging into Guance and checking the "Infrastructure".

Data Loss

Partial Data Loss

  • If some RUM Session data, Logs, or a few Trace data entries are missing, first check if sampleRate < 1 is set in FTRUMConfig, FTLoggerConfig, or FTTraceConfig;

  • If RUM data collection is incomplete, missing Resource or Action data?

    Resource and Action data are bound to Views. Ensure that there is an FTReactNativeRUM.startView operation. Refer to the RUM-View documentation to implement View event collection.

  • Investigate network issues and load problems with the device uploading data and the device running Datakit.

Compatibility Issues

React Native Navigation Runtime Compatibility Issues

Symbol ReactTextShadowNode.UNSET Not Found

This issue arises from version compatibility with react-native-navigation. Refer to the related issue here. Fix this by modifying or downloading and replacing ReactTypefaceUtils.java.

Module react/jsx-runtime Not Found

Affected Versions: SDK version 0.3.0 && React version < 16.14.0

Cause: The SDK internally uses react/jsx-runtime, which is supported only in React >= 16.14.0.

Fix Recommendations:

  • Upgrade the SDK version to >= 0.3.1

Note: It is not recommended to add the @cloudcare/react-native-mobile dependency library via a local path, as this may prevent the error from being resolved.

More Related Content

Feedback

Is this page helpful? ×