Is this helpful?

# Debugging and Logging

During the process of SDK integration, you can perform real-time debugging by checking SDK's logs in the IDE console or using the Debug feature of TE.

# Printing Log


After opening the log, you can check data tracking of SDK by filtering logs related to ThinkingAnalytics in IDE.

# 2. Debugging

You need to follow the following two steps to enable the Debug mode:

  1. Enable the debug mode at the client side

The sample code for enabling the Debug mode on the client side is as follows:

// obtain TDConfig instance
TDConfig config = TDConfig.getInstance(this, TE_APP_ID, TE_SERVER_URL);
Set the operation mode as the Debug mode
NORMAL mode: the data would be saved in caches and reported according to relevant cache policies under the NORMAL mode by default. It is recommended to use the mode in an online environment
Debug mode: report data item by item. If problems occur, the user would be notified with logs and anomalies. It is recommended to use the Debug mode in an online environment
DebugOnly mode: data would be verified without being stored; it is not recommended to use the DebugOnly mode in an online environment
// initialize SDK
instance = ThinkingAnalyticsSDK.sharedInstance(config);
  1. Add Device

To avoid launching the Debug mode in the production environment, it is required that only specified device can enable Debug mode. The Debug mode can only be enabled for devices whose IDs have been configured in the "Debugger"sector on the "Tracking Management" page of TE when the client side has enabled the Debug mode.

Device ID can be get by the following three methods:

  • #device_id property in the event data of TE
  • Client log: DeviceID would be printed as log after SDK is initialized
  • Call API:Device ID

The Debug mode may undermine the data tracking quality and stability of the App. It could only be used for data verification at the integration stage, and should not be used in the online environment.