Facebook-ios-sdk: -[NSNull count]: unrecognized selector sent to instance 0x22d0ed7f0

[Neil20170220]

SDK version: iOS 6.5.2

[Neil20170220]

Please help

[ferico55]

here's better stack trace

[barisyazganc]

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

[shengyang998]

1374

[vladambartsumyan]

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

[danwey]

same here
6.3.0 and 5.0.2

[georgescumihai]

Version 7.0 same issue

[TheyCallMeTank]

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

[jolyot]

same here

Using FBSDKCoreKit (5.13.1)
Using FBSDKLoginKit (5.13.1)

[yaminoma]

Same Issue
When will it be fixed?

[olenhad]

Same issue here with 5.5.0

[racer1988]

+1

[zavsby]

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.

[Sanich63]

[acali18]

Same issue, right where @Sanich63 shows on the screenshot

[fireup]

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

[DarrenDuXuan]

restrictive_data_filter_params NSNull.count

[jonashinge]

same here using 7.0.0.

[davidchristiandy]

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.

[magnett]

7.0.0 is crashing, 7.1.1 seems stable

[hemanthmpkumar]

+1

[abuharsky]

+1 crashing

[Balashov152]

+1 crashing

[Tomoy]

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

[darlanxw]

+1 crashing

[zavsby]

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

[Mehul1437]

Same here +1 crashing

[Subloran]

Also crashes [FBSDKRestrictiveDataFilterManager updateFilters:] + 62. There is a check for restrictiveParams.count, but restrictiveParams is NSNull object.

[peterdk]

Same

[Tomoy]

fixed??

[Nackwork]

Guys, our entire portfolio is crashing! Haven't you learned your lessons from May 7, 2020?

It's been 40min of total blackout and still no response?

I guess, we need more memes for FB QA department :)

[Mehul1437]

4 0x00000001052ff274 in +[FBSDKRestrictiveDataFilterManager updateFilters:] at /Users/travis/build/facebook/facebook-objc-sdk/FBSDKCoreKit/FBSDKCoreKit/AppEvents/Internal/FBSDKRestrictiveDataFilterManager.m:60

[ivaneChen]

我也是～中招了

[Tomoy]

fixed??

Its randomly working and crashing for me

[ivaneChen]

Same here +1 crashing

[charlieInDen]

Seriously - Start removing this SDK soon!!

[danwey]

别说中文。professional.

[dave7280]

That's how it ends when 50% of all application rely on one sdk.
You can only blame yourself. This already happened before at least once, so warnings were in place.

[ivaneChen]

別說簡體字

[fireup]

Guys, our entire portfolio is crashing! Haven't you learned your lessons from May 7, 2020?

It's been 40min of total blackout and still no response?

I guess, we need more memes for FB QA department :)

Apparently they fired the wrong guy in May.

[mzying2013]

6.5.1 crash, please help!

[mweststrate]

Linking for visibility: https://developers.facebook.com/status/issues/1739188102911114/

[batuhanaltun]

jh doeqwdwdhıou hewoıdwddoıewho ıofwdwdehwf ejf eıj ıfeıq jıdfj ıejd ıej ıfje jıfej ıeıf ceqjdı w0ıd ıw0 jq0dı jw0

I couldn't find a word to describe this event that happened 2 times in a short time.

[sunflash]

please fix ASAP

[burcsade]

unbelievable... second time this year.

[racer1988]

@Neil20170223 Please EDIT the issue with the status link: https://developers.facebook.com/status/issues/1739188102911114/

[JZWDream]

6.5.0,please help

[nicoyuste]

Groupon app is crashing on startup due to the same issue.

[mskalgorepublic]

They are responding at last.

[oliver98844]

Same in our app...cannot open Spotify, either 😱

SDK version 7.0.0

[absolute-heike]

🤦‍♀️ Looks like facebook hired a lot of Swift engineers in the last time and let them do stuff to the networking code 😂

[hongdangodori]

Same in our app... plz help..

[Geeks2020]

Does anyone try to degrade its version?

[vdugnist]

same, FBSDKLoginKit 5.6.0

[Salman144017]

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

[Tomoy]

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

still crashing here

[Geeks2020]

haha I am not facing this alone. It is working for now

[nicoyuste]

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

Not for me. I still see Groupon, Spotify, Strava, Wallapop apps crashing...

[vijay0964]

Not crashing in 7.1.1 version.

[patrikqvarnstrom]

This is the new thanks, Obama meme.

Thanks, Facebook!

[ankitatdelhii]

Seems like everyone is facing this issue. Thank God! I am not alone.😭

[Sanich63]

Just keep it here...

[nicoyuste]

Stack trace I see when I debug my app:

2020-07-10 13:20:10.002959+0200 XXX[65519:1877435] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull count]: unrecognized selector sent to instance 0x7fff80618070'
*** First throw call stack:
(
    0   CoreFoundation                      0x00007fff23c7127e __exceptionPreprocess + 350
    1   libobjc.A.dylib                     0x00007fff513fbb20 objc_exception_throw + 48
    2   CoreFoundation                      0x00007fff23c91fd4 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132
    3   CoreFoundation                      0x00007fff23c75c4c ___forwarding___ + 1436
    4   CoreFoundation                      0x00007fff23c77f78 _CF_forwarding_prep_0 + 120
    5   XXX                             0x000000010bc79f2d +[FBSDKRestrictiveDataFilterManager updateFilters:] + 109
    6   XXX                             0x000000010bc7f4d1 +[FBSDKServerConfigurationManager processLoadRequestResponse:error:appID:] + 3665
    7   XXX                             0x000000010bc61a7f __69+[FBSDKGraphRequestPiggybackManager addServerConfigurationPiggyback:]_block_invoke + 175
    8   XXX                             0x000000010bc5f208 -[FBSDKGraphRequestMetadata invokeCompletionHandlerForConnection:withResults:error:] + 248
    9   XXX                             0x000000010bc5a8db __82-[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:]_block_invoke + 251
    10  XXX                             0x000000010bc5a6fd -[FBSDKGraphRequestConnection processResultBody:error:metadata:canNotifyDelegate:] + 1149
    11  XXX                             0x000000010bc5a1e6 __64-[FBSDKGraphRequestConnection completeWithResults:networkError:]_block_invoke + 1494
    12  CoreFoundation                      0x00007fff23c3f1e7 __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7
    13  CoreFoundation                      0x00007fff23b847d4 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 228
    14  XXX                             0x000000010bc59a9e -[FBSDKGraphRequestConnection completeWithResults:networkError:] + 1102
    15  XXX                             0x000000010bc584e0 -[FBSDKGraphRequestConnection completeFBSDKURLSessionWithResponse:data:networkError:] + 2336
    16  XXX                             0x000000010bc54b1a __36-[FBSDKGraphRequestConnection start]_block_invoke_3 + 186
    17  XXX                             0x000000010bc5ca66 __73-[FBSDKGraphRequestConnection invokeHandler:error:response:responseData:]_block_invoke + 70
    18  libdispatch.dylib                   0x000000011c4e9dd4 _dispatch_call_block_and_release + 12
    19  libdispatch.dylib                   0x000000011c4ead48 _dispatch_client_callout + 8
    20  libdispatch.dylib                   0x000000011c4f8de6 _dispatch_main_queue_callback_4CF + 1500
    21  CoreFoundation                      0x00007fff23bd4049 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
    22  CoreFoundation                      0x00007fff23bceca9 __CFRunLoopRun + 2329
    23  CoreFoundation                      0x00007fff23bce066 CFRunLoopRunSpecific + 438
    24  GraphicsServices                    0x00007fff384c0bb0 GSEventRunModal + 65
    25  UIKitCore                           0x00007fff48092d4d UIApplicationMain + 1621
    26  XXX                             0x000000010916da20 main + 1296
    27  libdyld.dylib                       0x00007fff5227ec25 start + 1
    28  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException

[Kalzem]

Can Facebook learn from their mistake and have a proper QA instead of making crash all iOS apps using their SDK?

[PetrBodnar]

Our apps can start again. Looks like they fixed that issue

[nshtg]

Solution: We won't use FB SDK in the future. Thank you Mark suckerberg.

[ltk-daniel-zapater]

Wallapop working again, Spotify still crashing

[danglingP0inter]

So Fb developers also test their changes at prod. I'm so glad that I'm not alone.

[vrutberg]

FWIW I'm also getting this crash right now

[apogodin]

Temporary fix while developing

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

[jasondinh]

Permanent fix in dev and production

1. Remove FB SDK
2. ???
3. Profit

[vlmxs]

May this be the reason PUBG Mobile is not working on my iPad?

Yes, and Spotify as well...

[Geeks2020]

Permanent fix in dev and production

1. Remove FB SDK
2. ???
3. Profit

haha do we have a choice?

[nicoyuste]

You are not alone: https://downdetector.com

[DouglasMarq]

Stop blaming entirely at Facebook, your app is crashing because it is relying entirely at a 3rd party SDK..

[UnknownNPC]

Friday deployment went fine.

[Salman144017]

Stop blaming entirely at Facebook, your app is crashing because it is relying entirely at a 3rd party SDK..

So it's wrong to allow social login in your app?

[burcsade]

Fail fast, fail everyone

[iBodia]

same here

Using FBSDKCoreKit (6.3.0)
Using FBSDKLoginKit (6.3.0)

[skibitsky]

So it's wrong to allow social login in your app?

Now we learned that it's wrong :)

[DouglasMarq]

So it's wrong to allow social login in your app?

It's not wrong to allow social login at your app, it is wrong to rely your app at a SDK, you can handle this in another way, through cache or temporary data to make calls later.

Edit: Oh damn facebook sdk having issues, my app is not working, i'll just blame at it and wait for a result.

[Cool04ek]

Same here 5.2.3

[ckcharchit]

May this be the reason PUBG Mobile is not working on my iPad?

Yes, and Spotify as well...

Yes, Call of Duty Mobile, ludo star, as well.

[sandeepbol]

@DouglasMarq From where do you buy weed mate? 🚬

[Salman144017]

So it's wrong to allow social login in your app?

It's not wrong to allow social login at your app, it is wrong to rely your app at a SDK, you can handle this in another way, through cache or temporary data to make calls later.

Edit: Oh damn facebook sdk having issues, my app is not working, i'll just blame at it and wait for a result.

Read your comment again and let me know if you find any sense in it.

[apisdk]

🤦‍♂️ ...

[BrianValente]

So it's wrong to allow social login in your app?

It's not wrong to allow social login at your app, it is wrong to rely your app at a SDK, you can handle this in another way, through cache or temporary data to make calls later.

Edit: Oh damn facebook sdk having issues, my app is not working, i'll just blame at it and wait for a result.

Did you ever made an iOS app?

[revolter]

Isn't Facebook using this SDK? How could they not notice that it crashes? You don't need extensive tests. Simply open the app. 🤦🏻‍♂️

[1Podoshva]

The same issue.
My app crashes only on a simulator, for a device the app does not crash(log in via FB works fine).
In a device and simulator, the object of events is NSNull class type.
FBSDKCoreKit (5.15.1)
FBSDKLoginKit (5.15.1)
FBSDKShareKit (5.15.1)

[RuiAAPeres]

Facebook, WhatsApp, Instagram and FB's Messenger are working.

[apolegoshko]

[beretis]

So it's wrong to allow social login in your app?

It's not wrong to allow social login at your app, it is wrong to rely your app at a SDK, you can handle this in another way, through cache or temporary data to make calls later.

Edit: Oh damn facebook sdk having issues, my app is not working, i'll just blame at it and wait for a result.

Dude, even if I comment out import of the sdk, its still crashing. I have to remove SDK, now tell me about that. Im not relying on fb SDK, facebook login is just a feature, and the documented way how to implement it is to use their sdk. If it would crash only after fb login I get that. But if it crashes on startup when you're not even using the sdk, I think its safe to point finger at facebook

[skibitsky]

I can confirm that the issue was resolved for my app

[dave7280]

So it's wrong to allow social login in your app?

It's not wrong to allow social login at your app, it is wrong to rely your app at a SDK, you can handle this in another way, through cache or temporary data to make calls later.
Edit: Oh damn facebook sdk having issues, my app is not working, i'll just blame at it and wait for a result.

Did you even made an iOS app?

He's completely right, but plenty of developers have problems understanding business.

It's your job as developer to choose components you rely on, carefully.
Everyone knew, that exactly same issue happened already before, yet people are very surprised that same problem is here again.

Your business client wont care if it's facebook fault. You were paid to write an app and it's your fault. App you designed is not working, business is losing money and that's it. That's all what matters.

It's developers decision to choose this SDK, you could use something else or implement stuff on your own.
Asses the risk on the components you use, especially if they kill your app twice within 2 months.

[Geeks2020]

+1, The issue is already fixed for my apps. I use FB login.

[revolter]

you could use something else

Like what? If not the official and recommended SDK.

[sandeepbol]

Facebook, WhatsApp, Instagram and FB's Messenger are working.

Dude Facebook and Facebook messenger are React native apps and don't use this SDK.

[Magestro]

https://twitter.com/elonmusk/status/1260852444818362369?lang=en

[demensdeum]

@apogodin must be:
@interface NSNull (FacebookFix)

[hardW]

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

[apogodin]

@apogodin must be:
@interface NSNull (FacebookFix)

"FacebookFix" should be in investing in ObjC developers

[iliaprokhorov]

@apogodin This case is raising warning in Swift

[sandeee1928]

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

[Suvitruf]

[zhuravel-sergey]

pidary zaebali

[Salman144017]

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.

[Ricowere]

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

[cruftyoldsysadmin]

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

[Salman144017]

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.

[hardW]

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.

[dyumin]

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.

[own2pwn]

nu 4e zato O(n) mojem

[TheNamesJames]

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! 🏎

[diskman86]

Seems Facebook fixed it. Can anyone confirm?

[alekseenkodev]

Seems Facebook fixed it. Can anyone confirm?

yes

[chriscborg]

yes fixed

[zavsby]

yes, it's fixed now.

[varyP]

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

[Mart-Bogdan]

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

[joesus]

Duplicate of #1427

[mzying2013]

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

[wangguan1]

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

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