title: Android: FacebookAuthorizationException appears sometimes
body: <p>Since couple of weeks this exception appears sometimes on my App:</p>
  <pre><code>Non-fatal Exception: com.facebook.FacebookAuthorizationException: CONNECTION_FAILURE: TigonError(2): TigonLigerErrorDomain(2) AsyncSocketException: connect failed (immediately), type = Socket not open, errno = 101 (Network is unreachable)
         at com.facebook.login.LoginManager.onActivityResult(LoginManager.java:218)
         at com.facebook.login.LoginManager$1.onActivityResult(LoginManager.java:173)
         at com.facebook.internal.CallbackManagerImpl.onActivityResult(CallbackManagerImpl.java:95)
         at com.myapp.util.connect.FacebookConnect.onActivityResult(FacebookConnect.java:338)
  </code></pre>
  <p>Facebook SDK: 4.27.0
  Android version's impacted: 4.4.2 and 7 (Crashlytics informations)</p>
  <p>Have you got some ideas guys about this exception?</p>
  <p>Thank you very much</p>
  <p><em><strong>UPDATE</strong></em></p>
  <p>I wrote a ticket on Facebook support, and after several messages, the last is:</p>
  <blockquote>
  <p>Hi Anthony, thanks for the additional details. Looking at the data for your app,
  there don't seem to be any failed API calls logged for your app. This indicates
  that the login attempts failed before they reached our servers, and confirms
  that this was indeed due to network errors.</p>
  <p>I agree that it's not the ideal experience for users to have to retry their
  login attempt, but in the case of network-related issues like this, this is the
  best approach. I would recommend prompting the user to check their device
  connectivity and initialize the login flow again.</p>
  <p>From debugging this, it's unlikely that this is due to compatibility issues with
  Retrofit, though I can't rule it out with certainty. It's more likely that the
  affected users simply experienced a temporary drop in connectivity.</p>
  <p>I'll mark this as closed since there doesn't seem to be a bug within the
  Facebook SDK, but if you're able to get any information that would indicate
  otherwise (for example, a way to consistently reproduce the error on a device
  that has full internet connectivity), please let me know and I'll be glad to
  help look into this again.</p>
  </blockquote>