Facebook-ios-sdk: Allow developers to implement Facebook Login without the official SDK

Created on 10 Jul 2020 · 5Comments · Source: facebook/facebook-ios-sdk

The current Facebook Developer Policy requires that developers use the official Facebook SDK when implementing Facebook Login in their native app. Given that Facebook cannot ensure the stability of their SDK (resulting in the crashing of client apps), developers should have a policy-compliant option for implementing the login API themselves to avoid Facebook's QA practices rendering their apps unusable.

Section 8.2 of the above-linked page:

Native iOS and Android apps that implement Facebook Login must use our official SDKs for login.

Source

Jumhyn

👍57 🎉5

Most helpful comment

If you need sample code of this, see my gist with just ~100 loc.

ethanhuang13 on 10 Jul 2020

👍8 🎉1

All 5 comments

Why would they, when it would reduce the tracking they could do in a 3rd party app? This is Facebook. Let's be realistic

vishalnandagopal on 10 Jul 2020

👍8 👀4

If you need sample code of this, see my gist with just ~100 loc.

ethanhuang13 on 10 Jul 2020

👍8 🎉1

People should just not use Facebook SDK and remove Facebook Login. It’s that simple. Any developer still using the SDK is complicit in this behavior and should be given a one star review on App Store whenever their silly app crashes because of the SDK.

LeoNatan on 16 Jul 2020

The AppLaunch Xcode template shows 120ms consumption on FacebookSDK! That's a good point to write custom login and do not execute thousands lines of code for that simple action.

mojidabckuu on 9 Aug 2020

There is also another reason for this. We're a kids category app and we've had Facebook login for years. But recently we've been stuck in review for weeks, because of code references to IDFA and Facebook collecting anonymous ID's (which shouldn't be a problem, but apparently Apple doesn't like Facebook very much).