At a high level, yes - the logout won't continue until the server call is complete. However, since we have a timeout set for these calls and we don't check the status code of the response, even if it fails, the logout will continue. We have to use an AsyncTask, because network operations have to be in the background thread. I decided to continue the logout after this call just so we don't run into race conditions. For example, if the logout continues in parallel, we may end up with a situation where we don't have a valid RestClient to make the revocation call.