iOS SDK reference

Overview

This topic documents how to get started with the iOS SDK, and links to reference information on all of the supported features.

Get started

After you complete the Get started process, follow these instructions to start using the LaunchDarkly SDK in your application:

• Install the SDK
• Import the SDK
• Initialize the client
• Evaluate a flag

Install the SDK

The first step is to install the LaunchDarkly SDK as a dependency in your application.

LaunchDarkly supports multiple methods for installing the SDK. Each method is explained below.

//...
    dependencies: [
        .package(url: "https://github.com/launchdarkly/ios-client-sdk.git", .upToNextMinor("9.0.0")),
    ],
    targets: [
        .target(
            name: "YOUR_TARGET",
            dependencies: ["LaunchDarkly"]
        )
    ],
//...
COPY

use_frameworks!
target 'YourTargetName' do
  pod 'LaunchDarkly', '~> 9.0'
end
COPY

github "launchdarkly/ios-client" ~> 9.0
COPY

Import the SDK

After you install the SDK as a dependency, import the LaunchDarkly client in your application code:

import LaunchDarkly
COPY

Initialize the client

After importing the SDK, configure and initialize the client. Specify your mobile key when configuring the SDK so that your application is authorized to connect to a particular environment within LaunchDarkly.

The following example shows how to configure the SDK, specify your mobile key, and initialize the client.

We recommend calling the client initialization method with a timeout of five seconds or fewer. The SDK provides a timedOut boolean to the completion closure, indicating whether the connection timed out.

Here's how:

let config = LDConfig(mobileKey: "mobile-key-123abc", autoEnvAttributes: .enabled)
let contextBuilder = LDContextBuilder(key: "context-key-123abc")
guard case .success(let context) = contextBuilder.build()
else { return }
LDClient.start(config: config, context: context, startWaitSeconds: 5) { timedOut in
    if timedOut {
        // Client may not have the most recent flags for the configured context
    } else {
        // Client has received flags for the configured context
    }
}
COPY

To learn more about the specific configuration options available in this SDK, read LDConfig.

Evaluate a flag

After calling start, you can retrieve the LDClient instance with the static method LDClient.get():

let client = LDClient.get()!
COPY

Then, use the client to check which variation a particular context will receive for a given feature flag.

Here's how:

let showFeature = client.boolVariation(forKey: "flag-key-123abc", defaultValue: false)
if showFeature {
  // Application code to show the feature
else {
  // The code to run if the feature is off
}
COPY

Background fetch

When the app is backgrounded, the SDK does not receive real-time events.

Unlike other mobile SDKs, the iOS SDK does not support background fetch, so devices on the iOS operating system will not fetch flags from the background. However, devices on MacOS will update flag values opportunistically, according to the iOS SDK standard background polling defaults.

To change the background polling default for flags in your app, add the following code in your LDConfig:

var ldConfig = LDConfig(mobileKey: "mobile-key-123abc", autoEnvAttributes: .enabled)
ldConfig.backgroundFlagPollingInterval = 3600
COPY

Shut down the client

Shut down the client when your application terminates. To learn more, read Shutting down.

Data collection

The data collected by the iOS SDK persists until the number of cached contexts exceeds a limit. When you call identify, the number of cached contexts increments. Eventually, the number of cached contexts exceeds maxCachedContexts. When that happens, the SDK deletes context data in excess of maxCachedContext, starting with the oldest context first.

To learn more about data collection within this SDK and implications on submissions to the Apple App Store, read the Apple App Store data collection policy.

Supported features

This SDK supports the following features:

• Anonymous contexts and users
• Automatic environment attributes
• Configuration, including
  • Application metadata configuration
  • Service endpoint configuration
• Context configuration
• Evaluating flags
• Flag evaluation reasons
• Flushing events
• Getting all flags
• Hooks
• Identifying and changing contexts
• Logging configuration
• Monitoring SDK status
• Multiple environments
• Offline mode
• Private attributes
• Relay Proxy configuration, using proxy mode
• Sending custom events
• Shutting down
• Subscribing to flag changes