Your code will work fine: the weak reference will not cause a retain cycle as you explicitly instruct ARC not to increase the retainCount of your weak object. For best practice, however, you should create a strong reference of your object using the weak one. This won’t create a retain cycle either as the strong … Read more
If you are using Xcode 8 or above, you can use the memory graph thingy to see what object holds a reference to what object. To see the memory graph, first build and run your app with Xcode. When you want to check whether all the instances you created are discarded properly, go to this … Read more
If self could be nil in the closure use [weak self]. If self will never be nil in the closure use [unowned self]. If it’s crashing when you use [unowned self] I would guess that self is nil at some point in that closure, which is why you had to go with [weak self] instead. … Read more