3 ms·
In Android apps, that's how it works. The SDK (recommended for login) is set up by default to collect information and installs handlers for app lifecycle event
by david_allison 5y ago
In Android apps, that's how it works.
The SDK (recommended for login) is set up by default to collect information and installs handlers for app lifecycle events as soon as the app is installed. The default is to do this without requesting user consent.
A rough summary of the data: (Ad ID, device, locale, phone network, maybe install referrer).
To attribute advert -> install, Facebook ads pass on an encrypted blob containing campaign information to the Play Store, this blob is readable by the app, and is transmitted back to Facebook where it's decrypted.
The setting: https://github.com/facebook/facebook-android-sdk/blob/fcd4eff6e4d63f6e2922ae10aea298c7587b96b7/facebook-core/src/main/java/com/facebook/UserSettingsManager.kt#L71 https://github.com/facebook/facebook-android-sdk/blob/fcd4ef...
Defaulted to true: https://github.com/facebook/facebook-android-sdk/blob/5fe6e2a9d7056a17f54c1cae13e00788723d34f6/facebook-core/src/main/java/com/facebook/UserSettingsManager.kt#L52-L53 https://github.com/facebook/facebook-android-sdk/blob/5fe6e2...
https://developers.facebook.com/docs/app-events/getting-started-app-events-android#disable-auto-events https://developers.facebook.com/docs/app-events/getting-star...
- foverzar 5y agoWow, that's a very dark pattern. In any case, this is not how it's supposed to work in oauth, and it's definitely not required for it to work. I suppose developers could pretty much use any generic oauth lib for the login purposes.