SDK Initialization

Before using any Virtual Stadium UI components, you must initialize the SDK in your iOS application. This guide covers the initialization process and essential configuration steps.

#Initialize the SDK

The SDK must be initialized once when your application starts. You can choose between two approaches: using an AppDelegate (traditional approach) or using SwiftUI's lifecycle methods (modern approach).

#Option 1: Using AppDelegate (Recommended)

Create an AppDelegate and initialize the SDK: AppDelegate.swift:

import UIKit
import VirtualStadiumSDK

class AppDelegate: NSObject, UIApplicationDelegate {
    func application(
        _ application: UIApplication,
        didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil
    ) -> Bool {
        // Initialize Virtual Stadium SDK
        Task {
            do {
                try await Managers.SDK.shared.initialize()
                print("SDK initialized successfully")
            } catch {
                print("Failed to initialize SDK: \(error)")
            }
        }
        return true
    }
}

Then register your AppDelegate in your main App struct: YourApp.swift:

import SwiftUI

@main
struct YourApp: App {
    @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate
    
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

#Option 2: Using SwiftUI Lifecycle

Alternatively, initialize the SDK directly in your App struct using the init() method: YourApp.swift:

import SwiftUI
import VirtualStadiumSDK

@main
struct YourApp: App {
    
    init() {
        // Initialize Virtual Stadium SDK
        Task {
            do {
                try await Managers.SDK.shared.initialize()
                print("SDK initialized successfully")
            } catch {

Or use the .task modifier on your root view: YourApp.swift:

import SwiftUI
import VirtualStadiumSDK

@main
struct YourApp: App {
    @State private var isSDKInitialized = false
    
    var body: some Scene {
        WindowGroup {
            if isSDKInitialized {
                ContentView

#Basic Chat Implementation

Once the SDK is initialized, you can implement the ChatView component in your SwiftUI views.

#Minimal Setup

Here's a minimal example of implementing the ChatView: ContentView.swift:

import SwiftUI
import VirtualStadiumSDK

struct ContentView: View {
    let userJWT: String = "<your-jwt-token>"
    let channelId: String = "<your-channel-id>"
    
    var body: some View {
        ChatView(
            userJWT: userJWT,
            channelId: channelId,
            supportedLanguage: .english

#Full Implementation With Handlers

Here's a complete example with all handlers configured: ChatViewContainer.swift:

#Configuration Overview

Here's a complete checklist of the initialization and configuration steps:

#Troubleshooting

#SDK Not Initialized Error

If you see an error about the SDK not being initialized:

• Verify Managers.SDK.shared.initialize() is called before presenting ChatView
• Ensure your AppDelegate is registered using @UIApplicationDelegateAdaptor (if using Option 1)
• Check that the initialization completes before presenting the ChatView
• Review console logs for initialization error messages
• If using pure SwiftUI approach, ensure the loading state properly waits for initialization

#Handler Not Being Called

If your handlers (onBetShareHandler, onCopyToBetslip, etc.) aren't being called:

• Verify the handlers are not nil
• Check that you're providing the closure/function implementation
• Ensure the SDK is properly initialized before user interaction
• Review console logs for any error messages

#Initialization Timing Issues

If you experience timing-related issues with initialization:

• Use the AppDelegate approach (Option 1) for more reliable initialization timing
• Ensure async initialization completes before the UI that depends on it is shown
• Consider using a loading state to wait for initialization (as shown in Example 2)

#Next Steps

Now that the SDK is initialized and configured, you're ready to explore the chat component in detail: