6 ms·

Unless your app is designed for browsing Facebook, there's no reason that anything on Facebook's servers should affect if your app works. Many of the apps cras

Unless your app is designed for browsing Facebook, there's no reason that anything on Facebook's servers should affect if your app works. Many of the apps crashing are using Facebook for a portion of their app, such as one login option. Letting that take down the whole app is insufficiently defensive coding, whether in the app, sdk, or glue between them.

corndoge 6y ago
How do you defend against abort() in library code?
- Nextgrid 6y ago
  Don't include libraries which contain such code?
  - saagarjha 6y ago
    No abort here, the crash is coming from the runtime, which you’re not opting out of if you want your app to work.
    - slipheen 6y ago
      Then we can agree the FB sdk should have been better written to avoid this, right?
      - corndoge 6y ago
        Obviously, and now we agree!
frenchy 6y ago
> there's no reason that anything on Facebook's servers should affect if your app works. Absolutely, but the problem is that in order for you to use these features, you're supposed to use the official Facebook SDK. The additional problem, is that Facebook has no interest in defensive coding, because if you're not interacting with Facebook in an app, there's no benefit to Facebook for you using that app at all.