I prefer toxin. Facebook tastes great, looks great and smells great, like so many toxins do. But, like a toxin, you consume it, and it could be fatal. Facebook is a disgusting company.
They're a pox on the world.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Facebook SDK Issue Causing Some iOS Apps to Crash
- Thread starter MacRumors
- Start date
- Sort by reaction score
They're a pox on the world.
Makes for a pretty compelling reason to use iOS stock apps and services when possible. 
That's a pretty impressive failure that their client code is so awful that it crashes on whatever response the server was returning instead of safely handling it and displaying an error.
Probably not, Facebook get away with a whole bunch of ****. No one seems to care. Sad, but true.
it happen to me too. Spotify was crashing. Reinstalled, rebooted phone. When turn on airplane mode, was allowing sign in into spotity. After many atempts, reworked again.
Multiple iPhone and iPad users are seeing their apps crashing at launch as of this afternoon, and the issue appears to be caused by a faulty Facebook SDK that the apps are using.
There are multiple complaints about apps crashing continually on iOS devices on the MacRumors forums, and a wide range of apps appear to be impacted. Google's Waze app, for example, won't launch, and there have been complaints about apps that include Pinterest, Spotify, Adobe Spark, Quora, TikTok, and others.
Multiple developers on GitHub have attributed the problem to a Facebook software development kit used by the apps for sign-in purposes. Apps are failing to open even when users do not use the Facebook login options included.
It's not clear when the issue will be fixed, but with so many apps affected, it could be addressed shortly. Facebook will likely be able to fix the problem over the air with a server update.
Article Link: Facebook SDK Issue Causing Some iOS Apps to Crash
Yeah, the SDK is all Objective-C. I saw the error in the debugger. Basically it was parsing some JSON, and they were trying to treat a boolean as a dictionary. Was throwing [__NSCFBoolean objectForKeyedSubscript:]: unrecognized selector. So bit of a mix of the loose typing of obj-c and Facebook hacking on something.
It is a mistake we all made at some point. This is what I like about Swift, sometimes it is pedantic but it prevents mistakes like that.
When I look back at my Objective-C code base I see a lot of type checks I added to prevent bugs like that, but every now and then I find some code where I forgot to put it, and maybe the JSON I received has been correct for years so it never crashed.
Thank goodness I removed Facebook SDK from my apps a while ago, so I wasn't affected this time.
Both Google and Facebook are the cancers of todays world.
I wish one day they screw up so badly that every *phone on this planet will crash continuously for
a day or so, only then it would make a difference.
* Include computers too.
Hopefully we can now rip FB out of most apps
Their sign in with... is pretty bad anyway, FB has removed more and more features from it, and kept breaking it - I think the bottom line is, they simply are not very much interested in being a login provider anymore.
By the time they created app specific links it was over. They said it's for privacy but it was more for FB profit and control and protecting their user graph. Which is fine, not hating on FB, just saying their business interests simply do not align with a login-with feature like that.
Login with Apple ID and login with Google is working fine.
[automerge]1588845681[/automerge]
One tap sign in is super convenient, that's why.
I hate the FB spying too, but even as a developer I wasn't 100% aware that there's some facebook code running before my app is running - that's just horrible in every conceivable way. I mean - yes - now that it's obvious, it seems obvious, I just never thought about it before, what you do is you just follow the instructions, you add those libraries, and invoke them as per the developer documentation.
But at least myself, I wasn't losing any sleep over "oh when my app starts, before anything even happens, it calls into facebook's library and God knows what they're doing in there". Which is the case. FB login is basically malware. Never again.
Their sign in with... is pretty bad anyway, FB has removed more and more features from it, and kept breaking it - I think the bottom line is, they simply are not very much interested in being a login provider anymore.
By the time they created app specific links it was over. They said it's for privacy but it was more for FB profit and control and protecting their user graph. Which is fine, not hating on FB, just saying their business interests simply do not align with a login-with feature like that.
Login with Apple ID and login with Google is working fine.
[automerge]1588845681[/automerge]
One tap sign in is super convenient, that's why.
I hate the FB spying too, but even as a developer I wasn't 100% aware that there's some facebook code running before my app is running - that's just horrible in every conceivable way. I mean - yes - now that it's obvious, it seems obvious, I just never thought about it before, what you do is you just follow the instructions, you add those libraries, and invoke them as per the developer documentation.
But at least myself, I wasn't losing any sleep over "oh when my app starts, before anything even happens, it calls into facebook's library and God knows what they're doing in there". Which is the case. FB login is basically malware. Never again.
Nope. Even those of us without Facebook accounts can’t open apps today. Time to 1-star every affected app, because yes, the developers do deserve it.
Easy fix block graph.facebook.com and graph.instagram.com they will not impact you in anyway and disable the SDK. Almost every app has this in it.
[automerge]1588859361[/automerge]
[automerge]1588859361[/automerge]
Almost all of them do according to my PiHole graph.facebook.com is the most blocked domain by over 20K.
It does not taste great, it does not look great and it does not smell great since it is some rotten rubbish...
It spreads like cancer cells.
My High Sierra mac started chain-crashing the iCal app and I have to think it’s related to an old facebook calendar thats stuck in iCloud and can’t be removed via any GUI that I’ve found. I restored the machine from backup last night and saw this story in the morning.
Generally, by crashing. It's just a potential crash the developer explicitly ignored.
