App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m

Post by whatshisface » Sat, Jul 11, 2020, 12:23 AM UTC

Barrin92 wrote: post #381

BobbyJo wrote: post #375

Earlier quoted context omitted.

Have you ever worked at a large company? Really the only thing that groups the whole thing together is the legal entity. Different teams within the same company are essentially different companies once you reach a certain scale. I see no reason to disparage the good work one group does, because of a different group of people they've never met before, for no other reason than they share a CEO. A CEO that neither group…

this is a pretty simple way to absolve people of responsibility. Just because an institution has compartmentalized tasks, so that every single individual team appears to do nothing wrong, doesn't mean this actually absolves individuals, because following that logic obviously nobody would ever be responsible for anything. It's like Kierkegaard's example of the mob who collectively intimidates but every member argues t…

Post by saagarjha » Sat, Jul 11, 2020, 1:04 AM UTC

babesh wrote: post #391

saagarjha wrote: post #304

Earlier quoted context omitted.

> The crash happened because of a server side change that triggered roughly the Objective-C equivalent of a null pointer exception. > Objective-C is an old unsafe language. This was a safe crash, not an unsafe one. Swift can and would crash the same way.

You can’t safely call a method on a nil value in Swift. You need to explicitly force that in your code with an exclamation point to assume that the variable is not nil. Looks like the server passed empty value in JSON which got converted to NSNull in Objective-C. It's a common mistake to assume null is returned instead of NSNull. The Swift equivalent of the JSON library should return nil which you then need to explic…

  $ swift
  Welcome to Apple Swift version 5.3 (swiftlang-1200.0.16.15 clang-1200.0.22.41).
  Type :help for assistance.
    1> import Foundation
    2> // IIRC this used to throw an exception.
    3> // Now a respondsToSelector: check is silently inserted and we get a surprise nil.
    4> (Int?.none as AnyObject).count + "call Swift's bluff".count
  Fatal error: Unexpectedly found nil while unwrapping an Optional value: file repl.swift, line 4
  2020-07-10 18:03:43.815959-0700 repl_swift[73029:930570] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file repl.swift, line 4
  Execution interrupted. Enter code to recover and continue.
  Enter LLDB commands to investigate (type :help for assistance.)

Post by babesh » Sat, Jul 11, 2020, 1:11 AM UTC

saagarjha wrote: post #394

babesh wrote: post #391

Earlier quoted context omitted.

You can’t safely call a method on a nil value in Swift. You need to explicitly force that in your code with an exclamation point to assume that the variable is not nil. Looks like the server passed empty value in JSON which got converted to NSNull in Objective-C. It's a common mistake to assume null is returned instead of NSNull. The Swift equivalent of the JSON library should return nil which you then need to explic…

$ swift Welcome to Apple Swift version 5.3 (swiftlang-1200.0.16.15 clang-1200.0.22.41). Type :help for assistance. 1> import Foundation 2> // IIRC this used to throw an exception. 3> // Now a respondsToSelector: check is silently inserted and we get a surprise nil. 4> (Int?.none as AnyObject).count + "call Swift's bluff".count Fatal error: Unexpectedly found nil while unwrapping an Optional value: file repl.swift, li…

Post by zucker42 » Sat, Jul 11, 2020, 1:29 AM UTC

DyslexicAtheist wrote: post #372

beagle3 wrote: post #64

Waze, a google owned app for the past 4 years, crashes because of the FB app. WhatsApp, a Facebook owned app, will not give you read access to your own chat database - it’s encrypted. But they have an arrangement with Google where it’s will back up unencrypted to your Google account (though, Google won’t let you retrieve it ... only the WhatsApp app can) Everything about this duopoly, their cooperation and lack of co…

with all the daily (justified) outrage against FB/Google I struggle to understand why the community here is happy to applaud these companies for its innovation on specific projects or the work of specific engineers, ... whether it's project-zero or some fb framework we seem to be OK with praising their employees while at the same time hating how they use that innovation. some serious cognitive dissonace is going on -…

Post by ghayes » Sat, Jul 11, 2020, 1:42 AM UTC

zucker42 wrote: post #398

DyslexicAtheist wrote: post #372

Earlier quoted context omitted.

with all the daily (justified) outrage against FB/Google I struggle to understand why the community here is happy to applaud these companies for its innovation on specific projects or the work of specific engineers, ... whether it's project-zero or some fb framework we seem to be OK with praising their employees while at the same time hating how they use that innovation. some serious cognitive dissonace is going on -…

Maybe the people doing the lauding are different from those doing the criticizing? I'm inherently suspicious of statements which treat a discussion forum as monolithic.