-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
Feature Request: Suppress advertiserIDCollectionEnabledFalseWarning #1082
Comments
The log states the following:
But the code in |
Thanks for submitting this request. We will add it to our feature request list. The complete sentence is |
So now in iOS 14 setAdvertiserTrackingEnabled is there. how is that difference than isAdvertiserIDCollectionEnabled? |
Any updates on this feature request? I would like this removed from my console as well. |
@tianqibt my understanding is no difference. It's the same thing. |
But I may be wrong :) |
It's been 2 years, feature request list definitely not effective enough to remove undesired warnings spamming the console of every app using the sdk. Is there other way around to speed things up? |
any news about this matter? I'm getting that warning too. Thanks |
Still getting this warning when set to TRUE. |
Checklist
Feature Request: [name of my feature request]
Goals
As a consumer of the Facebook SDKs purely for social login purposes, I don't want to be notified about unrelated configuration warnings in the console logs during development of my application.
Since we have no need for Facebook to track analytics, we've set the
FacebookAdvertiserIDCollectionEnabled
andFacebookAutoLogAppEventsEnabled
info plist keys tofalse
however we now get the following log message:Expected Results
The log message above is not printed in my console. I explicitly opted out of any kind of automatic tracking and I don't need to be reminded about it each time we build and run the application.
If you're happy for me to, I'd be more than happy to submit a PR removing it but I'll wait for a response here first. Thanks
The text was updated successfully, but these errors were encountered: