Upgrade Guide
Migrating legacy 2.x integrations
The 2024.0.x SDK introduced the configuration and packaging changes below. These concepts also apply to the 2026.0.3 integration described in this guide. Check the release notes for additional changes between your source and target versions.
Update the SDK integration
Remove the legacy SDK integration and follow Installation for the selected release. For 2026.1.2, use the Swift Package Registry procedure; for the manually distributed 2026.0.3 release, use the legacy XCFramework instructions. Update the deployment target and linker settings to match that release. For 2026.0.3, the minimum deployment target is iOS 16.6 and the SmartContract XCFramework contains static libraries.
Move SDK configuration into code
Set the Security Server URL, license and Workflow Engine URL on SSCConfiguration.sharedManager().configuration before initializing the SDK. Use the configuration example as the source for this setup.
Replace legacy lookups such as [SFKConfiguration senseConfiguration][@"sec-server-url"] with the configured secServerUrl. Do not use the internal SFKConfiguration API in application code.
Migrate proxied hosts
Remove the old nonProxyHosts configuration. Configure the hostnames that should use the SDK proxy through configuration.httpConfiguration.addProxiedHost(...), as shown in HTTP configuration and proxied hosts.
The SDK adds the Workflow Engine host when preparing a contract request. Configure any additional proxied hosts explicitly.
Read server-provided properties through the public API
Replace calls to [SFKSessionService getConfigProperties] with [SSCSessionService getConfigProperties]. These properties are retrieved during session establishment; see Dynamic configuration.