I tried multiple HTTP classes (HttpURLConnection
, HTTPClient
and others) but they don\'t work in emulator. Then I decided to test that on my phone
You disable the strict mode using following code:
if (android.os.Build.VERSION.SDK_INT > 9) {
StrictMode.ThreadPolicy policy =
new StrictMode.ThreadPolicy.Builder().permitAll().build();
StrictMode.setThreadPolicy(policy);
}
This is not recommended: use the AsyncTask
interface.
Link of AsyncTask
Link of another reference
If you look at this Android documentation, it explains
NetworkOnMainThreadException:
The exception that is thrown when an application attempts to perform a networking operation on its main thread.
This is only thrown for applications targeting the Honeycomb SDK or higher. Applications targeting earlier SDK versions are allowed to do networking on their main event loop threads, but it's heavily discouraged.
So, depending on OS version, there may be enforcement (exception throwing) of the policy that you not make network requests on the UI thread. This could explain why your code works on a device, and not on an emulator (if they have different Android versions).
You could change the ThreadPolicy
. But as an alternative, I'd suggest you look again at the statement in the Android docs. They heavily discourage performing network operations on the main thread, and I'd certainly agree with them.
So, rather than changing the policy to make it legal, you might consider changing your code, so that your getResponse()
method is not called on the UI thread.
Typically, you would use AsyncTask to do the work in the background.
This happens because you try to perform network activity on the main thread.
I had the same issue, It worked for a while, then after a few weeks of developing, it stopped working.
The solution I found was to add these lines to the
onCreate()
Method:
StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder().permitAll().build();
StrictMode.setThreadPolicy(policy);
Hope this works for you too
EDIT
Due to increasing number of upvotes, I wish to add something.
This will remove the NetworkingOnMainThreadException
, HOWEVER, it is by far not a recommended way.
This exception is there for a reason. Network activity can take time, performing networking on the main thread, which is the same thread that responsible for updating the UI, would freeze the thread until the networking is done (this is what happens on every thread, but when it's performed on a dedicated thread, it's ok). In Android, if the UI-thread isn't active for 5 seconds, it will show the Application is not responsive, Do you want to close it?
dialog.
This is what the exception has come to prevent. Setting the policy, like I suggested, while removes the exception, is the wrong way of doing things.
Any networking actions should be done on a separate thread, either by using AsyncTask
or by creating new Thread
manually. AsyncTask
are a very easy and straight-forward way of implementing this, and this is what I recommend.
Please take this edit into consideration when using my answer.
Cheers