< How to store continuations to be resumed later | What’s the difference between Sequence, AsyncSequence, and AsyncStream? > |
Updated for Xcode 14.2
This error occurs when you’ve tried to call an async function from a synchronous function, which is not allowed in Swift – asynchronous functions must be able to suspend themselves and their callers, and synchronous functions simply don’t know how to do that.
If your asynchronous work needs to be waited for, you don’t have much of a choice but to mark your current code as also being async
so that you can use await
as normal. However, sometimes this can result in a bit of an “async infection” – you mark one function as being async, which means its caller needs to be async too, as does its caller, and so on, until you’ve turned one error into 50.
In this situation, you can create a dedicated Task
to solve the problem. We’ll be covering this API in more detail later on, but here’s how it would look in your code:
func doAsyncWork() async {
print("Doing async work")
}
func doRegularWork() {
Task {
await doAsyncWork()
}
}
doRegularWork()
Download this as an Xcode project
Tasks like this one are created and run immediately. We aren’t waiting for the task to complete, so we shouldn’t use await
when creating it.
SPONSORED In-app subscriptions are a pain to implement, hard to test, and full of edge cases. RevenueCat makes it straightforward and reliable so you can get back to building your app. Oh, and it's free if your app makes less than $10k/mo.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Link copied to your pasteboard.