Skip to content

docs(appevents): correct the Android activation behaviour in the parity notes #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Kapusch merged 1 commit into from
Oct 28, 2026
Merged

docs(appevents): correct the Android activation behaviour in the parity notes #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions Docs/Integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down
Loading