App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

Post by anonms-coward » Fri, Jul 10, 2020, 3:52 PM UTC

beagle3 wrote: post #297

anonms-coward wrote: post #287

Earlier quoted context omitted.

The number of people who use whatsapp is an order of magnitude or more than the number of people who consciously use Google drive, as in people who know google drive exists. Even the people who have google drive, most of them have much less intimate data on it than in their private messages on WhatsApp. If we are to take the position that all users are tech literate and should be fully in charge of how their data is…

And you are still avoiding the equivalence that everything you describe is already happening with sms messages at least, and generally much more. None of your arguments carry any weight especially since they don’t explain why it’s ok for data to be unencrypted on your google drive in the first place.

Post by valuearb » Fri, Jul 10, 2020, 3:59 PM UTC

XCSme wrote: post #267

monocularvision wrote: post #256

Earlier quoted context omitted.

This is a native SDK that is crashing the process. There is nothing an app developer can responsibly do to prevent or recover from this crash. Other than remove the SDK, of course.

So there is no way to try {} catch {} it, right?

Post by saagarjha » Fri, Jul 10, 2020, 4:01 PM UTC

hyko wrote: post #298

monocularvision wrote: post #256

Earlier quoted context omitted.

This is a native SDK that is crashing the process. There is nothing an app developer can responsibly do to prevent or recover from this crash. Other than remove the SDK, of course.

Yes there is: a remote kill switch that prevents the third party SDK from loading. That puts you back in control of the software you’re shipping. Fool me once, and all that.

Post by saagarjha » Fri, Jul 10, 2020, 4:02 PM UTC

XCSme wrote: post #267

monocularvision wrote: post #256

Earlier quoted context omitted.

This is a native SDK that is crashing the process. There is nothing an app developer can responsibly do to prevent or recover from this crash. Other than remove the SDK, of course.

So there is no way to try {} catch {} it, right?

Post by saagarjha » Fri, Jul 10, 2020, 4:04 PM UTC

blantonl wrote: post #277

emerongi wrote: post #273

Earlier quoted context omitted.

Maybe lessons will be learned, maybe not. The industry seems to have very low standards. Let's let these mistakes happen over and over and let's just patch them as we go. No long-term thinking. Someone should collect all these horrible incidents and start a university course on just plainly what NOT to do.

Some of the very brightest software engineers in the world work at Facebook. As much as I would love to rip on Facebook, I also understand that integrated software development is hard, and I guarantee you that Facebook is "doing it better" than most. Don't sit in an ivory tower and throw stones in glass houses. Can you guarantee that your own SDLC house is in order? Because it might be, right up until a sneaky edge c…