Skip to main content
Get ShortKit installed and verified in your app. Choose your platform below.

Requirements

Package structure

The SDK ships as a pre-compiled binary XCFramework via Swift Package Manager:Import the module in your code with import ShortKitSDK.

Package installation

Option A: Xcode UI

1

Open your project in Xcode

Go to File then Add Package Dependencies.
2

Enter the repository URL

Paste the following URL into the search field:
3

Select your version rule

Choose Up to Next Major Version and set the minimum to 0.2.22. Click Add Package.
4

Add to your target

Select the ShortKitSDK library product and add it to your app target.

Option B: Package.swift

Add ShortKit to your dependencies array:
Package.swift
Then add it to your target:
Package.swift

Verify installation

Build and run this minimal example to confirm the import resolves and the SDK initializes.
App.swift
If you have content uploaded to your ShortKit account, you should see a vertical video feed. If your account has no content yet, the feed will display an empty state — follow the Quickstart to upload your first video.
Get your publishable API key from the Admin Portal under Settings then API Keys. Use pk_live_... for production and pk_test_... for development.

Troubleshooting

This means Xcode has not resolved the Swift Package dependency.
  1. Verify the package URL is exactly https://github.com/shortkit/shortkit-ios
  2. Go to File then Packages then Reset Package Caches
  3. Clean the build folder: Product then Clean Build Folder (Shift+Cmd+K)
  4. Close and reopen Xcode
  5. Confirm your deployment target is iOS 16.0 or higher in your project settings
ShortKit requires iOS 16.0 or later. If you see a build error referencing a minimum deployment target:
  1. Select your project in the Xcode navigator
  2. Under the General tab, set Minimum Deployments to iOS 16.0 or higher
  3. If you have multiple targets, update each one
ShortKitSDK is distributed as a pre-compiled XCFramework. If the download fails:
  1. Check your internet connection — the binary is downloaded from GitHub Releases
  2. Go to File then Packages then Reset Package Caches and resolve again
  3. If you see a checksum mismatch, ensure you are on the latest version of the package
If Gradle cannot resolve the ShortKit dependency:
  1. Confirm your project includes Maven Central in its repositories. Most new Android projects include it by default in settings.gradle.kts.
  2. Check your internet connection and any proxy configuration
  3. Run ./gradlew --refresh-dependencies to clear the dependency cache
  4. Confirm your minSdk is 24 or higher
If you see duplicate class errors after adding ShortKit, another dependency in your project may include a conflicting version of a transitive dependency (e.g., Media3 or OkHttp).
  1. Run ./gradlew app:dependencies to inspect the full dependency tree
  2. Use Gradle’s resolutionStrategy or constraints block to force a consistent version
If flutter pub get cannot resolve the package:
  1. Verify the package name is exactly shortkit_flutter in your pubspec.yaml
  2. Run flutter pub cache repair to clear the cache
  3. Ensure you are using Flutter 3.38 or later: flutter --version
If pod install fails after adding the Flutter package:
  1. Confirm your ios/Podfile has platform :ios, '16.0' or higher
  2. Run cd ios && pod install --repo-update
  3. If you see a CocoaPods version error, update CocoaPods: gem install cocoapods
If you see an error about ShortKit not being found at runtime:
  • React Native CLI: Run cd ios && pod install and rebuild
  • Verify autolinking is enabled (check react-native.config.js is not excluding the package)
  • Clear the Metro cache: npx react-native start --reset-cache
If the native build fails after adding the package:
  1. Confirm "@shortkitsdk/react-native" is in the plugins array in your app.json or app.config.js
  2. Run npx expo prebuild --clean to regenerate native projects from scratch
  3. If using EAS Build, ensure @shortkitsdk/react-native is listed in your package.json dependencies (not just devDependencies)
  4. Clear the Metro cache: npx expo start --clear
If you are using the CDN script tag and see ShortKit is not defined:
  1. Confirm the script tag loads before your code runs. Place it above your initialization script, or use the defer attribute and initialize in a DOMContentLoaded listener.
  2. Check the browser console for network errors loading the script.
  3. Verify you are using ShortKit (capital S, capital K) — the global is case-sensitive.
If the SDK initializes successfully but the feed is empty:
  1. Confirm you have uploaded at least one video to your ShortKit account. You can check in the Admin Portal under Content.
  2. Verify the video status is Ready (processing can take 1-2 minutes after upload)
  3. Check that you are using the correct API key for the environment where your content lives (pk_live_... for production content, pk_test_... for test content)
A 401 error means the API key is invalid or not recognized:
  1. Double-check the full key string, including the pk_live_ or pk_test_ prefix
  2. Make sure you are using the publishable key, not the secret key, in client-side code
  3. Verify the key has not been revoked in the Admin Portal
  4. Confirm the key matches the environment you are targeting