Please help

here's better stack trace

Same here! shame on you FB!! what should we do now? just wait for them to release their mistake and rollback?

#1374

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

same here
6.3.0 and 5.0.2

Version 7.0 same issue

same
pod 'FBSDKCoreKit', '5.8.0'
pod 'FBSDKLoginKit', '5.8.0'
pod 'FBSDKShareKit', '5.8.0'

same here

Using FBSDKCoreKit (5.13.1)
Using FBSDKLoginKit (5.13.1)

Same Issue
When will it be fixed?

Same issue here with 5.5.0

+1

Same here, more then 500K of crashes for only last 20 minutes... Is anybody from FB stuff here? It seems the same crashes we had several months ago when almost all apps were affected and not launching.

Same issue, right where @Sanich63 shows on the screenshot

OH COME ON! Not again! Your crash has halted Firebase crashlytics again!

restrictive_data_filter_params NSNull.count

same here using 7.0.0.

I'm suspecting that this might be a backend related issue from FB side, because crash happens on an app that's released a month ago with no update whatsoever to FB SDK. Maybe some wrong values gets sent from their feature flag server or something, and causes crash on the client.

Hope FB can roll back whatever changes quickly.

7.0.0 is crashing, 7.1.1 seems stable

+1

+1 crashing

Oh god, this is happening again, crashing to all my users

+1 crashing

Seems it's night in US and no one react from FB...

Same here +1 crashing

@apogodin must be:
@interface NSNull (FacebookFix)

For me updating FBSDKLoginKit and FBSDKShareKit to 5.15.1 (was 5.5.0) seem to fix an issue. Please double check.

@apogodin must be:
@interface NSNull (FacebookFix)

"FacebookFix" should be in investing in ObjC developers

@apogodin This case is raising warning in Swift

Here’s the facebook bug page, https://developers.facebook.com/support/bugs/329763701368293/

pidary zaebali

For me updating FBSDKLoginKit and FBSDKShareKit to 5.15.1 (was 5.5.0) seem to fix an issue. Please double check.

I am using 5.15.1 and it was crashing initially but now its fixed for about half an hour ago.

FB guys; The problem seems to be happening when a NSNull object is been passed by parameter... So nullable annotation here was not enough...

You will have to revisit all the library to add a if is instance of NSNull then return? 😄

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

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

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

Using anything from Facebook is considered harmful to your business, unless you are Facebook.

It has started working now. I believe they reverted the change.

I am using 5.15.1 and it was crashing initially but now its fixed for about half an hour ago. Try updating to 5.15.1.

For me updating FBSDKLoginKit and FBSDKShareKit to 5.15.1 (was 5.5.0) seem to fix an issue. Please double check.

I am using 5.15.1 and it was crashing initially but now its fixed for about half an hour ago.

If to switch back to 5.5.0 for me it crashes even now( So I guess there is fix that is working for 5.15.1 (or lower?) now.

Temporary fix while developing

@interface NSNull (Fix)
- (NSUInteger)count;
@end
...
@implementation NSNull (Fix)
- (NSUInteger)count
{
    return 0;
}
@end

It's also possible to swizzle updateFilters: and call original implementation with empty NSDictionary in case NSNull is passed. This should do the trick for production hotfix.

nu 4e zato O(n) mojem

This should do the trick for production hotfix

How quickly can your app be submitted, reviewed, approved and then have users update? Before FB issues a fix?
What a Race Condition! 🏎

Seems Facebook fixed it. Can anyone confirm?

Seems Facebook fixed it. Can anyone confirm?

yes

yes fixed

yes, it's fixed now.

Might not be crashing, but we are unable to verify token from our backend. Guess facebook has turned if off for a while.

You should definitely RIIR to make it more memory-safe!

Duplicate of #1427

我写了一个关于这个问题的文章，包含以后此类问题的预防方法： https://blog.mzying.com/index.php/archives/231/

我写了一个关于这个问题的文章，包含以后此类问题的预防方法： https://blog.mzying.com/index.php/archives/231/

这个bug服了，OC里基本类型检查都没有