SDK lifecycle
The SDK is created and initialised when the client application starts up (upon calling OTVSDK.load()) and is destroyed when the application terminates. Typically, the SDK is created by the following code within the application entry AppDelegate::application(application: didFinishLaunchingWithOptions:) method.
OTVSDK.load()
Before version 5.0.0, a player licence string had to be provided as a parameter of OYVSDK.load(). After 5.0.0, as the player licence is no longer required, the parameter should be empty. See the Apple SDK 5 (FPS) Release Notes version 5.0.0.
Enabling logging
SDK users can set the logging levels by calling OTVSDK.setLogging(level:) after the OTVSDK.load() is called. If OTVSDK.setLogging() is not called, the default level is .warning
OTVSDK.setLogging(level: .debug)
|
Level |
Description |
|---|---|
|
.error |
Indicates a situation needs to be investigated, which may or may not lead the application to abort. |
|
.warning |
Indicates a potentially harmful situation that may lead to an error. |
|
.info |
Designates information about data values or object states at a coarse-grained level. |
|
.debug |
Designates fine-grained informational events, especially the key APIs calling traces that are most useful to debug an application. |