Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via Stack Overflow by Razgriz

    Happens when you make a network call on the main UI thread of the Android application which results in a UI freeze until the network call is complete and the response is received. Instead, execute the network calls in the background: use AsyncTask.

  2. ,

    An alternative for just getting rid of the Exception is use StrictMode.ThreadPolicy to force execute on main thread.

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

Solutions on the web

via GitHub by tuhin10
, 2 years ago
This exception has no message.
via Stack Overflow by user782104
, 2 years ago
via Stack Overflow by TheNerdFromYesterday
, 2 years ago
This exception has no message.
via Stack Overflow by Knossos
, 1 year ago
via GitHub by roms
, 2 years ago
This exception has no message.
android.os.NetworkOnMainThreadException: 	at android.os.StrictMode$AndroidBlockGuardPolicy.onNetwork(	at	at	at	at$000(	at$	at okio.Okio$	at okio.AsyncTimeout$	at	at okhttp3.internal.http.Http1xStream$	at okhttp3.internal.Util.skipAll(	at okhttp3.internal.Util.discard(	at okhttp3.internal.http.Http1xStream$FixedLengthSource.close(	at okio.RealBufferedSource.close(	at okio.ForwardingSource.close(	at okio.RealBufferedSource.close(	at okio.RealBufferedSource$1.close(	at com.testapp.apkinstall.MainActivity.writeResponseBodyToDisk(	at com.testapp.apkinstall.MainActivity.access$000(	at com.testapp.apkinstall.MainActivity$1$1.onResponse(	at retrofit2.ExecutorCallAdapterFactory$ExecutorCallbackCall$1$	at android.os.Handler.handleCallback(	at android.os.Handler.dispatchMessage(	at android.os.Looper.loop(	at	at java.lang.reflect.Method.invoke(Native Method)	at java.lang.reflect.Method.invoke(	at$	at