App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

Post by charlesdm » Fri, Jul 10, 2020, 11:53 AM UTC

pi-err wrote: post #27

I use a non-Facebook login on Spotify and the app crashes right there. How is this even possible, even less acceptable from Spotify point of view?

Post by layoutIfNeeded » Fri, Jul 10, 2020, 11:56 AM UTC

harryf wrote: post #53

yreg wrote: post #30

Earlier quoted context omitted.

>To stop crashes from the Facebook SDK, some devs tried commenting out any code that calls Facebook. Nothing worked. >It turns out that by just including the SDK with your app, Facebook runs hidden code on launch. (FBSDKApplicationDelegate.m) [0] https://twitter.com/sandofsky/status/1258288056399847425

... so if the app including the SDK has permission to access location data, the SDK could be passing that location data to Facebook?

Post by akmarinov » Fri, Jul 10, 2020, 11:59 AM UTC

speedyapoc wrote: post #40

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…

Post by jgeada » Fri, Jul 10, 2020, 12:00 PM UTC

Post by KuiN » Fri, Jul 10, 2020, 12:02 PM UTC

pi-err wrote: post #27

I use a non-Facebook login on Spotify and the app crashes right there. How is this even possible, even less acceptable from Spotify point of view?