Replies: 1 comment
-
We found the problem, seems to be a bug: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We need a strictly GDPR-compliant handling of the SDK, basically initialize it only after the user gives consent, so our settings look like this:
[
‘react-native-fbsdk-next’,
{
appID: ‘OURAPPID’,
clientToken: ‘OURTOKEN’,
displayName: ‘OURNAME’,
advertiserIDCollectionEnabled: false,
autoLogAppEventsEnabled: false,
isAutoInitEnabled: false,
iosUserTrackingPermission: ‘This identifier will be used to deliver personalized ads to you.’,
},
],
The settings also get written into the info.plist correctly:
Should work, right?
After doing this and without doing anything else, immediately when opening the app in the simulator, the app does the following requests:
Our expectation is that the SDK does not do anything until we initialize it - does anyone have an idea what could be wrong?
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions