Logging and Crash Reporting
The SDK writes its own logs and reports errors in its own code to Kindly. Debug logs are off by default and crash reporting is on
Settings
KindlyWebViewSDK.verboseLogging = true // debug logs, off by default
KindlyWebViewSDK.enableCrashReporting = false // on by defaultSet both before start so they cover the whole session
Reading the logs
Logs go to the unified log under the subsystem ai.kindly.webview. On a device, watch them in the Console app. For the booted simulator, in a terminal:
xcrun simctl spawn booted log stream --predicate 'subsystem == "ai.kindly.webview"' --level debugThe logs never contain chat content, chat ids, context values, tokens, or more of a URL than its scheme and host. A call the SDK refuses, such as displayChat before start or a context map that breaks the rules, is logged as an error with or without the debug logs. The debug logs add how the chat page loads, each token request's outcome and each link's, so turn them on while you integrate
Crash reporting
Crash reporting sends errors in the SDK's own code to Kindly, without chat content, see Privacy and Data for what a report carries. It is separate from your app's crash reporting:
The SDK does not use the Sentry SDK, so it never touches a Sentry setup of your app