From af7b86220953c5778ef6642cf8c874c0fce8ce8b Mon Sep 17 00:00:00 2001 From: Jean-Emmanuel BAILLAT Date: Wed, 28 Oct 2026 12:42:54 +0100 Subject: [PATCH] docs(appevents): correct the Android activation behaviour in the parity notes The iOS behaviour was right: with SDK 18.0.2, AppEvents.activateApp logs fb_mobile_activate_app through the public logEvent path as an explicit event, whatever isAutoLogAppEventsEnabled says. The Android comparison was wrong: facebook-core 19.0.0 drops activation events while automatic logging is off, so ActivateApp() sends only the install ping, and turning the flag off stops activations at once. Co-Authored-By: Claude Opus 5.5 --- Docs/Integration.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Docs/Integration.md b/Docs/Integration.md index 8bb83dc..7c59743 100644 --- a/Docs/Integration.md +++ b/Docs/Integration.md @@ -291,9 +291,13 @@ Behaviour differences: - Before initialization, the Android setters throw; the iOS setters are recorded and applied again once the SDK is initialized. -- After withdrawal, the Android SDK keeps logging activations on activity resumes until - the process ends; the iOS SDK only logs them when `ActivateApp` runs or automatic - logging is on. +- App opens with automatic logging off: on iOS, `ActivateApp()` logs + `fb_mobile_activate_app` as an explicit event. On Android (facebook-core 19.0.0), + activations are automatic events, so `ActivateApp()` then sends only the install ping; + measuring opens there needs `SetAutoLogAppEventsEnabled(true)`. +- After withdrawal, turning automatic logging off on Android stops activation events at + once, while activity tracking keeps running until the process ends; the iOS SDK only + logs activations when `ActivateApp` runs or automatic logging is on. - On iOS, the automatic-logging value set at Meta overrides the local one (SDK 18.0.2, section 4.1).