i can guarantee that even paid course anywhere dont teach you like how you explain each and every thing keep up the good work its really helpfull for developers like me to find content like yours
This is my go-to channel for iOS stuff. Learned alot in past from you and still learning. What sets you apart from other is you tell us not only how to do things but also how not to do things also. Ravi bhai mast kam karata hai tum, mereko tumako ♥️ se thank you bolane ka hai.
why your content so good :) ...You are really saviour...you just explain each and every bit in a such a way that where anyone can understand. kudos to you.. sharing your videos to my fellow mates. Thank you once again.
Thank you for the kind words, I am glad the content is helping you, feel free to ask questions on this topic and do share the channel with your iOS group
Indeed, I have mentioned the reason why the video was delayed but I am glad now it’s out 😊 plz feel free to ask questions and do share the video with your iOS group
Before I watched hecking with swift video all most two months ago related of async wait But not show bug Thanks you for providing latest method with own language (Hindi)
When I found one bug in the toolchain I was a little hesitant to show this feature, coz I knew this was a complex integration and bugs are bound to come and hence I delayed this. Every second channel was showing async await and I was like damn everyone on RUclips is in a race to show this feature first 😅 for views maybe but I am tortoise in that case
Thank you so much Ravi, this is the most readable, understandable and easy to maintain code for webservice call I have seen, One doubt I have, in case of error(error in http response or error in error variable) we want to display error Message in alert, Where should I place it, 1) In HttpUtility then i need to pass reference of controller thorough all functions or 2) in ViewContoller itself in this case code gets repeated for all viewcontrollers
I was thinking how will we break the await call sequence from the first function call which is not async in nature i.e here from view controller.. now got to know that "Task" helps here to break that await call chain. Thanks again for sharing another great content.
I am yet to try async await with SwiftUI and am assuming there it would be even more helpful as compared to UIKit thanks to the pub-sub approach, I don’t really like the Task approach but it is what it is I guess. Glad the video the was helpful 🙏 feel free to ask questions and do share the video with your iOS group
Dispatch group solves a different problem as compared to async await and hence it’s too early to say let’s dump the dispatch framework and use async await permanent. If I want to call 5 APIs all at once and I don’t care about the sequence then in that case DG is more useful as compared to async await
Hi Ravi, what if getToken() method takes much time (1 min), will getPayroll gives error? If yes, how to dependency for those 2 async methods (without operationqueues)?
You can use async await now to handle such use cases and that way when the first operation fails you can send the appropriate message from your service layer to the viewModel. If an api is taking more than a minute then that’s a performance bottleneck of that api and the api developers must fix that on priority
@@CodeCat15 let resultFirst = await testAsyncWaitFirstAPICall() //takes 10 sec let resultSecond = await testAsyncWaitTwoAPICall(input: resultFirst) // takes 5 sec print("hello test") // some code after async-await Que: Will print executed immediately OR after await completion? What I understand is, await will block the current execution flow, correct?
One of the highly recommended resources for understanding Clean Architecture be it iOS or any other technology that you learn in the future is the book "Clean Architecture: A Craftsman's Guide to Software Structure and Design" by Robert C. Martin (Uncle Bob). This book provides in-depth insights into Clean Architecture principles and how to apply them to iOS development.
The HttpUtility class has URLSession calls which is an apple class and has no business logic or any special cases, so writing test cases for this library would be futile because you would write test cases for your service layers which will use this utility so in a way you would end up indirectly testing the utility.
Hi Ravi, Thanks a lot for sharing this video. It's so fruit full. But I Have doubts for same: we are creating same nested cycles after one API to another API. It's like same dependency one API to another, so how we fixed this? Apart from that everything is awesome.
I like and want to use the Async await in one of the application but there are some rest APIs that are getting failed to respond, how can I manage a retry call with Async await. If I want to retry more then 3 times and still fail then I need to continue with the next api...How can I manage the retry flow can you pls explain?
Glad it was helpful Priyanka, as the this SO post it seems it can be done, I have not tried doing that yet but surely will release an IG video on it if needed stackoverflow.com/questions/70172361/how-to-run-multiple-api-call-simultaneously-using-async-await-in-swift
That’s a wonderful suggestion I would love doing that in the future videos, I have made a note of it and to test this I have some complex use cases in mind as well. Thank you for suggesting this
Hello Ravi, I hope you doing very well. If we have to show any alert when error comes from server or request time out then how can we do it? Some time we have to create one error screen for reload data so how can we manage?
In this case you may display the error in the Task struct, although I am not a big fan of how its done, since this feature is new I too am playing around with it and will be showing more of it in the coming videos as the swift community will be adapting async await heavily in their code.
Hello In second view controller i click on button and call this code which dismiss the controller Self.dismiss(animation: true, completion: nil) What i want is after press the button it took 5 seconds of time to dismissed the controller screen
Task awaits the async operations to complete, a little detail is provided in the actor video as to how Task works and maybe the delay is because Task is trying to finish the async task first and then dismiss the controller.
Hello Sir, Thanks to you for another nice tutorial. I am stuck in my project for making a walkie talkie app. I am unable to awake my application using notifications when app in background or closeed state. Can you please help me. I tried everywhere but no help. Can i contact you by any medium.
i can guarantee that even paid course anywhere dont teach you like how you explain each and every thing keep up the good work its really helpfull for developers like me to find content like yours
Thank you Afzal for your kind words means a lot to me 👍
true
💯 true🔥
This is my go-to channel for iOS stuff. Learned alot in past from you and still learning. What sets you apart from other is you tell us not only how to do things but also how not to do things also.
Ravi bhai mast kam karata hai tum, mereko tumako ♥️ se thank you bolane ka hai.
Thank you for your kind words bhai, I am glad the video was helpful
itni mehant(hard-work) Ravi Bhai
Thank you Junaid 🙏
@@CodeCat15 typo mistake . Too much hard work you do for your followers. Keep it up
Excellent 👏👏👏👏👏👏👏👏
Thank you Sai
Love to see you back with fire 🔥! Awesome video!
More to come!
amazing series Ravi. thanks a lot. binge watched the whole playlist. 👌
Glad it was helpful Siddharth
why your content so good :) ...You are really saviour...you just explain each and every bit in a such a way that where anyone can understand. kudos to you.. sharing your videos to my fellow mates. Thank you once again.
Thank you for the kind words, I am glad the content is helping you, feel free to ask questions on this topic and do share the channel with your iOS group
Thank you Sir for these informative videos. Very helpful & we always learn new things in each video.
Am glad this was helpful 🙏 hopefully the content will be helpful even while you are preparing for interviews
@@CodeCat15
Thank You for your kind words
Great Sir G !! Excellent Work.
Thank you 🙏 I am glad this was helpful, please feel free to ask questions and do share the video with your iOS group
I really like all your videos... you explain every topic in a very simple and interesting way.
Thank you for your kind words Ajay 😊 plz feel free to ask questions and do share the video with your iOS group
Great Sir !! Excellent Work
Glad this was helpful 🙏
Thank you Ravi for this wonderful series.
Glad it was helpful Kalpesh, please feel free to ask questions and do share the video with your iOS group.
This was much awaited video. !!❤️
Indeed, I have mentioned the reason why the video was delayed but I am glad now it’s out 😊 plz feel free to ask questions and do share the video with your iOS group
Superb! Ravi, Thank you so much.
I am glad this was helpful 😊
Awesome learning with simplest manner... thanks a lot.. keep doing great work :)
I am glad this video was helpful, please feel free to ask questions on the topic or share the video with your iOS group
Thanks for another informative video.
You bet!
Hi Ravi , I really like all your videos... You explain every topic in a very simple and interesting way.
Thank you Garima, am glad these videos are helpful. Please feel free to ask questions and do share the channel with your iOS group 😊
Helpful video, as always 👍👍
Glad this was helpful 😊
Good explaination video found gold in heap :)
Learning a lot from you. Would you kindly include subtitles to your videos? They would be really beneficial.
Thank you very much for this video. I love your videos I got lot of confidence after subscribing your channel.
Glad that the channel has helped you this much, thank you for your kind words and feedback means a lot to me
Before I watched hecking with swift video all most two months ago related of async wait
But not show bug
Thanks you for providing latest method with own language (Hindi)
When I found one bug in the toolchain I was a little hesitant to show this feature, coz I knew this was a complex integration and bugs are bound to come and hence I delayed this.
Every second channel was showing async await and I was like damn everyone on RUclips is in a race to show this feature first 😅 for views maybe but I am tortoise in that case
Thank you so much Ravi, this is the most readable, understandable and easy to maintain code for webservice call I have seen, One doubt I have, in case of error(error in http response or error in error variable) we want to display error Message in alert, Where should I place it, 1) In HttpUtility then i need to pass reference of controller thorough all functions or 2) in ViewContoller itself in this case code gets repeated for all viewcontrollers
the error can be returned in the delegate function and can be displayed on the main thread on the view controller
I was thinking how will we break the await call sequence from the first function call which is not async in nature i.e here from view controller.. now got to know that "Task" helps here to break that await call chain. Thanks again for sharing another great content.
I am yet to try async await with SwiftUI and am assuming there it would be even more helpful as compared to UIKit thanks to the pub-sub approach, I don’t really like the Task approach but it is what it is I guess.
Glad the video the was helpful 🙏 feel free to ask questions and do share the video with your iOS group
Video is awsm as usual. Very helpful to implement to own project .
Means this is working for any asynchronous call.can we avoid dispatch group uses?
Dispatch group solves a different problem as compared to async await and hence it’s too early to say let’s dump the dispatch framework and use async await permanent.
If I want to call 5 APIs all at once and I don’t care about the sequence then in that case DG is more useful as compared to async await
Hi Ravi, what if getToken() method takes much time (1 min), will getPayroll gives error?
If yes, how to dependency for those 2 async methods (without operationqueues)?
You can use async await now to handle such use cases and that way when the first operation fails you can send the appropriate message from your service layer to the viewModel.
If an api is taking more than a minute then that’s a performance bottleneck of that api and the api developers must fix that on priority
@@CodeCat15
let resultFirst = await testAsyncWaitFirstAPICall() //takes 10 sec
let resultSecond = await testAsyncWaitTwoAPICall(input: resultFirst) // takes 5 sec
print("hello test") // some code after async-await
Que: Will print executed immediately OR after await completion? What I understand is, await will block the current execution flow, correct?
can you please tell how to write unit test as well for async await function. you can drive from TDD
One of the highly recommended resources for understanding Clean Architecture be it iOS or any other technology that you learn in the future is the book "Clean Architecture: A Craftsman's Guide to Software Structure and Design" by Robert C. Martin (Uncle Bob). This book provides in-depth insights into Clean Architecture principles and how to apply them to iOS development.
Thank you so much bro
No problem, I am glad this was helpful
the great explanation. Loved it..! I would like to know how we can unit test the HttpUtility class as this has the generic function.
The HttpUtility class has URLSession calls which is an apple class and has no business logic or any special cases, so writing test cases for this library would be futile because you would write test cases for your service layers which will use this utility so in a way you would end up indirectly testing the utility.
Hi Ravi, Thanks a lot for sharing this video. It's so fruit full. But I Have doubts for same: we are creating same nested cycles after one API to another API. It's like same dependency one API to another, so how we fixed this? Apart from that everything is awesome.
Thank you 😊
Glad it was helpful, do share the video with your iOS group and feel free to ask questions 👍
Nice Tutorial !
one question do u know how to check Crashlytics Crash
This link will guide you out for the crashlytics logs
firebase.google.com/docs/crashlytics/test-implementation?platform=ios
@@CodeCat15 thanks ravi
Thanks Ravi. This is really nice..
Just one query. Async/await runs on which thread main thread or global thread?
When you use async/await in Swift, the code runs on a separate concurrent thread managed by the system, rather than the main thread.
I like and want to use the Async await in one of the application but there are some rest APIs that are getting failed to respond, how can I manage a retry call with Async await. If I want to retry more then 3 times and still fail then I need to continue with the next api...How can I manage the retry flow can you pls explain?
Thank you Ravi for sharing latest important information and I really like it 👍Can we achieve multiple calls at a time by this async / await?
Glad it was helpful Priyanka, as the this SO post it seems it can be done, I have not tried doing that yet but surely will release an IG video on it if needed
stackoverflow.com/questions/70172361/how-to-run-multiple-api-call-simultaneously-using-async-await-in-swift
Thank you Sir, for this amazing video with such a nice explanations. Can you do time test for different approaches?
That’s a wonderful suggestion I would love doing that in the future videos, I have made a note of it and to test this I have some complex use cases in mind as well.
Thank you for suggesting this
@@CodeCat15 Welcome Sir
Hello Ravi,
I hope you doing very well.
If we have to show any alert when error comes from server or request time out then how can we do it?
Some time we have to create one error screen for reload data so how can we manage?
In this case you may display the error in the Task struct, although I am not a big fan of how its done, since this feature is new I too am playing around with it and will be showing more of it in the coming videos as the swift community will be adapting async await heavily in their code.
Hello
In second view controller i click on button and call this code which dismiss the controller
Self.dismiss(animation: true, completion: nil)
What i want is after press the button it took 5 seconds of time to dismissed the controller screen
Task awaits the async operations to complete, a little detail is provided in the actor video as to how Task works and maybe the delay is because Task is trying to finish the async task first and then dismiss the controller.
@codecat create one video for UITableviewDiffableDatasource and UICollcetionDiffable
I like async await but don’t like the do catch block everywhere
same here but I think it's a necessary evil to make sure to capture unexpected behavior of the application a tradeoff to live with I guess
Thank u
Welcome 🙂
Hello Sir,
Thanks to you for another nice tutorial.
I am stuck in my project for making a walkie talkie app. I am unable to awake my application using notifications when app in background or closeed state. Can you please help me. I tried everywhere but no help. Can i contact you by any medium.
Bro Push notification pe video banao na
Please tell me in English
What's your question? I will be happy to explain it for you.
😊