Facebook-ios-sdk: Apps suddenly started crashing, crashlytics velocity alert on +[FBSDKEventDeactivationManager updateDeactivatedEvents:]

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

Firebase Crashlytics started to send velocity alerts on ( at the moment ) 4 of our apps, around 10 minutes ago

Podfile:

pod 'FBSDKCoreKit', '~> 6.2'
  pod 'FBSDKGamingServicesKit', '~> 6.2'
  pod 'FBSDKLoginKit', '~> 6.2'
  pod 'FBSDKShareKit', '~> 6.2'
Fatal Exception: NSInvalidArgumentException
0  CoreFoundation                 0x182a2e364 __exceptionPreprocess
1  libobjc.A.dylib                0x181c74528 objc_exception_throw
2  CoreFoundation                 0x182a3b828 __methodDescriptionForSelector
3  CoreFoundation                 0x182a33d10 ___forwarding___
4  CoreFoundation                 0x182918ecc _CF_forwarding_prep_0
5  REDACTED                    0x102e3c784 +[FBSDKEventDeactivationManager updateDeactivatedEvents:] + 64 (FBSDKEventDeactivationManager.m:64)
6  REDACTED                    0x102e66208 +[FBSDKServerConfigurationManager processLoadRequestResponse:error:appID:] + 259 (FBSDKServerConfigurationManager.m:259)
7  REDACTED                    0x102e4a35c __69+[FBSDKGraphRequestPiggybackManager addServerConfigurationPiggyback:]_block_invoke + 155 (FBSDKGraphRequestPiggybackManager.m:155)
8  REDACTED                    0x102e48bd8 -[FBSDKGraphRequestMetadata invokeCompletionHandlerForConnection:withResults:error:] + 41 (FBSDKGraphRequestMetadata.m:41)
9  REDACTED                    0x102e464b0 __82-[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:]_block_invoke + 806 (FBSDKGraphRequestConnection.m:806)
10 REDACTED                    0x102e463a4 -[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:] + 839 (FBSDKGraphRequestConnection.m:839)
11 REDACTED                    0x102e45fb4 __64-[FBSDKGraphRequestConnection completeWithResults:networkError:]_block_invoke + 788 (FBSDKGraphRequestConnection.m:788)
12 CoreFoundation                 0x182907828 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:]
13 REDACTED                    0x102e45d78 -[FBSDKGraphRequestConnection completeWithResults:networkError:] + 767 (FBSDKGraphRequestConnection.m:767)
14 REDACTED                    0x102e45234 -[FBSDKGraphRequestConnection completeFBSDKURLSessionWithResponse:data:networkError:] + 634 (FBSDKGraphRequestConnection.m:634)
15 REDACTED                    0x102e43408 __36-[FBSDKGraphRequestConnection start]_block_invoke_3 + 242 (FBSDKGraphRequestConnection.m:242)
16 libdispatch.dylib              0x1823aaa54 _dispatch_call_block_and_release
17 libdispatch.dylib              0x1823aaa14 _dispatch_client_callout
18 libdispatch.dylib              0x1823b7698 _dispatch_main_queue_callback_4CF$VARIANT$mp
19 CoreFoundation                 0x1829d6544 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
20 CoreFoundation                 0x1829d4120 __CFRunLoopRun
21 CoreFoundation                 0x1828f3e58 CFRunLoopRunSpecific
22 GraphicsServices               0x1847a0f84 GSEventRunModal
23 UIKit                          0x18bf7367c UIApplicationMain
24 REDACTED                    0x102c9a570 main + 41 (main.mm:41)
25 libdyld.dylib                  0x18241056c start

Most helpful comment

you can simply thumb up the first post instead of spam posting with +1s.

All 176 comments

+1

Our AppStore build is crashing on application launch 😱

+1

Duplicate of #1430

+1

Same here
pod 'FBSDKCoreKit', '5.5.0'
pod 'FBSDKShareKit', '5.5.0'
pod 'FBSDKLoginKit', '5.5.0'

+1

+1

+1

+1

+1 πŸ˜–

+1

+1

+1

+1

what are u doin Facebook.......

+1

Tweet to FB, let's hope they are listening 😱

https://twitter.com/manish_rathi_/status/1281541264425484289?s=20

+1

+1

+1

you can simply thumb up the first post instead of spam posting with +1s.

+1 😭

+1 Happening second time within 2 months. Please fix it.

+1 to spam more

+1

+1

+1

+1

I will say keep doing +1 until someone says we are working on it :p so one more +1 from my end

We are seeing the same issue, crashes are immediate

@joesus @tianqibt @clang13 @codytwinton @onebit @robtimp @dzhuowen can you please raise this?

γ…‡γ„·

Crashing here as well - 5.15.1 - I think poor Crashlytics is going to die again soon

+1

+1

+1

+1

Does anyone have this crash on SDK version 7.x.x?

+1

+1

+1, I like idiot debugging... why app crashing... again facebook broke >_<

Does anyone have this crash on SDK version 7.x.x?

I do

Does anyone have this crash on SDK version 7.x.x?

7.0.0 is crashing

GraphQL API is not working, server is down...

+100

+1 our app just started crashing because of this.

+101

+102

+103

+104

+200
(Increasing the bid price)

+201

_folds_

If you're reading this, I implore you to _really_ consider whether you need this SDK in your codebase.

So solve this problem, go to Facebook Developer page > Analytics and disable automatic Events. Solved for me.

https://developers.facebook.com/apps

They responded just few mintues ago.
Screenshot 2020-07-10 at 4 17 34 PM

+1

πŸ‘Ž

+1

+1
I know what you feel

zaebali

Found a solution! πŸŽ‰

Remove the following lines from your Podfile:

pod 'FBSDKCoreKit'
pod 'FBSDKLoginKit'
pod 'FBSDKShareKit'

++

++

So solve this problem, go to Facebook Developer page > Analytics and disable automatic Events. Solved for me.

https://developers.facebook.com/apps

I already had this option turned off earlier, but it crashing

+10086

+1

Same here, fix it guys please

https://github.com/facebook/facebook-ios-sdk/issues/1431#issuecomment-656623360

Tried this one and turned off all analytics but still crashing. :(

Nado chinit` bistro!

Also encountered #1430 and #1432

Another month, and another Facebook iOS SDK crashing problem. Time to rethink whether you actually need this SDK in your app, and how it's implemented.

Again half of my apps are crashing, what a joy.

Quick fix: remove Facebook SDK.

+1

+1

+1

I solved the issue by removing facebook functionality. We ditch facebook login for our app.

Keep re-opening and force close and on third or fourth try, your app should be able open fine.

Please stop commenting +1 just use the thump up.

I solved the issue by removing facebook functionality. We ditch facebook login for our app.

you mean you uploaded a new version to the stores? how can you remove the functionality on the current app?

I was playing on Spotify and got crash I thought it was because of iOS 14 beta version
also facing this on PubG Mobile

I solved the issue by removing facebook functionality. We ditch facebook login for our app.

you mean you uploaded a new version to the stores? how can you remove the functionality on the current app?

Yes, it still takes time to process the build. how can you disable on live app?

pidary zaebali

This company is insane... This is a second time in the last few months...

Can anybody reproduce the crash?

+1

+

1

Can anybody reproduce the crash?

Literally everybody.

So solve this problem, go to Facebook Developer page > Analytics and disable automatic Events. Solved for me.

https://developers.facebook.com/apps

Worked for me

@ap4996 do you mind sharing a screenshot of the page?

So solve this problem, go to Facebook Developer page > Analytics and disable automatic Events. Solved for me.
https://developers.facebook.com/apps

Worked for me

can you share how you did it. its not working for us

@ap4996 @narlei
do you mean this? how long did it take to effect?
Looks like not solving it here
image

Our app crash rate went from 0.2% to 65%. 😱

+1

@ap4996 @narlei
do you mean this? how long did it take to effect?
Looks like not solving it here
image

Nothing change for me. Still crashing

@ap4996 @narlei
do you mean this? how long did it take to effect?
Looks like not solving it here
image

yes..this one..took like 15-20 seconds to reflect

So solve this problem, go to Facebook Developer page > Analytics and disable automatic Events. Solved for me.

https://developers.facebook.com/apps

dones't work for me.

@ap4996 @narlei
do you mean this? how long did it take to effect?
Looks like not solving it here
image

Yes, this option, here about 1 minute.

There are two options because one is for iOS and other for Android.

It seems to be back alive for our app. For context: our app didn't have Log In-App Events Automatically turned on in the first place, but it still crashed.

I also received velocity alert.

@ap4996 @narlei
do you mean this? how long did it take to effect?
Looks like not solving it here
image

Yes, this option, here about 1 minute.

There are two options because one is for iOS and other for Android.

I already had both switches disabled, and the crash still occurred on both incidents this year

Its looks like fixed by Facebook, our app is working now :)

but still, will remove Facebook in next release for sure πŸ’―

Still all our apps are not working for us

+1

literally nobody:
facebook: let's destroy the world

Im here for some fun. I never used facebook-sdk and will never. My apps are tracking free; partly because i dont have time to add some metrics, mostly because i don't need them.

So solve this problem, go to Facebook Developer page > Analytics and disable automatic Events. Solved for me.
https://developers.facebook.com/apps

Worked for me

can you share how you did it. its not working for us

Don't work, our app is crashing and this option is already disabled.

Hopefully this will be the push that a lot of developers needed to stop using the Facebook SDK in their apps. A remote kill-switch (intentional or not) for apps running in production is completely unacceptable and financially damaging for the companies that use it.

I cannot disable automatic Events. turning off it and save, doesn't change anything.

So Facebook guys never test before they release? So unprofessional!

It was hours like a nightmare !!

Installing FBSDKCoreKit (7.1.1)
Installing FBSDKLoginKit (7.1.1)
Installing FBSDKShareKit (7.1.1)
Seems to be working... but need to test more...

It seems working again. Don't need to throw tomatos to them even with tests some shit stuffs can happen. We are all developper here we know it. Thank the facebook team for the hotfix.

For me seems to work now, had the same issue but now seems ok

It's seems working again. Don't need to throw tomatos to them even with tests some shit stuffs can happen. We are all developper we know it. Thank the facebook team for the hot fix.

Not really a hotfix if it has been broken for hours, costing $$$ in revenue for various businesses.

It stopped crashing.. not sure if because they fixed it or because we turned off automatic events...
Spotify is still crashing ...

Speculating, of course, but if events is null here... it's not going to have a count. This seems to be the issue our app is having (not fixed yet). They should make sure events exists before seeing how many of them there are 🀷

https://github.com/facebook/facebook-ios-sdk/blob/a6fd9f03f042a9f999b81a824c0b09917beeb927/FBSDKCoreKit/FBSDKCoreKit/AppEvents/Internal/EventDeactivation/FBSDKEventDeactivationManager.m#L74

It's seems working again. Don't need to throw tomatos to them even with tests some shit stuffs can happen. We are all developper we know it. Thank the facebook team for the hot fix.

The fact that this has happened twice in one year, and has such a colossal impact on large and small businesses alike, goes beyond human error.

  • Why weren't additional tests added to catch this issue after the initial hot fix in March?
  • Why weren't processes put in place to make sure this doesn't happen again?

Lack of resource and time really isn't an excuse for an organisation as huge as Facebook

Still crashing

Someone is going to have a rough day at Facebook.

Type checking all parameters in an Objective-C library is 101 (as you can't trust devs, and even less server responses).

If you didn't remove FB SDK from your iOS app until now, then use the Apple sign-in excuse to do so. And fuck (ads) marketing "benefit".

Someone is going to have a rough day at Facebook.

Type checking all parameters in an Objective-C library is 101 (as you can't trust devs, and even less server responses).

If you didn't remove FB SDK from your iOS app until now, then use the Apple sign-in excuse to do so. And fuck (ads) marketing "benefit".

easier said than done! good luck convincing a non tech client with this

We're seeing a reduced crash rate - now at less than 5% but a new crash stack trace

CoreFoundation | __exceptionPreprocess (CoreFoundation)
-- | --
libobjc.A.dylib | objc_exception_throw (libobjc.A.dylib)
CoreFoundation | -[NSOrderedSet initWithSet:copyItems:] (CoreFoundation)
CoreFoundation | ___forwarding___ (CoreFoundation)
CoreFoundation | _CF_forwarding_prep_0 (CoreFoundation)
FBSDKCoreKit | FBSDKRestrictiveDataFilterManager.mΒ lineΒ 66Β inΒ +[FBSDKRestrictiveDataFilterManager updateFilters:] (FBSDKRestrictiveDataFilterManager.m:66)
FBSDKCoreKit | FBSDKServerConfigurationManager.mΒ lineΒ 241Β inΒ +[FBSDKServerConfigurationManager processLoadRequestResponse:error:appID:] (FBSDKServerConfigurationManager.m:241)
FBSDKCoreKit | __78+[FBSDKServerConfigurationManager loadServerConfigurationWithCompletionBlock:]_block_invoke (FBSDKServerConfigurationManager.m:0)
FBSDKCoreKit | FBSDKGraphRequestMetadata.mΒ lineΒ 41Β inΒ -[FBSDKGraphRequestMetadata invokeCompletionHandlerForConnection:withResults:error:] (FBSDKGraphRequestMetadata.m:41)
FBSDKCoreKit | FBSDKGraphRequestConnection.mΒ lineΒ 806Β inΒ __82-[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:]_block_invoke (FBSDKGraphRequestConnection.m:806)
FBSDKCoreKit | FBSDKGraphRequestConnection.mΒ lineΒ 839Β inΒ -[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:] (FBSDKGraphRequestConnection.m:839)
FBSDKCoreKit | FBSDKGraphRequestConnection.mΒ lineΒ 788Β inΒ __64-[FBSDKGraphRequestConnection completeWithResults:networkError:]_block_invoke (FBSDKGraphRequestConnection.m:788)
CoreFoundation | __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ (CoreFoundation)
CoreFoundation | -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] (CoreFoundation)
FBSDKCoreKit | FBSDKGraphRequestConnection.mΒ lineΒ 767Β inΒ -[FBSDKGraphRequestConnection completeWithResults:networkError:] (FBSDKGraphRequestConnection.m:767)
FBSDKCoreKit | FBSDKGraphRequestConnection.mΒ lineΒ 634Β inΒ -[FBSDKGraphRequestConnection completeFBSDKURLSessionWithResponse:data:networkError:] (FBSDKGraphRequestConnection.m:634)
FBSDKCoreKit | __36-[FBSDKGraphRequestConnection start]_block_invoke_3 (FBSDKGraphRequestConnection.m:0)
libdispa...ch.dylib | _dispatch_call_block_and_release (libdispatch.dylib)
libdispa...ch.dylib | _dispatch_client_callout (libdispatch.dylib)
libdispa...ch.dylib | _dispatch_main_queue_callback_4CF$VARIANT$mp (libdispatch.dylib)
CoreFoundation | __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ (CoreFoundation)
CoreFoundation | __CFRunLoopRun (CoreFoundation)
CoreFoundation | CFRunLoopRunSpecific (CoreFoundation)
GraphicsServices | GSEventRunModal (GraphicsServices)
UIKitCore | UIApplicationMain (UIKitCore)
GrubHub | main.mΒ lineΒ 16Β inΒ main (main.m:16)
libdyld.dylib | 0x1b1254000 + 6384

Firebase is reporting the same crash report from my app too.

Spotify crashes on startup

Someone is going to have a rough day at Facebook.

Type checking all parameters in an Objective-C library is 101 (as you can't trust devs, and even less server responses).

If you didn't remove FB SDK from your iOS app until now, then use the Apple sign-in excuse to do so. And fuck (ads) marketing "benefit".

That's the dream, but migrating folks with Facebook authenticated accounts will be a massive pain for our users.

Is there an alternative to this SDK that can do the Facebook account authentication (I seem to recall someone mentioning an aws alternative during the last incident)

+[FBSDKRestrictiveDataFilterManager updateFilters:] (FBSDKRestrictiveDataFilterManager.m:60)
+[FBSDKServerConfigurationManager processLoadRequestResponse:error:appID:] (FBSDKServerConfigurationManager.m:258)
__78+[FBSDKServerConfigurationManager loadServerConfigurationWithCompletionBlock:]_block_invoke (FBSDKServerConfigurationManager.m:0)
-[FBSDKGraphRequestMetadata invokeCompletionHandlerForConnection:withResults:error:] (FBSDKGraphRequestMetadata.m:41)
__82-[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:]_block_invoke (FBSDKGraphRequestConnection.m:800)
-[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:] (FBSDKGraphRequestConnection.m:833)
__64-[FBSDKGraphRequestConnection completeWithResults:networkError:]_block_invoke (FBSDKGraphRequestConnection.m:782)
___53-[__NSArrayM enumerateObjectsWithOptions:usingBlock:]_block_invoke + 87
-[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 159
-[FBSDKGraphRequestConnection completeWithResults:networkError:] (FBSDKGraphRequestConnection.m:761)
-[FBSDKGraphRequestConnection completeFBSDKURLSessionWithResponse:data:networkError:] (FBSDKGraphRequestConnection.m:628)

easier said than done! good luck convincing a non tech client with this

Yeah, I know :( that's why some apps I work on are crashing <_<

Is there an alternative to this SDK that can do the Facebook account authentication (I seem to recall someone mentioning an aws alternative during the last incident)

@XmasRights For log-in, you can use the web alternative by redirecting to safari in-app (not documented well, but there was a github project I forked and updated for FB a while ago, just removed it recently) : https://github.com/Vinzius/Simplicity

We are also getting the same......

We're seeing a reduced crash rate - now at less than 5% but a new crash stack trace

CoreFoundation | __exceptionPreprocess (CoreFoundation)
-- | --
libobjc.A.dylib | objc_exception_throw (libobjc.A.dylib)
CoreFoundation | -[NSOrderedSet initWithSet:copyItems:] (CoreFoundation)
CoreFoundation | ___forwarding___ (CoreFoundation)
CoreFoundation | _CF_forwarding_prep_0 (CoreFoundation)
FBSDKCoreKit | FBSDKRestrictiveDataFilterManager.m line 66 in +[FBSDKRestrictiveDataFilterManager updateFilters:] (FBSDKRestrictiveDataFilterManager.m:66)
FBSDKCoreKit | FBSDKServerConfigurationManager.m line 241 in +[FBSDKServerConfigurationManager processLoadRequestResponse:error:appID:] (FBSDKServerConfigurationManager.m:241)
FBSDKCoreKit | __78+[FBSDKServerConfigurationManager loadServerConfigurationWithCompletionBlock:]_block_invoke (FBSDKServerConfigurationManager.m:0)
FBSDKCoreKit | FBSDKGraphRequestMetadata.m line 41 in -[FBSDKGraphRequestMetadata invokeCompletionHandlerForConnection:withResults:error:] (FBSDKGraphRequestMetadata.m:41)
FBSDKCoreKit | FBSDKGraphRequestConnection.m line 806 in __82-[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:]_block_invoke (FBSDKGraphRequestConnection.m:806)
FBSDKCoreKit | FBSDKGraphRequestConnection.m line 839 in -[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:] (FBSDKGraphRequestConnection.m:839)
FBSDKCoreKit | FBSDKGraphRequestConnection.m line 788 in __64-[FBSDKGraphRequestConnection completeWithResults:networkError:]_block_invoke (FBSDKGraphRequestConnection.m:788)
CoreFoundation | __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ (CoreFoundation)
CoreFoundation | -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] (CoreFoundation)
FBSDKCoreKit | FBSDKGraphRequestConnection.m line 767 in -[FBSDKGraphRequestConnection completeWithResults:networkError:] (FBSDKGraphRequestConnection.m:767)
FBSDKCoreKit | FBSDKGraphRequestConnection.m line 634 in -[FBSDKGraphRequestConnection completeFBSDKURLSessionWithResponse:data:networkError:] (FBSDKGraphRequestConnection.m:634)
FBSDKCoreKit | __36-[FBSDKGraphRequestConnection start]_block_invoke_3 (FBSDKGraphRequestConnection.m:0)
libdispa...ch.dylib | _dispatch_call_block_and_release (libdispatch.dylib)
libdispa...ch.dylib | _dispatch_client_callout (libdispatch.dylib)
libdispa...ch.dylib | _dispatch_main_queue_callback_4CF$VARIANT$mp (libdispatch.dylib)
CoreFoundation | __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ (CoreFoundation)
CoreFoundation | __CFRunLoopRun (CoreFoundation)
CoreFoundation | CFRunLoopRunSpecific (CoreFoundation)
GraphicsServices | GSEventRunModal (GraphicsServices)
UIKitCore | UIApplicationMain (UIKitCore)
GrubHub | main.m line 16 in main (main.m:16)
libdyld.dylib | 0x1b1254000 + 6384

Same here.
The sdk version is 5.5.0, and it's still crashing

+1

@XmasRights

@ap4996 @narlei
do you mean this? how long did it take to effect?
Looks like not solving it here
image

Yes, this option, here about 1 minute.
There are two options because one is for iOS and other for Android.

I already had both switches disabled, and the crash still occurred on both incidents this year

Our app stopped crashing.
Took like 10 minutes.
Spotify is still crashing, so i assume that did the trick.
Notice tho the screenshot has the Android sdk circled, we turned that one back on. The one above it is iOS

+1 crashing on 5.6.0. Turning airplane mode on and launching app mitigates the issue

Facebook SDK is radioactive material, remove it from your apps.

Same here. suddenly our app started crashing.

fml it's Friday night GMT+08:00
θ‰δ»–ε¦ˆηš„θ€ε­ηš„ε‘¨δΊ”ε•Š

If you can block DNS access to facebook.com

The apps will stop crashing. Of course the integration won't work either.

Is there an alternative to this SDK that can do the Facebook account authentication (I seem to recall someone mentioning an aws alternative during the last incident)

@XmasRights For log-in, you can use the web alternative by redirecting to safari in-app (not documented well, but there was a github project I forked and updated for FB a while ago, just removed it recently) : https://github.com/Vinzius/Simplicity

It's said that native apps must use official SDK here
Has anyone tried unofficial SDK or manual login and does it work?

Is there an alternative to this SDK that can do the Facebook account authentication (I seem to recall someone mentioning an aws alternative during the last incident)

@XmasRights For log-in, you can use the web alternative by redirecting to safari in-app (not documented well, but there was a github project I forked and updated for FB a while ago, just removed it recently) : https://github.com/Vinzius/Simplicity

It's said that native apps must use official SDK here
Has anyone tried unofficial SDK or manual login and does it work?

I've build a working alternative "SDK" the last time. But it's not allowed by FB's Platform Policy.

If you still need to use FBSDK but are considering building a "kill switch", you might want to check FacebookAutoInitEnabled in the official document for how not to auto init.

Same here !

Pinterest also crashes on startup

Grubhub is still seeing a crash rate of 3%, now at
FBSDKRestrictiveDataFilterManager.m line 66 in [FBSDKRestrictiveDataFilterManager updateFilters:]

Has been fixed

Just stopped crashing

At least migrating the SDK to Swift could improve the SDK.. It would be way safer πŸ€·β€β™‚οΈ

Still crashing...

on iOS 14 Public Beta 2, it seems to be working fine.

seems to be fixed now, the FB bug report is here:
developers.facebook.com/support/bugs/329763701368293

And the status on it:
developers.facebook.com/status/issues/1739188102911114

yup, working again!

I will say keep doing +1 until someone says we are working on it :p so one more +1 from my end

Please, open a PR fixing it or thumbs up the post and wait for a fix. Spam with +1s will not fix it faster.

use android)

@artemshevch
image

@@ This is the serious bug. Could the facebook team help us resolve this issue ?

image

Here's a permanent fix:

1. Open Xcode
2. Select your project
3. Look at the top middle
4. Select Swift Package Manager menu
5. Find Facebook Package - remove

This is ironic πŸ™‚

crash all apps integrated facebook sdk such as Tinder, PUBG ,Tiktok....
https://9to5mac.com/2020/07/10/app-crash-facebook-sdk/

so many crashes that Firebase Crashlytics can't process all of then
I have 503 error

Best solution:

Remove the Facebook SDK, use their auth API to perform the Facebook login instead.

unless you use Facebook for other analytics.

You all know Facebook is doing some new shady business under the hood, like how they got their dev certs revoked last year by Apple for abusing the enterprise program and spying on kids.

You all should be cautious of what methods they are swizzilng, you can’t trust Zucc!

It seems like they have fixed the issue
https://developers.facebook.com/status/issues/1739188102911114/

"We identified the issue quickly and resolved it. "

Best solution:

Remove the Facebook SDK, use their auth API to perform the Facebook login instead.

unless you use Facebook for other analytics.

Will Facebook allow using web API for login instead of their SDKs?

"We identified the issue ~quickly~ and resolved it. "

Do we require to update the SDK for that?

Best solution:

Remove the Facebook SDK, use their auth API to perform the Facebook login instead.

unless you use Facebook for other analytics.

Will Facebook allow using web API for login instead of their SDKs?

Their API Is meant for web browser login but you could theoretically do it with a WKWebView.

Duplicate of #1427

Do I need to update the SDK to the latest version to resolve this issue? the current SDK version is 7.0.0

ppl really complaining about an open source project? How toxic is the ios community

ppl really complaining about an open source project? How toxic is the ios community

Damn.. if you think that was toxic, just wait until you find out what Facebook did to our democracy.

For Facebook login there are instructions on doing it Framework free here:
https://dev.to/marinbenc/implementing-facebook-login-on-ios-without-facebook-sdk-3k05

I also implemented this at the weekend to make a near drop replacement for login only:
https://github.com/josephlord/FMZDropInMinimalFacebookLogin

@josephlord I've done a similar thing the last time. I should remind that this violates FB's Platform Policy.

https://gist.github.com/ethanhuang13/70c27ea9b5eb53199bc67c3bc9d47b7b

Hello Everyone,

_Best solution:_ Remove the Facebook SDK from your app 😍
_Another solution:_ Disable Facebook SDK Automatic Initialization πŸ’ͺ🏻

Apologies for

The fix on my end was

[FBSDKSettings setAutoLogAppEventsEnabled:NO];

For me, the best solution was create Framework wrappers and control it by feature flag.

This article talks about:
https://narlei.com/development/stay-safe-using-third-party-sdks-in-swift/

Was this page helpful?
0 / 5 - 0 ratings