-
-
Notifications
You must be signed in to change notification settings - Fork 50
FacebookSDK is outdated #233
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
Comments
@tillsanders Indeed, the current SDK is not only outdated but it's also officially deprecated and they will stop accepting API calls until 2023. I'm also surprised that this plugin hasn't been updated for so long. Sure, it's working just fine and that's probably a reason. Maybe they continued the support in pro plugins, who knows? |
There is no ProPlugin, but @bradmartin said on Slack he would take a look when he has some time. But of course, we all know how difficult it can be to make some room for stuff that's not the top priority! |
This comment was marked as abuse.
This comment was marked as abuse.
@NathanaelA Sorry if this came across wrong! I didn't mean to imply any obligation for anyone to put his/her time in this, because – as you said – it's open source and everyone has their own priorities. |
Facebook are ending their tracking service in June so if that's your only concern - you won't have to worry about it very soon 😆 |
I think there might be a misconception – they are ending Facebook Analytics, but not the tracking itself. Analytics was just a portal to analyse the collected data. But yeah, nonetheless, tracking is about to take a big hit with iOS 14.5 – thankfully! |
I submitted a PR which updates the SDK for iOS since it's critical right now - iOS 14+ requires Facebook SDK 8 or later for advertising related stuff to work #235 |
For those struggling with this: Just update the plugin's podfile to use SDK v. 11.0.0
|
If I'm not mistaken, the Facebook SDK is set to v5.0, while the current version is 8.2. So far, I'm not experiencing troubles, but this is probably only a matter of time.
Is this plugin still maintained, or is there a reason, why it has not upgraded beyond v5.0?
The text was updated successfully, but these errors were encountered: