title: Android AccountManager.getAuthToken ignoring callback after LoginActivity
body: <p>As stated in the question title, the AccountManager will start the LoginActivity from a call to <code>getAuthToken</code>, but then it doesn't enter the callback. </p>
  
  <p>What's weird is that it does go to the callback if it has any way of getting an auth token that doesn't require starting the activity (like a cached token or my refresh token mechanism). It's only when returning from the LoginActivity that it doesn't work.</p>
  
  <p>So I'm thinking I'm probably not putting everything in the result bundle that Android is expecting, but what <em>does</em> it expect? The docs are pretty thin on that.</p>
  
  <p>Here's the relevant part of the login activity:</p>
  
  <pre><code>Bundle result = new Bundle();
  if (tokens.hasAccess()) {
      result.putString(AccountManager.KEY_ACCOUNT_NAME, account.name);
      result.putString(AccountManager.KEY_ACCOUNT_TYPE, account.type);
      result.putString(AccountManager.KEY_AUTHTOKEN, tokens.access);
  }
  setAccountAuthenticatorResult(result);
  setResult(Activity.RESULT_OK);
  finish();
  </code></pre>
  
  <h3>Update</h3>
  
  <p>My problem is the same as <a href="https://stackoverflow.com/questions/14623255/android-authentication-callback-isnt-called">in this SO question</a>, right down to the delayed invocation of the callback when I relaunch. But his solution doesn't work for me, I already had the <code>putExtra(KEY_ACCOUNT_AUTHENTICATOR_RESPONSE, response)</code> in my authenticator.</p>