Swift package artifacts for FullStory SwiftUI selectors, an add-on to the FullStory SDK for instrumenting iOS mobile apps.
This package is used alongside fullstory-swift-package-ios, not instead of it. Each FSSwiftUISelectors release is built against one specific FullStory build, so its manifest pins the matching FullStory version exactly.
Email mobile-support@fullstory.com for additional help.
For information about the content of each release, please see the Release Notes.
In Xcode, add https://github.com/fullstorydev/fullstory-swiftui-selectors-ios as a package dependency and pin it to an exact version, then add the FSSwiftUISelectors library to your app target. FullStory itself is pulled in automatically at the matching version.
Because you will also be calling FullStory APIs directly (FS.setup(...) and friends), most projects should declare both packages explicitly at the same version:
dependencies: [
.package(url: "https://github.com/fullstorydev/fullstory-swiftui-selectors-ios", exact: "1.74.0"),
.package(url: "https://github.com/fullstorydev/fullstory-swift-package-ios", exact: "1.74.0"),
]The two pins must agree. Because this package pins FullStory with exact:, mismatched versions surface as a resolution error rather than a runtime failure.
Two things about the manifest are deliberate and are worth knowing before changing it.
No platforms: declaration. Declaring one becomes a floor that every consuming package must also declare. Real apps keep SwiftUI code in packages that declare a lower deployment target or none at all, and SwiftPM would refuse to resolve those. The framework is built for iOS 13 and everything it exposes is guarded by @available, so it links at any deployment target.
The FSSwiftUISelectorsDependencies target. It contains no code. SwiftPM does not allow a binary target to declare dependencies, but the framework's .swiftinterface contains import FullStory, so consumers need the FullStory module on their search path and linked into their build. That empty target carries the FullStory dependency and ships as part of the FSSwiftUISelectors library product. Without it, a project that depends on this package alone fails to compile with Unable to find module dependency: 'FullStory'.
Releases are published by the Update Swift Package Version workflow, which runs daily and can also be triggered manually from the Actions tab.
Unlike the FullStory SDK, the SwiftUI selectors xcframework does not ship a Package.swift alongside it, so the manifest is generated by scripts/generate-package-swift.sh rather than downloaded from the release server.
The workflow reads the shared VERSION file from the release server and only creates a release commit and tag once all of the following exist at that version:
fullstory-swiftui-selectors-<version>-xcframework.zipfullstory-<version>-xcframework.zip- the matching tag in
fullstory-swift-package-ios
That last check matters because the generated manifest pins fullstory-swift-package-ios at exactly this version. That repo is updated by its own scheduled job, so a release server that is a few hours ahead of it would otherwise produce a package that cannot resolve.
If anything is missing the run exits successfully without changing the repo, so it is safe for the daily schedule to run while a release is still in progress. If a selectors release is ever skipped because the release server has already moved on to a newer VERSION, trigger the workflow manually and pass the version you want to publish.