How to create a Generic Networking Layer in iOS apps (Refresh Tokens, Combine, Async/Await, SwiftUI)

[@EssentialDeveloper]

Sign up to gain FREE access to exclusive iOS dev courses, workshops, and mentoring sessions: www.essentialdeveloper.com/community?

[@sebastiankubiak7874]

😊😊😊😊

[@Joao-nn6gn]

Not only impressed by the tecnical content, but with how good Caio is in capture what the student is struggleing with

[@mistymu8154]

This is one of the best videos I have watched on this topic. I have coupled the HTTP part and the decoding part so many times. As you point out, it quickly becomes a mess with a bunch of different if statements to handle different APIs and things like an empty 204 or a 307 redirect which either do not return JSON or a different JSON than a 200 response.

[@maciusessa]

Daaaaaamn... Outstanding video. Needed that in my project. Great. Thanks a lot! :D

[@shreyshrivastava8551]

We use both async await and Combine. If developer wants publisher, he can wrap the response in a publisher and send it forward.

[@incelemeTRe]

Thank you for this excellent session!

[@EssentialDeveloper]

Glad you enjoyed it!

[@IamCutePanda]

could you please assessed my project and close some " grey spots " I am trying to reach a junior position ( Swift UI ) dev!

[@dineshvijaykumar4237]

In terms of the API Mappers, what would we do if our custom mapper still included functionality from the generic one? Would we duplicate the code over to the specialised mapper or is there a way to combine both mappers?

[@EssentialDeveloper]

Hi! You could extract it into another function and share it between the mappers.

[@joshkinney4895]

If you were to create a new app (mainly uikit very little swiftui) would you avoid Alomofire? Why?

[@EssentialDeveloper]

Hi! Yes, we'd avoid it because the less 3rd-party dependencies, the easier it is to maintain a project long-term. In our opinion, Alamofire doesn't provide enough benefits to justify the maintenance cost/risk.

[@pavlobudzynskyi9739]

1 thing I'm not seeing in this video is how do we implement retry logic after the token is refreshed and avoid multiple refresh requests at the same time

[@EssentialDeveloper]

Hi Pavlo. We showed it in this other session: www.essentialdeveloper.com/articles/how-to-refresh-auth-tokens-correctly-using-swift-async-await-actors-live-dev-mentoring

[@pavlobudzynskyi9739]

@@EssentialDeveloper thanks for the response, but unfortunately it's no longer publicly available. Maybe some day :)

[@suryabhan1000]

@@EssentialDeveloper actually this video is not publically available. could you?

[@EssentialDeveloper]

Hi @suryabhan1000, this video is not publicly available anymore. Only students of the iOS Lead Essentials have access to it now. Check it out if you're interested: iosacademy.essentialdeveloper.com/p/ios-lead-essentials/

[@divakukulza]

00:52:23 favorite part 01;07;34

[@sunshine_279]

Hey, the app is crashing when we click on "Alternative login for developers" button. *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'The specified URL has an unsupported scheme. Only HTTP and HTTPS URLs are supported.' *** Can you please help? also can the given code directly be used? I have same functions and flow to implement... auth token, refresh token. I have to use Async/await. Please reply

[@EssentialDeveloper]

Hi! This is not our project. We didn't write the code and we don't recommend using it directly. The goal is to watch the session and learn by using the project to practice along ✅

[@dubstepwawawa]

Where we can find sample code?

[@EssentialDeveloper]

Hi! The link is in the video description.

[@Contreras04]

wow... I have been doing it wrong all my life