[Kapusch]

Summary

Adds Kapusch.TikTok.Business.Android, a .NET Android package for the TikTok Business SDK (App Events) 1.7.1, independent of the existing Kapusch.TikTok.Android Share package. Replaces #4 with a clean history: no commit contains any encoded private pattern.

• Packaging: the checksum-locked upstream AAR ships unchanged next to a thin Kotlin JNI facade. Shared AndroidX and Kotlin classes come from managed NuGets. Google Play Billing and Install Referrer stay consumer-owned. Nothing is bundled twice.
• Public API aligned with Kapusch.TikTok.Business.iOS (TikTokApisForiOSComponents PR feat(business): add Kapusch.TikTok.Business.Android (TikTok Business SDK 1.7.1) #4): same types, members, config record (AppId, TikTokAppIds, AccessToken and the same opt-outs), TikTokBusinessInitResult(Status, int ErrorCode, ErrorMessage) with the shared 1001/1002 codes, and the same semantics. A deferred start returns InitializedTrackingDisabled with ErrorCode 0. Calls return false before initialization. Calls run synchronously in call order. Platform gaps are documented in Docs/Business/Integration.md ("Differences from the iOS package").
• Initialization is bounded and deterministic. SDK 1.7.1 returns silently from every initializeSdk call after the first, and its async init step swallows Throwables without calling back. The facade enters the SDK only once per process and answers later attempts with InitIncompleteErrorCode (1104). A managed 30 s timer that does not depend on the main looper reports InitTimeoutErrorCode (1105). A late success still sets the initialized state.
• Releases: one publish workflow, with v* tags for Share (unchanged contract) and business-v* tags for Business.
• Public tree scan: scripts/verify-public.py follows the shared approach. Private terms come at run time from KAPUSCH_PRIVATE_TERMS (CI secret) or .git/info/private-terms, and failures only say "private term #N".

Review findings addressed

• [blocker] Encoded private names in scripts/verify-public.py: replaced by the run-time private-terms scanner. Checked git log -p origin/master..HEAD and all commit messages for plain, hex, \x escaped, base64 and URL-encoded forms of every configured term: none found.
• [major] Initialization could hang forever, and a retry could re-enter a half-built SDK: fixed as described above.
• The log level mapping now follows the Android SDK's real order (NONE < INFO < WARN < DEBUG, with errors logged at INFO).
• Identity calls use the SDK's synchronous identify/logout. getAppEventLogger() returns null outside SDK call stacks, so the SDK event queue cannot be used. The docs state the remaining Android ordering gap honestly.
• Currency validation now matches iOS (ISO 4217 shape, non-negative value, currency required with a value). JSON serialization accepts the same value types as iOS.

Validation

• No client keys, signing material, or secrets committed
• Business: cold Native/Android/build.sh, dotnet pack, scripts/validate-business-package.sh (now also checks that the Kotlin and managed error codes match)
• Share: built, packed and scripts/validate-package.sh passed. Share sources are unchanged.
• Sample Release builds with R8, with and without Billing / Install Referrer
• python3 -I scripts/verify-public.py with the local private-terms file
• Runtime check on an Android 16 (API 36) x86_64 emulator, offline:
  • an invalid config throws ArgumentException;
  • concurrent calls share one task;
  • DisableAutoStart gives InitializedTrackingDisabled with code 0;
  • a repeated init returns the current state;
  • StartTrack gives Started;
  • identify, track, logout, flush and token update all return true;
  • after SetTrackingEnabled(false), manual calls return false;
  • with native assets disabled, init gives 1102 and no crash.
• An app that references both packages builds in Release with R8 when KapuschTikTokAndroidIncludeBundledRuntimeDependencies=false. With the bundled graph it fails on duplicate AndroidX classes, as documented.

🤖 Generated with Claude Code