Swift 5.5: Async Await Operations (Xcode 13, iOS 15, 2022) - iOS for Beginners

In this video we will learn to use the new async await attributed to perform async operations in Swift. Newly available as of 2021 and Swift 5.5, this new style greatly improves upon closures, callbacks, and other concurrent patterns in Swift & iOS. We'll be working in Xcode 13 and Swift 5.5
💻 Source Code: / iosacademy
🎥 Subscribe for more: ua-cam.com/users/iOSAcademy?su...
😎 Like my teaching style? Check out some of my most popular courses! courses.iosacademy.io
#swift #asyncawait #wwdc2021
** Like my teaching style? Check out some of my most popular courses!
courses.iosacademy.io
Join this channel to get access to perks, code, groups, and more:
Building Instagram: courses.iosacademy.io/p/build...
Building TikTok: / @iosacademy
SwiftUI for Beginners: ios-academy.teachable.com/p/s...
Join the iOS Academy Community: iosacademy.io/
** Get Skillshare free for 2 Months and learn iOS
www.skillshare.com/r/user/afraz
** Manage all your investments from app earnings on Betterment!
bit.ly/3eBwlI9
** Grow your own UA-cam tech channel with TubeBuddy:
www.tubebuddy.com/iosacademy

[@flamboulder]

These videos are absolutely outstanding summaries thank you 🙏

[@iOSAcademy]

Thanks

[@prithvi_acoustic]

Thank you for the great explanation

[@MrLinusunil]

Really good video, thanks for sharing that. It was concise and easy to understand.

[@iOSAcademy]

Thanks

[@DhruvilPatel]

Simple and clear, thanks mate!

[@iOSAcademy]

Youre welcome

[@smael1989]

Nice, looking forward to some practice about it

[@iOSAcademy]

Nice

[@difanaufalpratama8765]

Man that so fast, it doesn't take a week and you already make tutorial for new features. Keep going bro!

[@iOSAcademy]

Thanks, will do!

[@glennadams7047]

Nice. I think a whole series of tutorials on this is needed, with simple to complex use cases. I would buy the course if you made one :)

[@iOSAcademy]

Coming soon!

[@glennadams7047]

@@iOSAcademy And include all the nested network calls . like populating a table view with users, their photos, etc all separate calls, proper error handling , etc. all the pain-in-the-ass stuff. Just my $.02. regards and keep up the great work

[@jineshdoshi]

@@iOSAcademy any ETA on this?

[@davidandreasson1434]

Great! simply great, thanks!!

[@iOSAcademy]

You’re welcome

[@cinquain0]

Beautiful video. Bravo!

[@iOSAcademy]

Thanks

[@jerseycafe9099]

good job! thanks mate!

[@iOSAcademy]

Youre welcome

[@janarthanank877]

Easy to understand 👏🏻

[@iOSAcademy]

Thanks

[@fermatslasttheorem6298]

Great video. I'm a senior iOS engineer but trying to catch up on some APIs I've been lazy to learn.

[@iOSAcademy]

Nice!

[@rahulchhetri1869]

same

[@karlostj4683]

Some imminent deprecation on the "async { ... }" call. Need to change it (going forward) to "Task { ... } "

[@iOSAcademy]

Yep

[@franciscoarciganolasco6027]

can be use Task instead of async for concurrent or parallel proccesing?

[@alley8481]

Async await it's pretty cool and very simple ❤️. Thank you for u tutorial sir. Please, if is possible, make a tutorial about repository sir. 😁

[@iOSAcademy]

Sure I will

[@aidenzaw260]

You saved my life.

[@TheBooban]

The syntax is much better, it makes sense. completion handlers didn't make sense as they are part of the function parameters but when you call them, the closure is outside the params ().

[@fermatslasttheorem6298]

Well, no they don't have to be at all. You can certainly put a closure inside the function parenthesis. What you are talking about is a trailing closure syntax, which is only if you have a closure that is the last argument of the function. You don't have to use trailing closure syntax if you don't want to.

[@josejimenez7502]

They are making it easy.

[@iOSAcademy]

Yep!

[@junglee-bee]

`async throws -> T` is a better option than `async -> Result` but by now I know you will say “It’s Subjective” 😝 which of course it is.

[@iOSAcademy]

I actually love generics but a bit advanced for the general audience

[@junglee-bee]

@@iOSAcademy oh, sorry, I actually meant `async throws -> [User]`
but i really like ur content. hope u hit ur 50k target soon :)

[@DanielYDev]

If a network error has occurredit is better to inform to view layer, don't you think?
It may be necessary to handler the type of error or inform the user.
I think...

[@fermatslasttheorem6298]

throws or result - either is good depending on the use case.

[@coffeebydny393]

Thanks for the content, btw which theme in Xcode do you use?

[@iOSAcademy]

Midnight

[@3909630]

yeah ima call you professor iOS now

[@iOSAcademy]

haha thanks!

[@RahulVerma-tv6gq]

But what if we are using alamofire which returns a Result type data, from which it’s not possible to return data as we can’t return anything inside cases of result, how to handle that any help would be appreciated.

[@asigivati1382]

can you or someone please tell me what is the different of the tableview variable you wrote that looks the same as lazy variable definition, but without the lazy keyword.
is it behave like lazy? is this variable create only once and only when someone access to it?
at 03:55

[@franciscoarciganolasco6027]

if use Task what would happen?

[@samha1513]

async {} is now Task.init(operation: {})

[@fermatslasttheorem6298]

Or just "Task { }" - which is the same thing. You don't have to use init and the only argument can be done with a trailing closure.

[@hakankumdakc9233]

how did you do that without adding import _Concurrency? I get error about couldn't found async. Also imported concurrency but couldn't found that module.

[@iOSAcademy]

It should work in xcode 13

[@TheSpiralnotizblock]

Do you have a video on how to use a REST API with Swift?

[@iOSAcademy]

Yes, just search for API on the channel

[@TheSpiralnotizblock]

@@iOSAcademy Great!

[@hajjdawood]

I wish these tutorials were done in SwiftUI, much cleaner, and much faster. Instead of spending like 8 minutes setting up the project due to UIkit nonsense, just add List (user) and be done.

[@dhav7634]

We all know async calls do not block execution until the async operation is completed.
With await being introduced are we still doing that or are we waiting on the async operation being completed?

[@iOSAcademy]

Waiting

[@dhav7634]

@@iOSAcademy Got it. So anything that we do NOT want to wait for async call should be outside the "Task" block?

[@lyphuc4362]

from javascript

[@MrPerucan]

Literally lol

[@iOSAcademy]

Yep!

[@glennadams7047]

I know right ? What took so long ??? Apple is a $2T company.

[@TheBooban]

so is @escaping completion handlers obsolete now?

[@iOSAcademy]

No. Both are still valid

[@Martin-xj8rp]

@@iOSAcademy but its possible to replace the completion Blocks with it, right?

[@justworkfine321]

Is concurrency is async?

[@iOSAcademy]

Yes

[@sebastianstrus6273]

Bad quality of the video. Please fix this. You hurt our eyes. Besides that, thanks for the content. It's very helpful.

[@aliquewilliams3080]

You wasted almost half the video setting up the project before showing the concept. Next time, have the project already prepared.

[@emmanuelpregnolato5026]

I think the weak self attempt was correct.
async { [weak self] in
guard let _self = self else {
return
}
let users = await fetchUsers()
_self.users = users
DispatchQueue.main.async {
_self.tableView.reloadData()
}
}
🙃

[@fermatslasttheorem6298]

As of Swift 5, you can use "let self = self "

[@maqusss]

setting users property in 8:54 should also happen on main thread. Does "async" in line 31 dispatch closure on current thread? that would make DispatchQueue.main.asynch from line 35 unneccesary.

[@MrLinusunil]

AFAIK you can perfectly do that on non-main threads. Only updating the UI (like reloading the table view) needs to be on the main thread.

[@maqusss]

@@MrLinusunil You can if you use some kind of synchronization.
Otherwise you have potential data race or inconsistent state because two threads are accessing the same property, one changing it.
For example: property is read on main thread in table view data source method numberOfRows,
then propeerty is changed on non-main thread before cellForRowAt call, then you have crash "index out of range".