Log Level – iOS

Log levels control how much diagnostic information the SDK emits. They allow you to adjust logging verbosity based on your debugging needs without affecting SDK behavior.

The SDK writes logs only in response to its own activity, such as lifecycle events, state transitions, warnings and errors.

Log levels are hierarchical — higher verbosity levels automatically include logs from lower levels.

---

Log Level Comparison

Level	Description	Includes	Recommended Use
NONE	Disables all logging output.	–	When logging is not needed.
ERROR	Error logs only.	ERROR	When you only need failure notifications.
WARN	Warning and error logs.	WARN, ERROR	When you want visibility into potential issues alongside failures.
INFO (Default)	High-level SDK activity and state transitions.	INFO, WARN, ERROR	General monitoring of SDK activity, events, operations, and state changes.
DEBUG	INFO logs plus detailed diagnostic information.	DEBUG, INFO, WARN, ERROR	Investigating issues or when deeper diagnostic details are required.
ALL	All logs, including high-frequency real-time events.	ALL	Detailed analysis, troubleshooting complex scenarios, or low-level debugging.

---

Setting the Log Level

Call VideoSDK.setLogLevel(level:) with one of the LogLevel cases: .NONE, .ERROR, .WARN, .INFO, .DEBUG or .ALL.

The level is .INFO until you change it. If you call setLogLevel without a level, it uses .INFO. VideoSDK.getLogLevel() returns the current level.

The log level can be configured at any time:

• Before joining a room
• After joining a room
• During runtime

Logs appear in the Xcode console while your app runs from Xcode. Most lines start with VideoSDK:.

Enable Logs

VideoSDK.setLogLevel(level: .DEBUG)

Disable Logs

VideoSDK.setLogLevel(level: .NONE)