App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

Post by x86_64Ubuntu » Fri, Jul 10, 2020, 1:38 PM UTC

AndrewZM wrote: post #79

speedyapoc wrote: post #40

Earlier quoted context omitted.

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…

This is exactly what happens. Basically a null value is converted into an NSNull object and calling count on it will of course throw an exception... because there is no count method in that class... It makes me wonder what all those engineers at FB are actually doing... ? Every time I tried to integrate or look into the FB SDK for simple functionality it was a total clusterfuck.

Post by anonms-coward » Fri, Jul 10, 2020, 1:40 PM UTC

heavenlyblue wrote: post #115

cerberusss wrote: post #81

Earlier quoted context omitted.

Also, you can't migrate WhatsApp between iPhone and Android. There's a utility called BackupTrans, which follows an extremely convoluted process including a step where they install an old version of WhatsApp. It seemed to work but it trips some wire and WhatsApp put me in an hour-long timeout state, twice. Since I very much depend on WhatsApp, I dare not use it anymore.

You can still download the history as a text file though - I did that.

Post by zrobotics » Fri, Jul 10, 2020, 1:41 PM UTC

levosmetalo wrote: post #150

AtHeartEngineer wrote: post #124

Earlier quoted context omitted.

I've been converting people to signal for years, I've got everyone in my life to switch except for my parents and 2 coworkers.

I gave up after realizing that Signal will not deliver message for a couple of days and that message notification doesn't work. Why wasting personal credit on something that is clearly inferior from the usability point of view. And after it started insisting on creating a PIN each time I start Signal, I finally deleted it from my phone. You can forget about security if you can't get a seamless user experience.

Post by Sephiroth87 » Fri, Jul 10, 2020, 1:43 PM UTC

zentiggr wrote: post #161

zuppy wrote: post #41

Earlier quoted context omitted.

this, combined with a wrong past technical decision that we can not change it instantly. unfortunately it's not as easy to fix mobile bugs as it is on the web, as you have to both pass the approval process and wait for the full rollout to clients. in our case, it's just a wrong decision, we don't use it for tracking. also, if you use facebook login, the terms and conditions force you to use their SDK (which automatic…

> we don't use it for tracking True, you're just facilitating, not profiting. Such a clear and obvious good reason to drop support and walk away.

Post by sfifs » Fri, Jul 10, 2020, 1:44 PM UTC

beagle3 wrote: post #147

wccrawford wrote: post #86

Earlier quoted context omitted.

I'm pretty sure that's the same agreement that every developer has with Google just by writing an android app and using Google APIs. You can store data on Google Drive that isn't accessible from Google Drive and only that app can read or write it.

> I'm pretty sure that's the same agreement that every developer has with Google just by writing an android app and using Google APIs. But why would WhatsApp store it unencrypted on Google Drive, and encrypted (without giving you any access to the key) on your own SD card or local backup? It makes no sense. Except ... Google and Facebook have agreed that WhatsApp stores the database unencrypted, and in return Google…