Skip to main content

Frequently Asked Questions

1. Cannot find header files after importing framework?​

(1). Check if the paths in Framework Search Paths and Head Search Paths are filled in correctly
(2). Confirm whether the tingyunApp.framework file has been "Copied" to the project

2. Error when importing SDK with CocoaPods (The dependency 'tingyunApp' is not used in any concrete target)​

The error occurs because the specified target is not used. Solution: Add the following content to Podfile, then execute pod install (or pod update):
 target 'MyApp' do
     pod 'tingyunApp'
 end (Replace MyApp with the target in your project)

3. Error when executing carthage update​

Enter the ~/Library/Caches/org.carthage.CarthageKitdependencies/ directory,
delete the corresponding tingyunApp folder, then execute carthage update in the project root directory

4. No log output during runtime after successful instrumentation?​

(1). Confirm whether initialization code has been added
(2). Confirm whether NSLog has been overridden. If overridden, it may cause SDK printed logs to not display

5. SDK starts normally but cannot connect to server​

(1). Check if the reporting end has disabled the current application
(2). Confirm whether the current monthly active users exceed the purchased monthly active user limit
(3). Confirm whether bundleID is set in security verification and check its correctness

6. After successful instrumentation, entering the "Intelligence Summary" report shows only active devices​

Check if the network protocol library used by the user is supported. iOS SDK supported protocol libraries: NSURLConnection, ASIHttpRequest, AFNetworking, UIWebview, NSURLSession (iOS 8 and above versions)

7. Cannot collect TCP data in network data reports​

(1). After SDK version 2.5.4, the SDK removed the socket module, iOS 8 and below systems cannot collect TCP data
(2). Before SDK version 2.5.4, iOS 9, 10, 11 cannot collect TCP data
(3). After SDK version 2.5.0, only NSURLSession requests (with delegate methods set), Webview requests, and AFNetworking requests on iOS 10.2 and above devices can collect TCP data

8. Cannot collect NSURLSession network data​

Confirm whether it's an iOS 8 and above device. Tingyun SDK only supports NSURLSession after iOS 8

9. URL/Error filtering not effective​

(1). Usually a regular expression configuration issue. You can check through online regular expression tools. Note that slashes need to be added before and after the regular expression configured in the report
(2). Did you check immediately after configuration? (After saving configuration, you need to wait one or two minutes, then you can log into the report to view)

10. Why is crash not collected?​

(1). Tingyun SDK does not support crash collection for simulators
(2. Are other SDKs embedded? After version 2.3.2, the SDK is compatible with third-party SDK crash collection. The SDK initialization code needs to be placed after other third-party SDK initialization code to ensure Tingyun SDK can normally collect crash data and third-party SDKs can also collect crash data. Therefore, it's recommended to initialize Tingyun SDK after other third-party SDKs (Note: If the startup position is correct but crash still cannot be collected, it may be because other SDKs have done special processing so that their SDK crash collection handler starts after Tingyun SDK crash collection handler)
(3). If crash occurs after installing to phone through Xcode, Tingyun SDK only supports Exception type crash collection
(4). If the application crashes immediately after startup, the crash collection handler cannot start in time, causing Tingyun SDK to be unable to collect crash data
(5). If it's killed by the system or flash exit due to memory warnings, Tingyun SDK cannot collect such data
(6). Tingyun SDK's crash collection logic is that crash data from this crash will only be uploaded after the next startup
(7). Confirm whether the crash collection switch is enabled in the report

11. Why cannot collect WebView performance data?​

(1). Check if the WebView module switch is enabled in the report
(2). Confirm whether the WebView's delegate is ViewController
(3). If onload or unload events are not called during page loading, Tingyun SDK cannot collect WebView performance data
(4). If onload or unload events are called during page loading, but the accessed page URL is "about:blank", Tingyun SDK cannot collect WebView performance data
(5). Confirm whether the device is iOS 10.2 and above system

12. Cannot collect launch time data?​

(1). Confirm whether the user has instrumented in the main function. If instrumented in other locations, Tingyun SDK cannot collect launch time data
(2). Check if the UI module switch is enabled in the report. The user launch time module is controlled by the UI switch. After turning it off, Tingyun SDK cannot collect launch time data

13. Why cannot parse crash stack trace after uploading dsym file?​

Confirm whether the uploaded dsym file is correct. Steps are as follows:
  (1). Log into the report and enter the crash details interface, remove formatting, and view the first line information under binaryImage
  (2). Check dsym UUID: Open terminal, enter the dsym file directory, execute dwarfdump -u xxx (xxx is the dsym name), and the dsym UUID will be displayed after execution

14. Incorrect crash collection thread after embedding talkingdata?​

If you find that NSException crash stack trace collection is incorrect after embedding SDK, please place the SDK initialization at the end of the application: didFinishLaunchingWithOptions method or place the SDK initialization in the main function.