[Kapusch]

Summary

Supersedes #3. This branch carries the same work with a rewritten history. The earlier public-tree scanner commit is replaced, so no commit in the merged history contains a private deny pattern. The CI sample-link steps now arrive with the sample, so every commit builds. Review fixes from #3 are separate commits on top.

This adds a second, independent package to the repo, Kapusch.TikTok.Business.iOS 1.0.0-rc.1. It wraps the TikTok Business SDK (App Events SDK) 1.7.2, the latest stable iOS release (re-checked 2026-10-26).

The existing Kapusch.TikTok.iOS package (OpenSDK Share) does not change. Its project, lock, validator, notices and docs are untouched. A local repack matches the published 1.0.0 entry for entry, and its buildTransitive files, notices, readme and privacy manifests are byte-identical. The only difference is NuGet.org's repository signature.

Layout

	Share (unchanged)	Business (new)
Project	src/Kapusch.TikTokApisForiOSComponents	src/Kapusch.TikTok.Business.iOS
PackageId / namespace	Kapusch.TikTok.iOS	Kapusch.TikTok.Business.iOS
Lock	DependencyLocks/iOS/lockstate.txt	DependencyLocks/iOS/business-lockstate.txt
Native artifact	ktkshare.xcframework (ktk_*)	ktkbusiness.xcframework (ktkb_*)
Validator	scripts/validate-package.sh (keeps NSPrivacyTracking=false)	scripts/validate-business-package.sh
Tags	vX.Y.Z[-rc.N]	business-vX.Y.Z[-rc.N]

Public C# API (Kapusch.TikTok.Business.iOS)

• TikTokBusinessSdk.InitializeAsync(TikTokBusinessConfig) returns Task<TikTokBusinessInitResult(Status, ErrorCode, ErrorMessage)>.
  • Status is one of Started, InitializedTrackingDisabled or Failed, taken from the SDK completion handler.
  • ErrorCode carries SDK codes such as -2 (App ID mismatch), or the wrapper codes 1001 / 1002.
• Other members: StartTrack(), SetTrackingEnabled(bool), TrackEvent(name, IReadOnlyDictionary<string, object>?, eventId?), Identify(externalId, externalUserName?, phoneNumber?, email?), Logout(), Flush(), UpdateAccessToken(), IsInitialized, IsTrackingEnabled, SdkVersion and TestEventCode.
• Typed helpers:
  • TrackStartTrial, TrackSubscribe and TrackPurchase take value, currency, eventId, contentId and contentType. TrackPurchase also takes contents and description.
  • TrackRegistration and TrackLogin take eventId.
• TikTokBusinessConfig fields:
  • AppId, TikTokAppIds (a list), AccessToken (the App Secret), DebugMode, LogLevel;
  • DisableAutoStart, DisableAutomaticTracking, DisableInstallTracking, DisableLaunchTracking, DisableRetentionTracking, DisablePaymentTracking, DisableAppTrackingDialog, DisableSKAdNetworkSupport, DisableAdvertiserIdCollection, DisableEnhancedDataPostback, LimitedDataUse;
  • AttAuthorizationDelay, CustomUserAgent, LowPerformanceDevice.
• Constants:
  • TikTokBusinessEventNames lists all 28 standard event names of SDK 1.7.2, spelled exactly as the SDK sends them (LaunchAPP, InAppADClick, InAppADImpr, ...), plus the auto-only 2Dretention and PurchaseRestored.
  • TikTokBusinessPropertyNames lists value, currency, content_id, content_type, description, contents, price, quantity, content_category, content_name, brand and ad_revenue.
  • TikTokBusinessContent is a record for the entries of contents.

Why these choices

iOS packaging: build from the locked source and merge with libtool -static, instead of using the upstream release xcframework.

• The upstream static xcframework is built with Swift 6.3.3 / Xcode 26.6 and the iOS 26.5 SDK, which I checked in its .swiftinterface and Info.plist. That is newer than this repo's pinned toolchain (Xcode 26.3 / Swift 6.2.4).
• Static Swift objects from a newer compiler can fail to link for consumers on Xcode 26.3. This is the same reason PR ci: pin macos-15, Xcode 26.3 and the 10.0.203 iOS toolchain #2 pinned CI.
• Building from the SHA-256-locked source tarball keeps the existing technique: one force-loaded static xcframework per package, no embedded dynamic framework, no extra signing or launch cost.
• SPM is an official upstream integration (TikTokBusinessSDK_SPM), so this is not a patched build.
• The spike built cleanly in about 2 minutes for 3 slices with Xcode 26.3.

Swift runtime, -ObjC, -lc++

• The .NET 10 iOS SDK always links the Swift system libraries (_AddSwiftLinkerFlags). LinkWithSwiftSystemLibraries=true is still set on the NativeReference so the requirement is explicit.
• ForceLoad covers -ObjC. It loads every object, including the categories, and the classes the SDK resolves with NSClassFromString (TikTokStoreKitObserver, TTSDKCrashInstallationConsole).
• IsCxx adds -lc++ for the crash monitor's C++ unit. -lsqlite3, -lz, the SDK frameworks and a weak AppTrackingTransparency are declared explicitly.

Privacy manifest

• The upstream SPM package declares no resources, so the manifest is taken unchanged from the repo root. It is byte-identical to the one inside the release xcframework.
• It is bundled as TikTokBusinessSDK_Privacy.bundle/PrivacyInfo.xcprivacy, the CocoaPods bundle name.
• The validator checks that the packaged manifest is identical to the upstream file.

Nothing starts before InitializeAsync

• Every other export, except SdkVersion, returns false until the wrapper has configured the SDK. So Identify cannot persist identity data before consent, and no SDK singleton is created.
• I verified this on a simulator: trackBeforeInit=False flushBeforeInit=False, and the SDK printed no log line.
• The upstream +load hooks that run anyway are documented in Integration.md §2. None of them makes a network call. One stores the launch URL and a launch referrer in NSUserDefaults; for a notification launch, the referrer is the payload.

DisableAutoStart maps to disableTracking() on iOS

• The SDK reports -1 in that case. The wrapper maps it to InitializedTrackingDisabled, not to a failure.
• That result has ErrorCode 0 and no message, the same as a repeated call in that state.
• A repeated InitializeAsync returns the current state instead of the SDK's -3 error.
• Integration.md says this is not a consent gate, because the SDK fetches its remote config at init even in this mode.

Threading: only InitializeAsync hops to the main thread.

• initializeSdk schedules an NSTimer on the current run loop, so it needs the main thread.
• Every other member calls the SDK synchronously on the caller's thread. The SDK reads the identity when it creates each event, so Identify(); TrackRegistration(); and Logout(); TrackEvent(); must run in call order, also from background async code.
• This is how the SDK itself calls trackEvent and flush, from its network-callback threads. The other setters only write a flag or hand work to the SDK's own queues.

Value as a string in the typed helpers. This mirrors TikTokContentsEvent.setValue:(NSString *) and TikTokContentParams.price, so manual events have the same wire shape as the SDK's own contents events.

Config fields that have no effect on iOS: DisableAppTrackingDialog and DisableAdvertiserIdCollection.

• They are kept so the API matches the Android package.
• The upstream ATT switch is deprecated and never read in 1.7.x.
• iOS has no ad-ID switch. The IDFA is only readable after ATT.
• Both are documented in XML docs and in Integration.md.

A single publish.yml, routed by tag prefix

• GitHub tag filters match the whole tag name, so v* does not match business-v*. The script also routes by prefix and checks the business-v format.
• Manual runs get a package choice that defaults to share, so Share behaviour is unchanged.
• Keeping one workflow file means the existing NuGet trusted-publishing policy, which is scoped to repo and workflow file, can cover the new package ID.

Separate notices file for the Business package. Editing the root THIRD_PARTY_NOTICES.md would have changed the contents of the Share nupkg, which packs that file. The Business notices are in src/Kapusch.TikTok.Business.iOS/THIRD_PARTY_NOTICES.md and also include the KSCrash notice for the embedded TTSDKCrash component.

Validation (local, Xcode 26.3, .NET 10.0.203)

• bash src/Kapusch.TikTok.Business.iOS/Native/iOS/build.sh: 3 slices with 130 objects each (wrapper, 116 Obj-C/C/C++, 13 Swift), producing ktkbusiness.xcframework (5.2 MB device archive).
• scripts/validate-business-package.sh: passed.
• scripts/validate-package.sh: passed. The Share repack also matches the published 1.0.0, as described in the summary.
• scripts/check-native-symbol-collisions.sh: no strong global symbol in common on arm64, simulator arm64 or simulator x86_64 (347 Share and 614 Business symbols).
• The sample links for iossimulator-x64 (Debug and Release) and for an unsigned ios-arm64 Release build (full AOT). The device binary links the Swift runtime from /usr/lib/swift and bundles TikTokBusinessSDK_Privacy.bundle.
• Runtime smoke on an iPhone 17 simulator (iOS 26.3): launch OK, sdk=1.7.2 initialized=False trackBeforeInit=False flushBeforeInit=False.
• python3 -I scripts/verify-public.py: passed, with and without run-time extra patterns. Negative tests: a filled Sample* key in Info.template.plist, a matching extra pattern and an invalid extra pattern all fail.
• scripts/check-native-symbol-collisions.sh --with <archive>: a test archive defining _defaultPattern is reported as a collision; the Share xcframework is not.
• I simulated the publish.yml routing for v1.0.1, business-v1.0.0-rc.1, a malformed business-v1.0, and manual runs with and without a version.

Public-tree scan without private names. scripts/verify-public.py keeps only generic checks in the tree: pasted App Secrets, and empty Sample* keys in sample Info.template.plist files. Deny patterns for private identifiers are read at run time from VERIFY_PUBLIC_EXTRA_PATTERNS, one regex per line, from a CI secret or an untracked local file. Matches are reported by file name only, so the scan never prints what it looks for.

Generic upstream symbols. The force-loaded archive defines two unprefixed upstream globals, _handleConfiguration (KSCrash-derived TTSDKCrashC.c) and _defaultPattern (TikTokViewUtility.m). They are not renamed, because the repo never patches upstream sources. Integration.md §8 lists them, and check-native-symbol-collisions.sh --with <archive> lets an app compare its other static SDKs with the Business archive.

Not done / open

• Event delivery is not verified on a device. No Events Manager app or credentials are available here. Before the final 1.0.0, check in Test Events that InstallApp, LaunchAPP, StartTrial and Subscribe arrive, and that no automatic Purchase arrives with DisablePaymentTracking.
• NuGet trusted publishing for the new ID. If the current policy does not let publish.yml create Kapusch.TikTok.Business.iOS, the first business-v1.0.0-rc.1 push will fail at the push step. The fix is to add or extend the policy on nuget.org; no code change is needed.
• VERIFY_PUBLIC_EXTRA_PATTERNS secret. CI passes it to the public-tree job, but the repository secret has not been created yet. Until it is, CI runs only the generic checks.
• Required-reason APIs. The SDK uses some that its own manifest does not declare: sysctl kern.boottime, NSFileSystemSize and stat. Integration.md tells host apps to declare them.

🤖 Generated with Claude Code