Swift version: 5.6
Unless you specific otherwise, all Swift properties are strong, which means they will not be removed from RAM until whatever owns them is removed from RAM. So, if you create an array in your view controller and you want it to stick around until the view controller is destroyed, that's what strong does.
Weak on the other hand is there when you want to say "I want to be able to reference this variable, but I don't mind if it goes away, so I don't want to own it." This might seem strange: after all, where's the point in having a reference to a variable that might not be there?
Well, the answer lies in a thing called reference cycles. If object A has a strong variable pointing at object B, and object B has a strong variable pointing at object A, neither object would ever be deleted because they both keep each other alive.
In this situation, having one of the objects change their property to be weak would solve the problem. For example, object A has a strong variable to object B, but object B has a weak variable pointing at object A. This guarantees that B cannot be destroyed while A still exists, but A can be destroyed because B doesn't have a strong variable owning it.
SPONSORED In-app subscriptions are a pain. The code can be hard to write, full of edge cases, and time-consuming to maintain. RevenueCat provides a backend and wrapper around StoreKit to make things simple so you can focus on building your app.
Available from iOS 7.0 – see Hacking with Swift tutorial 1
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.