networkonmainthreadexception kotlin
networkonmainthreadexception retrofit
android.os.networkonmainthreadexception kotlin
android.os.networkonmainthreadexception httpurlconnection
android.os.networkonmainthreadexception okhttp
android.os.networkonmainthreadexception jsoup
android.os.networkonmainthreadexception bitmap
android networkonmainthreadexception error

I just found out about NetworkOnMainThreadException at official docs

and was wondering if the emulator is throwing this. I have been testing my app quite a bit and as far as I know all networking is off the main thread (using Roboguice RoboAsyncTask) but you never know if one has not escaped.

I am also using StrictMode and have not seen anything.

  1. Is my code just clean or is this not thrown on the emulator?

  2. How are we supposed to prepare for this happening in production?

  3. What about a grace period or something? Or is that elapsed now ;-) ??

How to fix 'android.os.NetworkOnMainThreadException'?, This example demonstrates how do I fix the android.os.​NetworkOnMainThreadException. Step 1 − Create a new project in Android Studio,  NetworkOnMainThreadException() NetworkOnMainThreadException() NetworkOnMainThreadException(IntPtr, JniHandleOwnership) NetworkOnMainThreadException(IntPtr, JniHandleOwnership) A constructor used when creating managed representations of JNI objects; called by the runtime.

I have tested this and it does in fact happen on the emulator as well. Better make sure you test your app at least on the emulator if you plan to get it onto the 3.0 tablets and beyond.

How to fix android.os.NetworkOnMainThreadException?, when an Android device running 3.0 or above detects a network access on the UI thread, a NetworkOnMainThreadException will be thrown:  Overview; Android Platform; Android Support Library; AndroidX; AndroidX Test; AndroidX Constraint Layout; Architecture Components; Jetpack Compose UI; Android Automotive Library

NetworkOnMainThreadException occurs when some networking operations are performed inside main method; I mean Oncreate(). You can use AsyncTask for resolving this issue. or you can use

StrictMode.ThreadPolicy mypolicy = new StrictMode.ThreadPolicy.Builder().permitAll().build();

inside onCreate() method.

How to resolve android.os.NetworkOnMainThreadException , How to avoid android os NetworkOnMainThreadException Take your app to the top keyword Duration: 3:40 Posted: Sep 24, 2014 6.In main activity class ( I have declared things; one inner class extends AsyncTask and another one is function.Asynctask will call the downloadData function of Utility class in doInBackground override method it’s the separate thread which will not affect to the UI thread. while function directly call the downloadData function from the UI thread so this will throw exception.

If you are running on 3.0, i can't help; Because Strict mode is on by default in it; But its above tat, then this might help

StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder().permitAll().build();

Include this before your HTTP connection creation; Then it works

How to avoid android os NetworkOnMainThreadException, App (Android SDK 23 ) is crashed when because of android.os.​NetworkOnMainThreadException ( looks like from okhttp library) when callin This example demonstrates how do I fix the android.os.NetworkOnMainThreadException. Step 1 − Create a new project in Android Studio, go to File ⇒ New Project and fill all required details to create a new project. Step 2 − Add the following code to res/layout/activity_main.xml.

From Honeycomb SDK (3), Google will no longer allow network requests (HTTP, Socket) and other related operations directly in the Main Thread class, in fact, should not do direct network operation in the UI thread, blocking UI, user experience is bad! Even if Google is not prohibited, under normal circumstances, we will not do it ~! So, that is, in the Honeycomb SDK (3) version, you can also continue to do so in Main Thread, more than 3, it will not work.

1.use Handler

The more time-consuming operations associated with network are placed into a child thread and then communicated with the main thread using the Handler messaging mechanism

public static final String TAG = "NetWorkException";

public void onCreate(Bundle savedInstanceState) {
    // Opens a child thread, performs network operations, waits for a return result, and uses handler to notify UI
    new Thread(networkTask).start();

Handler handler = new Handler() {
    public void handleMessage(Message msg) {
        // get data from msg and notify UI
        Bundle data = msg.getData();
        String val = data.getString("data");
        Log.i(TAG, "the result-->" + val);

 * net work task
Runnable networkTask = new Runnable() {

    public void run() {
        // do here, the HTTP request. network requests related operations
        Message msg = new Message();
        Bundle data = new Bundle();
        data.putString("data", "request");

2.use AsyncTask

public static final String TAG = "NetWorkException";
private ImageView mImageView;

public void onCreate(Bundle savedInstanceState) {
    mImageView = findViewById(;
    new DownImage(mImageView).execute();

class DownImage extends AsyncTask<String, Integer, Bitmap> {

    private ImageView imageView;

    public DownImage(ImageView imageView) {
        this.imageView = imageView;

    protected Bitmap doInBackground(String... params) {
        String url = params[0];
        Bitmap bitmap = null;
        try {
            //load image from internet , http request here
            InputStream is = new URL(url).openStream();
            bitmap = BitmapFactory.decodeStream(is);
        } catch (Exception e) {
        return bitmap;

    protected void onPostExecute(Bitmap result) {
        // nodify UI here

3.use StrictMode

if (android.os.Build.VERSION.SDK_INT > 9) {
    StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder().permitAll().build();

android.os.NetworkOnMainThreadException crashed Android App , NetworkOnMainThreadException was introduced with Android 3.0. In an effort by Google to ensure apps stay responsive, NetworkOnMainThreadException is  android.os.NetworkOnMainThreadException: Class Overview. The exception that is thrown when an application attempts to perform a networking operation on its main thread.

How Do I Fix NetworkOnMainThreadException?, How to fix android.os.NetworkOnMainThreadException ? - Error while running an Android project for RssReader. For seasoned android developer, android.os.NetworkOnMainThreadException is something they are use to and they can spot where it wil happen but this is a different case for beginners android developers The main cause of android.os.NetworkOnMainThreadException is when you try to make a network call in UI Thread or time taken processing.

How to fix android.os.NetworkOnMainThreadException ?, NetworkOnMainThreadException and how to avoid it. From the Android site you can read: NetworkOnMainThreadException. The exception that  NetworkOnMainThreadException is a pretty popular exception among those new to android development. This exception is mainly thrown whenever an application attempts to make a networking operation (like an API call or Http request) on its main thread.

NetworkOnMainThreadException Class (Android.OS), If you check the exception call stack carefully you should find that it is actually the constructor for InetSocketAddress that is throwing, because it tries to resolve the host address, which is obviously a network operation.

  • This was introduced in Android 3.0. I got it when i was doing a network operation on the UI thread, as the documentation states. I moved and run the operation on a separate thread and it was gone.
  • You get it in the emulator too or just with a device? Without StrictMode enabled?
  • I got it on the emulator without running in StrictMode.
  • It should not be hard to intentionally cause this if you want to be sure that it's going to result in an error message.
  • @Samuh may i ask which version of android emulator u were using when u get NetworkOnMainThreadException? cause I could not reproduce this erro on the emulator at all. Thanks!
  • Using Handler doesn't necessarily solve the problem. The default behaviour of Handler also executes on the main (UI) thread.
  • The docs say this: "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. See the document Designing for Responsiveness."
  • Read my blog post on the NetworkOnMainThreadException for more information. It explains why this occurs on Android 3.0 and above.
  • This is wrong. The exception is thrown when performing Network I/O on the main Thread. This can happen in any method, not just in onCreate().
  • old answer, but please be assured: It is the wrong way to do! Do never ever any network stuff on the UI thread. A kitten will die for every millisecond of delay you cause with that...