Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

github.com

Post reply on HN
Print view View original

31–40 of 446 posts

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#31

Post by cesarb »

lathiat wrote: post #3

That’s twice in as many months. They may need some better QA here although to be fair it does seem mostly people with an older SDK version based on the comments. But still. I guess they need to cotton onto whatever server side change happened and roll it back. At least this time you can disable the SDK (at least one app developer has a kill switch for the SDK) unlike the last issue that happened during code initialis…

> I guess they need to cotton onto whatever server side change happened and roll it back.

"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable." -- Leslie Lamport, 1987 (https://lamport.azurewebsites.net/pubs/distributed-system.tx...)

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#34

Post by Nextgrid »

zuppy wrote: post #9
0xy wrote: post #4

It's fantastic news in that it forces the companies who will undoubtedly lose millions of dollars in revenue from this to evaluate their inclusion of the tracking spyware in their apps.

that's not the only purpose of the SDK, we're using it for social login (login with Facebook).

You can implement OAuth entirely server-side without any client support beyond displaying a web view. No need to include spyware and the approach is reusable for any OAuth provider.

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#36

Post by creaghpatr »

yreg wrote: post #20

Workaround for users: Enable airplane mode and disable WiFi, or block facebook domains Workaround for developers: Go to Facebook Developer page > Analytics and disable automatic Events.[0] Apparently this doesn't solve the issue for everyone. Issue in Facebook's tracker: https://developers.facebook.com/status/issues/17391881029111... [0] https://github.com/facebook/facebook-ios-sdk/issues/1427#iss...

Thank you now I can listen to cached Spotify playlists!

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#38

Post by lowwave »

krtkush wrote: post #23

Given how protective Apple is about the experience of apps on the App Store and this happening the second time, I'm surprised they have not come up with a way to prevent this from happening. Also, a monolithic SDK should not exist in this day and age.

Libs over SDK!

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#39

Post by yreg »

Nextgrid wrote: post #7
rock_artist wrote: post #6

Argh. Waze, Viber, Gett. It started yesterday on my wife’s phone and today I see it across more devices.

It would be nice to have a complete list of apps that include this spyware so we can avoid them.

Or you can block the DNS to be sure.

    facebook.com
    fbcdn.com
    fbcdn.net
    fbsbx.com
    fb.com
    instagram.com

Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

#40

Post by speedyapoc »

andersco wrote: post #22

How is it that a third party SDK is consistently causing apps to completely crash rather than, for example, displaying an error message? Is this a failure that cannot be caught? Sorry, just trying to understand. The dependency relationship just seems to be extreme.

My guess in this particular instance is that it seems like the Facebook SDK is fetching some sort of remote serialized configuration, calling “count” on what it expects to be an array, and instead is calling it on NSNull (an object representing “null”) which is throwing an exception.

There are some intricacies on iOS surrounding null values and serialization, and as a developer it is important to understand that you may encounter NSNull. As a standard practice in my company, we type check every remote value before calling anything on it. Seems like that would have prevented this issue.

Post reply on HN