By VaporwareWolf

2013-09-13 23:54:06 8 Comments

I've been updating my apps to run on iOS 7 which is going smoothly for the most part. I have noticed in more than one app that the reloadData method of a UICollectionViewController isn't acting quite how it used to.

I'll load the UICollectionViewController, populate the UICollectionView with some data as normal. This works great on the first time. However if I request new data (populate the UICollectionViewDataSource), and then call reloadData, it will query the data source for numberOfItemsInSection and numberOfSectionsInCollectionView, but it doesn't seem to call cellForItemAtIndexPath the proper number of times.

If I change the code to only reload one section, then it will function properly. This is no problem for me to change these, but I don't think I should have to. reloadData should reload all visible cells according to the documentation.

Has anyone else seen this?


@dimpiax 2015-09-06 18:30:43

Swift 5 – 4 – 3

// GCD    
DispatchQueue.main.async(execute: collectionView.reloadData)

// Operation

Swift 2

// Operation

@Wissa 2018-06-04 03:39:09

Here is how it worked for me in Swift 4

func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {

let cell = campaignsCollection.dequeueReusableCell(withReuseIdentifier: "Cell", for: indexPath) as! Cell


    DispatchQueue.main.async {

    return cell

@Prajakta 2018-03-26 08:27:55

 dispatch_async(dispatch_get_main_queue(), ^{

            [collectionView reloadData];
            [collectionView layoutIfNeeded];
            [collectionView reloadData];


it worked for me.

@zszen 2017-11-20 17:42:58

inservif (isInsertHead) {
   [self insertItemsAtIndexPaths:tmpPoolIndex];
   NSArray * visibleIdx = [self indexPathsForVisibleItems];
   if (visibleIdx.count) {
       [self reloadItemsAtIndexPaths:visibleIdx];
}else if (isFirstSyncData) {
    [self reloadData];
   [self insertItemsAtIndexPaths:tmpPoolIndex];

@Liki qu 2017-06-22 03:39:49

try this code.

 NSArray * visibleIdx = [self.collectionView indexPathsForVisibleItems];

    if (visibleIdx.count) {
        [self.collectionView reloadItemsAtIndexPaths:visibleIdx];

@WeZZard 2015-10-27 11:00:54

The solution given by Shaunti Fondrisi is nearly perfect. But such a piece of code or codes like enqueue the execution of UICollectionView's reloadData() to NSOperationQueue's mainQueue indeed puts the execution timing to the beginning of the next event loop in the run loop, which could make the UICollectionView update with a flick.

To solve this issue. We must put the execution timing of the same piece of code to the end of current event loop but not the beginning of the next. And we can achieve this by making use of CFRunLoopObserver.

CFRunLoopObserver observes all the input source waiting activities and the run loop's entry and exit activity.

public struct CFRunLoopActivity : OptionSetType {
    public init(rawValue: CFOptionFlags)

    public static var Entry: CFRunLoopActivity { get }
    public static var BeforeTimers: CFRunLoopActivity { get }
    public static var BeforeSources: CFRunLoopActivity { get }
    public static var BeforeWaiting: CFRunLoopActivity { get }
    public static var AfterWaiting: CFRunLoopActivity { get }
    public static var Exit: CFRunLoopActivity { get }
    public static var AllActivities: CFRunLoopActivity { get }

Among those activities, .AfterWaiting can be observed when current event loop is about to end, and .BeforeWaiting can be observed when the next event loop just has began.

As there is only one NSRunLoop instance per NSThread and NSRunLoop exactly drives the NSThread, we can consider that accesses come from the same NSRunLoop instance always never cross threads.

Based on points mentioned before, we can now write the code: an NSRunLoop-based task dispatcher:

import Foundation
import ObjectiveC

public struct Weak<T: AnyObject>: Hashable {
    private weak var _value: T?
    public weak var value: T? { return _value }
    public init(_ aValue: T) { _value = aValue }

    public var hashValue: Int {
        guard let value = self.value else { return 0 }
        return ObjectIdentifier(value).hashValue

public func ==<T: AnyObject where T: Equatable>(lhs: Weak<T>, rhs: Weak<T>)
    -> Bool
    return lhs.value == rhs.value

public func ==<T: AnyObject>(lhs: Weak<T>, rhs: Weak<T>) -> Bool {
    return lhs.value === rhs.value

public func ===<T: AnyObject>(lhs: Weak<T>, rhs: Weak<T>) -> Bool {
    return lhs.value === rhs.value

private var dispatchObserverKey =

private var taskQueueKey =

private var taskAmendQueueKey =

private typealias DeallocFunctionPointer =
    @convention(c) (Unmanaged<NSRunLoop>, Selector) -> Void

private var original_dealloc_imp: IMP?

private let swizzled_dealloc_imp: DeallocFunctionPointer = {
    (aSelf: Unmanaged<NSRunLoop>,
    aSelector: Selector)
    -> Void in

    let unretainedSelf = aSelf.takeUnretainedValue()

    if unretainedSelf.isDispatchObserverLoaded {
        let observer = unretainedSelf.dispatchObserver

    if let original_dealloc_imp = original_dealloc_imp {
        let originalDealloc = unsafeBitCast(original_dealloc_imp,
        originalDealloc(aSelf, aSelector)
    } else {
        fatalError("The original implementation of dealloc for NSRunLoop cannot be found!")

public enum NSRunLoopTaskInvokeTiming: Int {
    case NextLoopBegan
    case CurrentLoopEnded
    case Idle

extension NSRunLoop {

    public func perform(closure: ()->Void) -> Task {
        let task = Task(self, closure)
        return task

    public override class func initialize() {

        struct Static {
            static var token: dispatch_once_t = 0
        // make sure this isn't a subclass
        if self !== NSRunLoop.self {

        dispatch_once(&Static.token) {
            let selectorDealloc: Selector = "dealloc"
            original_dealloc_imp =
                class_getMethodImplementation(self, selectorDealloc)

            let swizzled_dealloc = unsafeBitCast(swizzled_dealloc_imp, IMP.self)

            class_replaceMethod(self, selectorDealloc, swizzled_dealloc, "@:")

    public final class Task {
        private let weakRunLoop: Weak<NSRunLoop>

        private var _invokeTiming: NSRunLoopTaskInvokeTiming
        private var invokeTiming: NSRunLoopTaskInvokeTiming {
            var theInvokeTiming: NSRunLoopTaskInvokeTiming = .NextLoopBegan
            guard let amendQueue = weakRunLoop.value?.taskAmendQueue else {
                fatalError("Accessing a dealloced run loop")
            dispatch_sync(amendQueue) { () -> Void in
                theInvokeTiming = self._invokeTiming
            return theInvokeTiming

        private var _modes: NSRunLoopMode
        private var modes: NSRunLoopMode {
            var theModes: NSRunLoopMode = []
            guard let amendQueue = weakRunLoop.value?.taskAmendQueue else {
                fatalError("Accessing a dealloced run loop")
            dispatch_sync(amendQueue) { () -> Void in
                theModes = self._modes
            return theModes

        private let closure: () -> Void

        private init(_ runLoop: NSRunLoop, _ aClosure: () -> Void) {
            weakRunLoop = Weak<NSRunLoop>(runLoop)
            _invokeTiming = .NextLoopBegan
            _modes = .defaultMode
            closure = aClosure

        public func forModes(modes: NSRunLoopMode) -> Task {
            if let amendQueue = weakRunLoop.value?.taskAmendQueue {
                dispatch_async(amendQueue) { [weak self] () -> Void in
                    self?._modes = modes
            return self

        public func when(invokeTiming: NSRunLoopTaskInvokeTiming) -> Task {
            if let amendQueue = weakRunLoop.value?.taskAmendQueue {
                dispatch_async(amendQueue) { [weak self] () -> Void in
                    self?._invokeTiming = invokeTiming
            return self

    private var isDispatchObserverLoaded: Bool {
        return objc_getAssociatedObject(self, &dispatchObserverKey) !== nil

    private func loadDispatchObserverIfNeeded() {
        if !isDispatchObserverLoaded {
            let invokeTimings: [NSRunLoopTaskInvokeTiming] =
            [.CurrentLoopEnded, .NextLoopBegan, .Idle]

            let activities =
            CFRunLoopActivity({ CFRunLoopActivity($0) })

            let observer = CFRunLoopObserverCreateWithHandler(
                true, 0,


            let wrappedObserver = NSAssociated<CFRunLoopObserver>(observer)


    private var dispatchObserver: CFRunLoopObserver {
        return (objc_getAssociatedObject(self, &dispatchObserverKey)
            as! NSAssociated<CFRunLoopObserver>)

    private var taskQueue: [Task] {
        get {
            if let taskQueue = objc_getAssociatedObject(self,
                as? [Task]
                return taskQueue
            } else {
                let initialValue = [Task]()


                return initialValue
        set {


    private var taskAmendQueue: dispatch_queue_t {
        if let taskQueue = objc_getAssociatedObject(self,
            as? dispatch_queue_t
            return taskQueue
        } else {
            let initialValue =


            return initialValue

    private func handleRunLoopActivityWithObserver(observer: CFRunLoopObserver!,
        activity: CFRunLoopActivity)
        -> Void
        var removedIndices = [Int]()

        let runLoopMode: NSRunLoopMode = currentRunLoopMode

        for (index, eachTask) in taskQueue.enumerate() {
            let expectedRunLoopModes = eachTask.modes
            let expectedRunLoopActivitiy =

            let runLoopModesMatches = expectedRunLoopModes.contains(runLoopMode)
                || expectedRunLoopModes.contains(.commonModes)

            let runLoopActivityMatches =

            if runLoopModesMatches && runLoopActivityMatches {


extension CFRunLoopActivity {
    private init(_ invokeTiming: NSRunLoopTaskInvokeTiming) {
        switch invokeTiming {
        case .NextLoopBegan:        self = .AfterWaiting
        case .CurrentLoopEnded:     self = .BeforeWaiting
        case .Idle:                 self = .Exit

With the code before, we can now dispatch the execution of UICollectionView's reloadData() to the end of current event loop by such a piece of code:

NSRunLoop.currentRunLoop().perform({ () -> Void in

In fact, such an NSRunLoop based task dispatcher has already been in one of my personal used framework: Nest. And here is its repository on GitHub:

@Oded Regev 2015-09-01 13:06:26

Check that each one of the UICollectionView Delegate methods does what you expect it to do. For example, if


doesn't return a valid size, the reload won't work...

@Jiang Qi 2015-07-09 04:59:20

Do you set UICollectionView.contentInset? remove the left and right edgeInset, everything is ok after I remove them, the bug still exists in iOS8.3 .

@Shaunti Fondrisi 2013-12-04 21:09:08

Force this on the main thread:

dispatch_async(dispatch_get_main_queue(), ^ {
    [self.collectionView reloadData];

@Jonauz 2013-12-13 01:45:50

You are welcome to explain more..

@Shaunti Fondrisi 2014-01-02 18:54:28

I'm not sure if I can explain more. After searching, researching, testing and probing. I feel this is an iOS 7 bug. Forcing the main thread will run all UIKit related messages. I seem to run into this when popping to the view from another view controller. I refresh the data on viewWillAppear. I could see the data and collection view reload call, but the UI was not updated. Forced the main thread (UI thread), and it magically starts working. This is only in IOS 7.

@Raphael Oliveira 2014-05-09 14:57:01

It doesn't make that much sense because you cannot call reloadData out of main thread (you can't update views out of the main thread) so this maybe is a side effect that results in what you want due to some race conditions.

@Joony 2015-08-13 06:51:32

Dispatching on the main queue from the main queue just delays execution until the next run loop, allowing everything that's currently queued a chance to execute first.

@Fidel Eduardo López 2015-09-11 16:43:27

Thanks!! Still don't understand if Joony argument is correct because core data request consume it's time and it's answer is delayed or because i'm reloading data at willDisplayCell.

@Karan Alangat 2016-06-22 07:32:10

it didn't work for me :(

@Shaunti Fondrisi 2016-08-30 15:24:54

Wow all this time and this still comes up. This is indeed a race condition, or related to the view event lifecycle. view "Will" appear would have been drawn already. Good insight Joony, Thanks. Think we can set this item to "answered" finally?

@Vinay Jain 2015-03-20 04:53:51

It happened with me too in iOS 8.1 sdk, but I got it correct when I noticed that even after updating the datasource the method numberOfItemsInSection: was not returning the new count of items. I updated the count and got it working.

@nyxee 2017-07-21 14:29:56

how did you update that count please.. All the above methods have failed to work for me in swift 3.

@Anton Matosov 2014-03-02 21:25:11

I had exactly the same issue, however I managed to find what was going on wrong. In my case I was calling reloadData from the collectionView:cellForItemAtIndexPath: which looks not to be correct.

Dispatching call of reloadData to the main queue fixed the problem once and forever.

  dispatch_async(dispatch_get_main_queue(), ^{
    [self.collectionView reloadData];

@iOSDeveloper 2014-10-08 13:18:06

can u tell me what this line is for [self.collectionData.collectionViewLayout invalidateLayout];

@Anton Matosov 2015-03-01 07:18:10

It should not be there. Thanks for pointing that out.

@sudo make install 2015-09-20 12:06:06

This solved it for me as well--in my case reloadData was being called by a change observer.

@Trung Bui 2016-02-28 16:14:52

nice job. This solved my problem. Thank you so much

@Stefan Arambasich 2016-07-10 14:22:42

Also this applies to collectionView(_:willDisplayCell:forItemAtIndexPath:)

@stephane 2014-04-15 22:25:45

Thanks first of all for this thread, very helpful. I had a similar issue with Reload Data except the symptom was that specific cells could no longer be selected in a permanent way whereas others could. No call to indexPathsForSelectedItems method or equivalent. Debugging pointed out to Reload Data. I tried both options above ; and ended up adopting the ReloadItemsAtIndexPaths option as the other options didn't work in my case or were making the collection view flash for a milli-second or so. The code below works good:

NSMutableArray *indexPaths = [[NSMutableArray alloc] init]; 
NSIndexPath *indexPath;
for (int i = 0; i < [self.assets count]; i++) {
         indexPath = [NSIndexPath indexPathForItem:i inSection:0];
         [indexPaths addObject:indexPath];
[collectionView reloadItemsAtIndexPaths:indexPaths];`

@miguelsanchez 2014-03-04 19:26:10

Reloading some items didn't work for me. In my case, and only because the collectionView I'm using has just one section, I simply reload that particular section. This time the contents are correctly reloaded. Weird that this is only happening on iOS 7 (7.0.3)

[self.collectionView reloadSections:[NSIndexSet indexSetWithIndex:0]];

@liamnichols 2013-09-30 18:04:45

In my case, the number of cells/sections in the datasource never changed and I just wanted to reload the visible content on the screen..

I managed to get around this by calling:

[self.collectionView reloadItemsAtIndexPaths:[self.collectionView indexPathsForVisibleItems]];


[self.collectionView reloadData];

@Lugubrious 2014-07-23 17:54:33

That line caused my app to crash - "*** Assertion failure in -[UICollectionView _endItemAnimations], /SourceCache/UIKit_Sim/UIKit-2935.137/UICollectionView.m:384‌​0"

@liamnichols 2014-07-25 15:05:41

@Lugubrious You are probably performing other animations at the same time.. try putting them in a performBatchUpdates:completion: block?

@Jon Evans 2014-08-11 22:37:24

This worked for me, but I'm not sure I understand why it's necessary. Any idea what the issue is?

@liamnichols 2014-08-13 12:15:02

@JonEvans Unfortunately I have no idea.. I believe it is some kind of bug in iOS, not sure if it has been resolved in later versions or not though as I haven't tested since and the project I had the issue in is no longer my problem :)

@Jon Evans 2014-08-14 02:22:44

@liamnichols Well, glad to hear that it's not a problem for you anymore at least! I will add to this that I had some crashing issues with this code until I reversed the order of the calls (so reloadData first and then reloadItemsAtIndexPaths), but since I don't know why it works at all I certainly can't explain why that helped!

@AXE 2014-08-25 09:50:39

Works for me. Thanks!

@CyberDandy 2014-12-29 16:16:58

This bug is just pure bullshit ! All my cells were - at random - disappearing when I reloaded my collectionView, only if I had one specific type of cell in my collection. I lost two days on it because I could not understand what was happening, and now that I applied your solution and that it works, I still do not understand why it is now working. That's so frustrating ! Anyway, thanks for the help :D !!

@akdsouza 2015-05-28 06:44:29

Not sure why but i had to follow this answer to get visible cells to align & size correctly on rotation change. Thanks!

@Dylan Moore 2015-06-26 02:04:42

@Shaunti 's answer should work for most and it's less performance heavy

@Nitish 2016-03-03 10:10:22

Not sure why but this saved my day. Thanks :)

@Dody Rachmat Wicaksono 2016-10-09 08:34:03

Thank you very much. It fix my issue.

@n_b 2017-03-22 19:36:50

In my case, reloadItemsAtIndexPaths had to be called after reloadData due to a data change.

@iDevAmit 2014-01-17 12:40:23

You can use this method

[collectionView reloadItemsAtIndexPaths:arayOfAllIndexPaths];

You can add all indexPath objects of your UICollectionView into array arrayOfAllIndexPaths by iterating the loop for all sections and rows with use of below method

[aray addObject:[NSIndexPath indexPathForItem:j inSection:i]];

I hope you understood and it can resolve your problem. If you need any more explanation please reply.

@user2459624 2014-01-19 10:27:32

I had the same issue with reloadData on iOS 7. After long debug session, I found the problem.

On iOS7, reloadData on UICollectionView doesn't cancel previous updates which haven't completed yet (Updates which called inside performBatchUpdates: block).

The best solution to solve this bug, is stopping all updates which currently processed and call reloadData. I didn't find a way to cancel or stop a block of performBatchUpdates. Therefore, to solve the bug, I saved a flag which indicates if there's a performBatchUpdates block which currently processed. If there isn't an update block which currently processed, I can call reloadData immediately and everything work as expected. If there's an update block which currently processed, I'll call reloadData on the complete block of performBatchUpdates.

@VaporwareWolf 2014-01-23 05:58:26

Where you performing all of your updated inside performBatchUpdate? Some in some out? All out? Very interesting post.

@user2459624 2014-08-27 13:45:44

I'm using the collection view with NSFetchedResultsController to show data from CoreData. When the NSFetchedResultsController delegate notify on changes, I gather all the updates and call them inside performBatchUpdates. When the NSFetchedResultsController request predicate is changed, reloadData must be called.

@Avner Barr 2013-10-01 09:32:37

I also had this problem. By coincidence I added a button on top of the collectionview in order to force reloading for testing - and all of a sudden the methods started getting called.

Also just adding something as simple as

UIView *aView = [UIView new];
[collectionView addSubView:aView];

would cause the methods to be called

Also I played around with the frame size - and voila the methods were getting called.

There are a lot of bugs with iOS7 UICollectionView.

@VaporwareWolf 2013-10-02 16:58:33

I'm glad to see (in certian ways) that others are experiencing this problem as well. Thanks for the workaround.

Related Questions

Sponsored Content

5 Answered Questions

[SOLVED] UICollection view reloadData cause recreate visible cell

8 Answered Questions

[SOLVED] UICollectionView animate data change

1 Answered Questions

1 Answered Questions

[SOLVED] UICollectionview datas loading issue

2 Answered Questions

3 Answered Questions

1 Answered Questions

1 Answered Questions

1 Answered Questions

Sponsored Content