Pull to Refresh in Swift 5 - Refresh control (Xcode 11, 2020) - iOS Development

[@mohamedjaber2836]

Dude, your channel is the best channel for iOS.....KEEP IT UP.....

[@shehryarahmed3371]

You're amazing buddy 😍

[@JusCJay]

Your videos are great! I've been wondering how to do this for a long time now. I'm about to go update some apps with a refresh! Keep the great content coming. I want to be a fast as you one day. -CJ

[@bini-4-christ]

LIKE button smashed 👊👊👊

[@iOSAcademy]

WOOO haha thanks

[@borbagui]

Thanks, work for me!

[@iOSAcademy]

nice!

[@ThanhNguyen-ux3vc]

wow great thank you very much

[@scottmanny]

Thank you, exactly what I was looking for.

[@bestfireplace4173]

U r the best

[@iOSAcademy]

thanks

[@headach09]

Hi, Thanks for the video. The whole process from scratch is really awesome. I wonder the method to Refresh control is use third party or it is xcode build in method. (it seems like build in method, is it !?) Thanks 😀

[@iOSAcademy]

thanks

[@rev_kous9275]

That’s very useful, thanks.

[@iOSAcademy]

Thanks

[@TacianoMaximo]

Tks, thats help me!!!!!

[@iOSAcademy]

Youre welcome!

[@Shermyyy]

Great video as always! Do you have any plans for videos on singletons and MVVM?

[@justinpeterson2120]

Can you show us a video where a user can check off a tableview and click a button to send those checked items to the desired table view ?

[@MikaelMengistu]

Great stuff!

[@iOSAcademy]

Thanks

[@dev_jeongdaeri]

Super cool!!!

[@davidhere_23]

I am sorry but may I know what's the for: .valueChanged means? Like why do we need to put that since it's not used in the code in the video. And also I don't quite understand why do we need to put [weak self] just because we do appending in the closure. I am new to this and would appreciate if anyone can clear my doubts thanks!

[@ProductsHub365]

what ever the objects we deal inside closure .. sometimes returns optional value or they might have some value .. if we are damn sure that are objects definitely has some value in them . use owned self as a capture list .. else if we are sure that our objects lack some values or might be nil we should handle with weak self .. both weak and unowned used to avoid retain cycles .. if we try to do any closure functionality without weak or unowned .. till this closure finish its task particular.. controller will gets hold in the memory if we use weak self .. it makes sure that we are not holding any strong refereence to any controller and instance controller deallcoation is done. make sure you dont force wrap self inside weak self closure ... if we use unowned .. we have to make sure that object isnide closure cannot be nil until closure finishes it task .. it can be used only if we have gurantee that object has certain value in it or stays in memory

[@TheseEyesSeeDarknessClearly7]

12:40

[@martintaborsky9954]

Why it does not work on iPhone X? I have tested it on real devices like iphone x and 6s both have ios 14.6 on 6s works on X does not work

[@iOSAcademy]

Might be in Apple bag