From the official Handler docs Handler There are two main uses for a Handler: (1) To schedule messages and runnables to be executed as some point in the future. (2) To enqueue an action to be performed on a different thread than your own. In short, Handler is used to manage different Runnables. runOnUiThread It … Read more
For details on the differences between the two types of queue, see Lion’s answer. Both approaches will work. However, NSOperation is mostly needed when more advanced scheduling (including dependencies, canceling, etc.) is required. So in this case, a simple DispatchQueue.main.async { /* do work */ } will be just fine. That would be equivalent to … Read more
To answer your immediate question, you must simply launch the coroutine in the correct context: val call = ApiClient.getInterface().getRoute(request.getURL()) GlobalScope.launch(Dispatchers.Main) { try { success?.invoke(call.await()) } catch (t: Throwable) { fail?.invoke(t) } } However, this would be just the tip of the iceberg because your approach is the wrong way to use coroutines. Their key benefit … Read more
The UIThread is the main thread of execution for your application. This is where most of your application code is run. All of your application components (Activities, Services, ContentProviders, BroadcastReceivers) are created in this thread, and any system calls to those components are performed in this thread. For instance, let’s say your application is a … Read more
Below is corrected Snippet of runThread Function. private void runThread() { new Thread() { public void run() { while (i++ < 1000) { try { runOnUiThread(new Runnable() { @Override public void run() { btn.setText(“#” + i); } }); Thread.sleep(300); } catch (InterruptedException e) { e.printStackTrace(); } } } }.start(); }
You need to call Toast.makeText(…) from the UI thread: activity.runOnUiThread(new Runnable() { public void run() { Toast.makeText(activity, “Hello”, Toast.LENGTH_SHORT).show(); } }); This is copy-pasted from another (duplicate) SO answer.