Databases
StackOverflow2013
Postsdbo
POAsyncTask doInBackground odd behavior
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAsyncTask doInBackground odd behavior
    primarykey
    data
    text
    <p><strong>ORIGINAL</strong> I have an AsyncTask which performs network requests, and it works fine. The environment I'm testing in is against Eclipse with the USB wired to the device to log information to LogCat. When detaching the USB wire from the device and re-attaching the wire back to the device I can see the LogCat session resume, afterwards, I exit the application and re-enter the application, and when the AsyncTask runs again, the network request fails.</p> <p><strong>Has anyone ever experienced odd behavior when performing network calls in between detaching and re-attaching the USB wire to the android device?</strong> The flow of the application appears normal as I've logged about every sequence up to the point &amp; through the point of the AsyncTask executing. <strong>The application is functional with the network calls when the USB is wired at all times.</strong> Might the LogCat have anything to do with this?</p> <p>Thanks.</p> <p><strong>EDIT</strong> The network request does not actually fail, the server just responds with an error code. But before I could start blaming the server, I performed multiple hits successfully through the browser to the same URL. I've only involved the USB into the picture, because the odd behavior only occurs when the USB is detached from the device and re-attached.</p> <p><strong>UPDATE</strong> After doing further research, I've finally diagnosed the issue but have no idea why it's so. When the debugger is attached to the process responsible for handling the network calls (background threads), the application works as expected. However, when the debugger is disconnected from the process, the network calls brings back the server error results.</p> <p><strong>How is the debugger influencing the network calls?</strong></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRyan
    1. USRyan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYou are saying that you exit the application and come back in. That sounds more likely to be the culprit of why things are failing. Have you debugged this at all ?
      singulars
      1. POAsyncTask doInBackground odd behavior
      1. USdymmeh
    2. COHow do you know the request fails?
      singulars
      1. POAsyncTask doInBackground odd behavior
      1. UStyczj
    3. COI have edited the post, please see edit.
      singulars
      1. POAsyncTask doInBackground odd behavior
      1. USRyan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload