Repository navigation
Open Measurement as its own product: KontextKit + KontextKitOM (0.2.0) - #6
Merged
Merged
Conversation
…ubspecs Core + OMSDK); 0.2.0 Every consumer linked OMSDK_Kontextso.xcframework (2.3 MB) and took on the IAB OM licence because the one target depended on the binary. Two targets and two products now: KontextKit (Sources/KontextKit: DeviceInfo, Privacy, StoreKit, UI, Utilities, the privacy manifest) and KontextKitOM (Sources/KontextKitOM: the OMID wrappers and omsdk-v1.js, depending on KontextKit and the binary target). An SDK that does not measure with OMID depends on KontextKit alone. CocoaPods mirrors it with subspecs Core (default) and OMSDK. KontextKitOM reads its script from its own resource bundle. CI builds and tests KontextKit-Package. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… resource any more Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every consumer of
KontextKitlinkedOMSDK_Kontextso.xcframework(2.3 MB) and took on the IAB OM licence, because the one target depended on the binary.sdk-swift-videouses nine providers and nothing from OM; nothing outsideSources/OMSDK/referenced OM either, so the split is clean.What
Two targets, two products:
KontextKitSources/KontextKit/PrivacyInfo.xcprivacyKontextKitOMSources/KontextKitOM/OMManager,OMSession,OMPartner,OMCreativeType,omsdk-v1.js; depends onKontextKitand theOMSDK_Kontextsobinary targetCocoaPods: subspecs
KontextKit/Core(default) andKontextKit/OMSDK(vendored_frameworks,OMLICENSEpreserved).pod lib lintpasses.KontextKitOMreadsomsdk-v1.jsfrom its own resource bundle (Bundle.moduleunder SPM,KontextKitOM.bundleunder CocoaPods) — theBundle.moduleaccessor is per target.CI builds and tests the
KontextKit-Packagescheme, which covers both products. 166 tests pass locally.Breaking (0.2.0)
Consumers that use OM add the second product and
import KontextKitOMwhereOMManager& co. are used; CocoaPods consumers depend onKontextKit/OMSDK.import KontextKitstill gives every provider and manager. sdk-swift PR follows; sdk-swift-video depends onKontextKitalone.Release
After merge: tag
0.2.0,pod trunk push(trunk goes read-only on December 2, 2026 — this one should go out before then), then bump sdk-swift and sdk-swift-video.🤖 Generated with Claude Code