You're likely using [weak self] incorrectly in your Swift Tasks... #concurrency #swift #ios

[0:01]It might not be obvious, but the code below has a memory leak. We have a weak self capture inside of the task, and we immediately make that capture strong again. Tasks can swift concurrency start running as soon as possible, which in practice is pretty much immediately. So that means that self hasn't gone away at the point that this task would start. So that guard is pretty much always going to allow us to have a strong capture of self. In the while loop, we make use of self by fetching more pages, and we keep going as long as there are more pages available. This means that for the duration of the while loop, self cannot go away. If we do want self to be able to be deallocated, we need to make sure we don't have a strong reference at the start of our task. We can unwrap self inside of the while loop instead, making every iteration have its own strong reference to self. This solves the leak and avoids one of the common issues I see in tasks.