How to Handle Logs from the Twilio Video iOS SDK – Twilio Support

Objective

When building real-time video applications, having access to detailed logs is essential for troubleshooting and monitoring user experience. Developers using the Twilio Video JavaScript SDK may be familiar with the ability to direct logs to external locations using Logger.getLogger('twilio-video'). However, if you’re developing with the Twilio Video iOS SDK, you may notice that similar functionality is not currently available.

This article explains the current options for logging in the Twilio Video iOS SDK, available workarounds, and how to provide feedback to Twilio.

Product

Programmable Video

Procedure

Current Logging Capabilities in the iOS SDK

The Twilio Video iOS SDK provides built-in logging that can be adjusted for verbosity. You can enable debug-level logging in your iOS app with the following code:

TwilioVideoSDK.setLogLevel(.debug)

This will increase the detail of logs generated by the SDK, which can be helpful during development and troubleshooting.

However, at this time, the iOS SDK does not support exporting or redirecting these logs to an external location (such as a remote server or analytics platform) out of the box. Logs are available only within the app’s local environment.

Why Is External Logging Important?

External logging allows you to:

Capture real user experiences in production environments
Monitor and troubleshoot issues that occur on end-user devices
Aggregate logs for analysis and long-term storage

This is especially useful for teams who need to diagnose issues that only occur in the field, or who want to maintain a centralized log repository.

Workarounds and Alternatives

While direct external logging is not currently supported in the iOS SDK, you have a few options:

1. Use the Video Log Analyzer REST API

Twilio provides the Video Log Analyzer REST API , which allows you to access data generated by Programmable Video rooms and participants. Key points:

Logs are available for 7 days after a room ends.
Most logs are accessible within 10 minutes after the room ends; full summarization may take up to 30 minutes.
This API provides insights into room and participant behavior, which can help with troubleshooting.

2. Custom Logging in Your App

If you need to capture additional events or errors from your app (outside of the SDK), you can implement your own logging mechanism. For example, you can send custom logs to your backend using HTTP requests or a third-party logging service.

Feature Requests and Feedback

Twilio is always looking to improve its SDKs based on customer feedback. If external logging from the iOS SDK is important to your workflow, we encourage you to let us know. Your feedback helps prioritize future enhancements.

Additional Information

The Twilio Video iOS SDK currently does not support exporting logs externally.
You can adjust log verbosity for local debugging.
Use the Video Log Analyzer REST API for post-room analysis.
Implement custom logging in your app for additional needs.
Share your feedback with Twilio to help shape future SDK features.

For more information or to stay updated on SDK changes, visit the Twilio Video documentation and the Twilio Video iOS SDK.