iOS-Swift Blog

As we all know that iPhone and iPad apps will be available on Mac App Store on Apple silicon. So if you are willing not to serve on Mac App Store we need to do some changes to  our deployed builds. As we know this is going to happen automatically on Apple Silicon Mac for all your iOS/iPad App. Though there will be no modification on the App.  Thank God !! There is no extra work for porting to the Mac App.   Do not worry about the framework and all they will work just fine as they were working on the iPhone and iPad, the framework will be intact as it is. So Happy 😊 How we can identify the app on the Mac App Store, Users will be able to find iPhone and iPad apps right on the Mac App Store. These apps will be distinguished by the “ Designed for iPhone ” and “ Designed for iPad ” badge next to the app icon. You should not worry about the rating and review as well those will be independently mapped. Managing Mac App Store availability.   By default, your apps will be pub

 As we discussed the closure in detail in the previous blog as Closure in Swift - Part 1 . I would like to suggest to go first if you want to understand this better.  Closures as Reference Types: As if we assign as  let closure =  closreReturnFromFunction()   to constant but that does not mean that its constant and closure scope can not be changed. As you have seen in the previous  Closure in Swift - Part 1 .  that counter can be modified once the closure will execute, this is because closure is reference types.   When we assigned closure to variable or constant we actually assigned closure reference not the content of closure. I Hope, it's clear !!. Escaping Closures: A closure is said to be escaping closure when it is passed as a function argument to the function and it will execute after the function returns from its scope. This is asynchronous in behavior.   Let's understand what that does It means. It's simple. Trust me. So when the function starts execut