title: Android HTTP Client Problems
body: <p>I'm hoping someone can find this problem.  I had an app that was fully working in server communications.  Unfortunately, I somehow lost my Eclipse workspace when moving to the Windows 8 CP.  I still had the .apk, and using Dex2jar and jd-gui, I was able to salvage a lot of code.  I've got it all back into working condition, but this.  I'm attempting to send a URL to a server, and get back a string response.  Here's the code:</p>
  
  <pre><code>import org.apache.http.client.HttpClient;
  import org.apache.http.client.ResponseHandler;
  import org.apache.http.client.methods.HttpGet;
  import org.apache.http.impl.client.BasicResponseHandler;
  import org.apache.http.impl.client.DefaultHttpClient;
  
  public class login extends Activity{
  
  &lt;code&gt;
  
  public void pushLogin(View paramView){
  
    try{
      HttpClient client = new DefaultHttpClient();
      HttpGet request = new HttpGet(loginFinal);
      ResponseHandler&lt;String&gt; responseHandler = new BasicResponseHandler();
      errorTextView.setText(loginFinal);
  
      //code gets here
      String response = client.execute(request, responseHandler);
      //does not get here
      errorTextView.setText(response);
    }
  </code></pre>
  
  <p>My TextView always contains the string loginFinal, I cannot get it to display the response.  To check this, I moved the <code>errorTextView.setText(loginFinal);</code> to the line after attempting to get the String response.  It didn't run at that point either.  I'm tearing my hair out, and I'm sure it's something simple.  I've got the internet permission, I even found my original code for this portion of the app on this site as I posted it asking a separate question.  This code is, as far as I can tell, identical.  The only thing I can think of that changed is I moved my build target from Froyo to Honeycomb, as I decided I want to focus on tablets.</p>
  
  <p>The best part is that LogCat does absolutely nothing when I press the button, triggering pushLogin.  It doesn't seem to be triggering the <code>client.execute(request, responseHandler)</code> at all.</p>