[Kapusch]

Summary

Replaces #6. Same feature: Kapusch.Facebook.iOS 1.2.0 (first published as 1.2.0-rc.1) adds Meta App Events (FacebookAppEvents) and moves the Login and Share facades from Swift to Objective-C, so the build no longer depends on the Swift compiler Meta used.

Differences from #6:

• The bundled Facebook iOS SDK stays 18.0.2. This is the owner's decision. The 19.0.0 bump commit is dropped, along with what only SDK 19 has: the metadata and product-improvement switches and the arm64e slice handling.
• The history is rebuilt from master. No commit contains the encoded private pattern that feat: App Events + Facebook iOS SDK 19.0.0 (1.2.0) #6's scripts/verify-public.py carried. The scanner now follows the shared approach of the Android repository:
  • only generic patterns are tracked;
  • private terms are read at run time from KAPUSCH_PRIVATE_TERMS (a repository secret in CI) or from the untracked .git/info/private-terms;
  • a failure names only the file and private term #N.
• This PR adds the independent review that feat: App Events + Facebook iOS SDK 19.0.0 (1.2.0) #6 never got, and its fixes. The commits after fix(login) are those fixes.

Review findings and fixes

Checked against the Facebook iOS SDK 18.0.2 sources (FBSDKAppEvents.m, Settings*.swift, ApplicationDelegate.swift, FBSDKUserDataStore.m, FBSDKTimeSpentData.m).

1. Calls made before the SDK is initialized were silently lost (fix(app-events): refuse calls…). Before FBSDKApplicationDelegate configures it, the SDK:

   • drops logged events, with only a log line;
   • ignores user data;
   • overwrites a user ID set earlier with the persisted one;
   • answers setting getters with defaults, and caches some of them for the whole process. For example, reading IsSKAdNetworkReportEnabled before initialization pinned it to true whatever the Info.plist said.

   Now:

   • App Events, Login and Share report initialization to a shared registry, and the new IsSdkInitialized reads it.
   • The event methods, the identity methods and the getters throw InvalidOperationException until then, as Android does.
   • HandleOpenUrl and ContinueUserActivity stop forwarding until then. Forwarding stores campaign IDs and feeds AEM, so it must wait for consent.

2. API alignment with Kapusch.Facebook.Android 1.2.0-rc.1 (feat(app-events): align…):

   • InitializeSdk(dataProcessingOptions, dataProcessingCountry, dataProcessingState).
   • Data processing options are recorded and applied again after initialization. Before, options set before init were lost at the next launch.
   • FacebookAppEventsUserData.ExternalId. SetUserData now replaces every field, as on Android.
   • decimal and ulong parameter values are sent as exact text.
   • float values keep their shortest form. Before, 0.1f was sent as 0.10000000149011612.

3. Consent semantics were partly inaccurate (docs(app-events): describe SDK 18.0.2…):

   • In SDK 18.0.2, an automatic-logging value set at Meta overrides the local FacebookAutoLogAppEventsEnabled / SetAutoLogAppEventsEnabled once the app configuration is cached. SDK 19 changed this.
   • The docs now separate what stops at once on withdrawal from what only stops later.
   • They no longer claim that purchase amounts are rounded to three decimals: the SDK does not do that. The activation threshold is Meta's session timeout, 60 s by default.
   • A parity table lists the intentional gaps with Android:
     • no auto-init on iOS;
     • no SDK 19 metadata switches in 18.0.2;
     • iOS-only forwarding, advertiser tracking, SKAdNetwork and single-field user data.

4. The sample's withdrawal did not match the recipe (fix(sample)): it now sets explicit-only flushing and skips the identity calls when the SDK is not initialized.

5. Packaging guards (ci: commits):

   • validate-package.py checks the SDK slices and privacy manifests that the targets reference. An SDK slice rename, like 19's arm64e, would otherwise break every consuming build.
   • CI builds the sample, and scripts/verify-app-symbols.py checks that the app keeps every kfb_* entry point. Only a built app showed the dead-stripping bug that fix(login) fixes.

Checked with no change needed:

• The Login and Share port matches the old Swift sources line by line:
  • result mapping (failure, then cancelled, then success);
  • the empty-token check;
  • nonce handling;
  • the callback guards;
  • native dialog mode;
  • the pasteboard handling, which never reads the pasteboard;
  • the URL scheme filter.
• The facades match the 18.0.2 headers: selectors, nullability, threading (activateApp and InitializeSdk hop to the main thread) and the flush-behaviour values.

Validation (local, Xcode 26.3, .NET 10.0.203)

• bash src/Kapusch.FacebookApisForiOSComponents/Native/iOS/build.sh: OK. Every commit of the branch builds natively and in managed code (-warnaserror).
• dotnet pack and python3 scripts/validate-package.py: OK.
• bash tests/validate-feature-selection.sh: OK.
• python3 scripts/verify-public.py: OK, with the private terms configured. The commit messages and patches of the branch are clean too, in plain, hex and base64 forms.
• The sample builds for the simulator with Login;AppEvents, AppEvents and Share. All 37 kfb_* entry points are present in each build.
• An x64 simulator run launches the sample and initializes the SDK through Login.

🤖 Generated with Claude Code