-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Used the SDK version of 5.0.2, and this afternoon suddenly caused a complete crash of the application #1429
Comments
I have faced the same issue and this causes crash on launch up. Crash Information: -[NSNull count]: unrecognized selector sent to instance 0x1c6877ad8' Hope you help us to solve this problem as soon as possible, thank you very much! |
Suddenly we are having the same issue with our app that was working fine before.
|
related to #1430 more stack traces there |
Yes, they change some responses in the completion handler. Handler expecting some value in count in FBSDKGraphRequestConnection |
wtf fb engineers |
Real rubbish, this is the second time this year |
Do you have a timely solution? I'm really worried |
I have integrated it into my app, I need some functions of fb, now the initialization has failed, the app crashes as soon as it is opened |
Any suggestions how to implement secure authentication through facebook without it? |
Any fb fix soon? |
It has started working now. I believe they reverted the change. |
I haven't solved it yet, I'm very anxious |
Not yet |
Lol I have the same issue |
Lol we're in the same boat。 |
Same. Here's the crashlog
` |
Someone has an update, my app started crashing on launch |
FF: All our apps are crashing!! Someone with a workaround?? |
the crash rate is 10-9, on of the sessions survives - doesn't mean its fixed, it's still crashing, what an ugly show, removing the sdk as soon as this is sorted |
For me updating FBSDKLoginKit and FBSDKShareKit to 5.15.1 (was 5.5.0) seem to fix an issue. Please double check. |
Same issue here. Waze and Spotify crash during initialization. |
Is it Planned obsolescence to force developers to update the SDK! 🤣 |
UPDATE |
This caused my app to crash like crazy while it was live, how would i prevent something like this from happening in the future ? any suggestion ?? |
Use remote switch (LaunchDarkly?) to disable FB SDK? |
Please check this thread with some ideas More specifically this: |
Duplicate of #1427 |
I used the SDK version of 5.0.2, and this afternoon suddenly caused a complete crash of the application
Crash information
-[NSNull count]: unrecognized selector sent to instance 0x1cd6fe1e0
2020-07-10 17:24:26.052924+0800 OSDemo[4198:604792] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull count]: unrecognized selector sent to instance 0x1cd6fe1e0'
*** First throw call stack:
(0x18b944300 0x18b658c1c 0x18b842a90 0x18b948a60 0x18b94ad60 0x102e3e8c4 0x102e36e0c 0x102e35a3c 0x102e73ee0 0x102e7cdc4 0x102e7cca8 0x102e7c858 0x18b91667c 0x18b814248 0x102e7c5fc 0x102e7b948 0x102e79930 0x103471d10 0x10347318c 0x103481d14 0x18b8bf6b0 0x18b8ba2c8 0x18b8b98f4 0x195cd0604 0x18fa8d358 0x102a3f1a4 0x18b7352dc)
libc++abi.dylib: terminating with uncaught exception of type NSException
Hope you help me solve this problem as soon as possible, thank you very much!
The text was updated successfully, but these errors were encountered: