Applies to CocoaPods integrations for the SightCall iOS SDKs
What is changing?
SightCall now publishes iOS SDK podspecs in its own public CocoaPods spec repository:
https://github.com/sightcall/sightcallsdkpods
You do not need to change your app code. The pod names, frameworks, and APIs remain the same. You only need to add the SightCall repository to your Podfile, keep the CocoaPods CDN for other public dependencies, and pin an exact SDK version.
| Pod | Trunk | SightCall spec repository |
|---|---|---|
LSUniversalSDK |
Up to 5.6.0, frozen | 5.5.0 to 5.8.6 as of 03 November 2026 |
SightCallVisionSDK |
Up to 5.6.0, frozen | 5.5.0 to 5.8.3 as of 03 November 2026 |
LSUniversalSDK_Agent |
Not available | 5.8.3 and 5.8.6 as of 03 November 2026 |
SightCallVisionSDK_Agent |
Not available | 5.8.0 and 5.8.1 as of 03 November 2026 |
LSUniversalBroadcastSDK |
Use the SightCall repository | 1.2.2, 5.4.2, and 5.5.5 currently listed in the repository |
Versions in the table are a snapshot. Check the repository for the current list before selecting a version.
Update your Podfile
1. Declare the SightCall repository first
Put the SightCall source before the CocoaPods CDN. Once you declare any source, CocoaPods no longer adds the CDN implicitly, so list it explicitly when your app uses other public pods.
Before
platform :ios, '15.0'
use_frameworks!
target 'MyApp' do
pod 'LSUniversalSDK', '5.6.0'
endAfter
source 'https://github.com/sightcall/sightcallsdkpods.git'
source 'https://cdn.cocoapods.org/'
platform :ios, '15.0'
use_frameworks!
target 'MyApp' do
pod 'LSUniversalSDK', '5.8.6'
endUse the same pattern for SightCallVisionSDK, LSUniversalSDK_Agent, SightCallVisionSDK_Agent, and LSUniversalBroadcastSDK. Select a version that exists in the repository.
2. Pin an exact version
Use an exact version such as '5.8.6'. Avoid optimistic ranges such as '~> 5.8' and avoid leaving the version blank. The repository can contain non-release entries, and exact pinning keeps builds reproducible.
3. Optionally tie each pod to its source
Some older versions exist in both the Trunk CDN and the SightCall repository. CocoaPods may print a Found multiple specifications warning. The warning is harmless when the SightCall source is listed first. To make the origin explicit, add :source to the pod:
pod 'LSUniversalSDK', '5.8.6',
:source => 'https://github.com/sightcall/sightcallsdkpods.git'4. Install or update
pod install --repo-updateWhen moving to a newer version later, update the version in the Podfile and run:
pod update LSUniversalSDKReplace the pod name when updating a different SDK.
5. Verify the source
Open Podfile.lock and check the SPEC REPOS section:
SPEC REPOS:
https://github.com/sightcall/sightcallsdkpods.git:
- LSUniversalSDKIf the SDK is listed under trunk, it is still resolving from CocoaPods Trunk. Check the source order and the requested version.
Continuous integration
Build machines need HTTPS access to github.com and sightcall-ios-cocoapods.s3.amazonaws.com. If CI caches ~/.cocoapods/repos, run pod repo update or pod install --repo-update once after changing the Podfile. No credentials are required. Commit Podfile.lock so every machine resolves the same version.
Minimum iOS version
platform :ios, '15.0' and use an app target with a deployment target of iOS 15.0 or higher.Troubleshooting
| Symptom | Fix |
|---|---|
| Unable to find a specification for LSUniversalSDK (= 5.8.6) | Add the SightCall source and run pod install --repo-update. |
| You still get 5.6.0 after the change | Update the version in the Podfile and run pod update LSUniversalSDK. Check whether Podfile.lock still pins 5.6.0. |
| Found multiple specifications for LSUniversalSDK | This is harmless when the SightCall source is first. Add the per-pod :source option to silence it. |
| An unexpected SDK version is installed | Use an exact version instead of an unpinned dependency or optimistic range. |
| The SDK download fails or times out | Allow HTTPS access to sightcall-ios-cocoapods.s3.amazonaws.com. |
| The dependency requires a higher deployment target | Raise the app's deployment target and platform :ios to iOS 15.0 or higher. |
Does this change the SDK API?
No. This migration changes where CocoaPods finds the podspec. It does not require application code changes.