blocks|key|3064425|text|如果你使用的是协程-android，你可以使用Dispatchers.Main|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3064426|(gradle依赖项为implementation+"org.jetbrains.kotlinx:kotlinx-coroutines-android:1.0.0")|3064427|network.getRoute(request,
++++++++success+=+{
++++++++++++withContext(Dispatchers.Main)+{
++++++++++++++++//+update+UI+here
++++++++++++}
++++++++},
++++++++fail+=+{
++++++++++++//+handle+the+exception
++++++++})+|code-block|syntax|javascript|3064428|entityMap^0|N|G|0|B|1Z|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

If you're using coroutines-android you can use <code>Dispatchers.Main</code> 
(gradle dependency is <code>implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:1.0.0"</code>)

<pre><code>network.getRoute(request,
 success = {
 withContext(Dispatchers.Main) {
 // update UI here
 }
 },
 fail = {
 // handle the exception
 }) 
</code></pre>

blocks|key|804243|text|要回答您直接提出的问题，您只需在正确的上下文中启动协程：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|804244|val+call+=+ApiClient.getInterface().getRoute(request.getURL())
GlobalScope.launch(Dispatchers.Main)+{
++++try+{
++++++++success?.invoke(call.await())
++++}+catch+(t:+Throwable)+{
++++++++fail?.invoke(t)
++++}
}|code-block|syntax|javascript|804245|然而，这只是冰山一角，因为您的方法使用协程的方式是错误的。它们的主要好处是避免了回调，但您正在重新引入它们。您使用的GlobalScope也侵犯了的最佳实践，因为它不是用于生产的。|offset|length|style|CODE|804246|显然，您已经有了一个异步API，它为您提供了一个可以await的Deferred<RoutesResponse>。使用方法如下：|804247|scope.launch+{
++++val+resp+=+ApiClient.getInterface().getRoute(request.getURL()).await()
++++updateGui(resp)
}|804248|你可能会因为我建议在你必须执行可挂起代码的每个图形用户界面回调中都有一个launch块而苦恼，但这实际上是使用这个特性的推荐方式。它与编写Thread+{+...+my+code+...+}.start()是严格并行的，因为您的launch块的内容将与外部的代码并发运行。|804249|上面的语法假设您有一个实现CoroutineScope的scope变量。例如，它可以是您的Activity|804250|class+MyActivity+:+AppCompatActivity(),+CoroutineScope+by+MainScope+{

++++override+fun+onDestroy()+{
++++++++super.onDestroy()
++++++++cancel()
++++}
}|804251|MainScope委托将默认协程调度程序设置为Dispatchers.Main。这允许您使用普通的launch+{+...+}语法。|804252|entityMap^0|0|0|1M|B|0|Q|5|W|O|0|0|10|6|1X|Y|36|6|0|D|E|S|5|19|8|0|0|0|9|N|G|1D|E|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@$I|13|J|14|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@$I|16|J|17|K|L]|$I|18|J|19|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1B|8|@$I|1C|J|1D|K|L]|$I|1E|J|1F|K|L]|$I|1G|J|1H|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@$I|1J|J|1K|K|L]|$I|1L|J|1M|K|L]|$I|1N|J|1O|K|L]]|9|@]|A|$]]|$1|U|3|V|5|D|7|1P|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1Q|8|@$I|1R|J|1S|K|L]|$I|1T|J|1U|K|L]|$I|1V|J|1W|K|L]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]]|Z|$]]

To answer your immediate question, you must simply launch the coroutine in the correct context:

<pre><code>val call = ApiClient.getInterface().getRoute(request.getURL())
GlobalScope.launch(Dispatchers.Main) {
 try {
 success?.invoke(call.await())
 } catch (t: Throwable) {
 fail?.invoke(t)
 }
}
</code></pre>

However, this would be just the tip of the iceberg because your approach is the wrong way to use coroutines. Their key benefit is avoiding callbacks, but you're re-introducing them. You are also infringing on the <a href="https://medium.com/@elizarov/structured-concurrency-722d765aa952" rel="noreferrer">structured concurrency</a> best practice by using the <code>GlobalScope</code> which is not meant for production use.

Apparently you already have an async API that gives you a <code>Deferred&lt;RoutesResponse&gt;</code> that you can <code>await</code> on. The way to use it is as follows:

<pre><code>scope.launch {
 val resp = ApiClient.getInterface().getRoute(request.getURL()).await()
 updateGui(resp)
}
</code></pre>

You may be distressed by the fact that I'm suggesting to have a <code>launch</code> block in every GUI callback where you must execute suspendable code, but that is actually the recommended way to use this feature. It is in a strict parallel to writing <code>Thread { ... my code ... }.start()</code> because the contents of your <code>launch</code> block will run concurrently to the code outside it.

The above syntax assumes you have a <code>scope</code> variable ready which implements <code>CoroutineScope</code>. For example, it can be your <code>Activity</code>:

<pre><code>class MyActivity : AppCompatActivity(), CoroutineScope by MainScope {

 override fun onDestroy() {
 super.onDestroy()
 cancel()
 }
}
</code></pre>

The <code>MainScope</code> delegate sets the default coroutine dispatcher to <code>Dispatchers.Main</code>. This allows you to use the plain <code>launch { ... }</code> syntax.

blocks|key|2128749|text|private+var+viewModelJob+=+Job()
private+val+uiScope+=+CoroutineScope(Dispatchers.Main+%2B+viewModelJob)

uiScope.launch+{
++++++++++++withContext(Dispatchers.IO)+{
++++++++++++++++//Do+background+tasks...
++++++++++++++++withContext(Dispatchers.Main){
++++++++++++++++++++//Update+UI
++++++++++++++++}
++++++++++++}
++++++++}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2128750|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>private var viewModelJob = Job()
private val uiScope = CoroutineScope(Dispatchers.Main + viewModelJob)

uiScope.launch {
 withContext(Dispatchers.IO) {
 //Do background tasks...
 withContext(Dispatchers.Main){
 //Update UI
 }
 }
 }
</code></pre>

I'm trying to call an API and when my variables are ready, update UI components respectively.

This is my Network singleton who is launching the coroutine:

<pre><code>object MapNetwork {
 fun getRoute(request: RoutesRequest,
 success: ((response: RoutesResponse) -&gt; Unit)?,
 fail: ((throwable: Throwable) -&gt; Unit)? = null) {
 val call = ApiClient.getInterface().getRoute(request.getURL())

 GlobalScope.launch(Dispatchers.Default, CoroutineStart.DEFAULT, null, {

 try {
 success?.invoke(call.await())
 } catch (t: Throwable) {
 fail?.invoke(t)
 }

 })
 }
}
</code></pre>

And this is how I call it:

<pre><code>network.getRoute(request,
 success = {
 // Make Some UI updates
 },
 fail = {
 // handle the exception
 }) 
</code></pre>

And I get the Exception that says can't update UI from any thread other than UI thread:

<pre><code>com.google.maps.api.android.lib6.common.apiexception.c: Not on the main thread
</code></pre>

I already tried <a href="https://medium.com/@macastiblancot/android-coroutines-getting-rid-of-runonuithread-and-callbacks-cleaner-thread-handling-and-more-234c0a9bd8eb" rel="noreferrer">this</a> solution but <code>resume</code> in <code>Continuation&lt;T&gt;</code> class is "deprecated" since Kotlin 1.3

How to update UI in coroutines in Kotlin 1.3

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在尝试调用API，当我的变量准备就绪时，分别更新UI组件。这是我的网络单例，他正在启动协程：object MapNetwork {    fun getRoute(request: RoutesRequest,                 success: ((response: RoutesResponse)...

问如何在Kotlin 1.3中更新协程中的UI
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Kotlin 1.3中更新协程中的UIEN