iOS – completion block in UIView animateWithDuration gets called too early

3 Solutions Collect From Internet About “iOS – completion block in UIView animateWithDuration gets called too early”

From the UIView documentation:


A block object to be executed when the animation sequence ends. This block has no return value and takes a single Boolean argument that indicates whether or not the animations actually finished before the completion handler was called. If the duration of the animation is 0, this block is performed at the beginning of the next run loop cycle. This parameter may be NULL.

What this means is that there isn’t a guarantee that the code will be executed only when the animation is done. I’d advise you to check the “finished” parameter as a condition for execution.

Yes. It is being called too early because it’s being interrupted somehow. Probably by a modal presentation transition or perhaps something else. Depending on your needs, the following may be a solution you like. We avoid the conflict by manually delaying the execution of our animation code like so:

// To get this in Xcode very easily start typing, "dispatch_aft..."

// Note the "0.2". This ensures the outstanding animation gets completed before we start ours
dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(0.2 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{
    [UIView animateWithDuration:1.0 delay:0 options:0 animations:^{
        // Your animation code
    } completion:^(BOOL finished) {
        // Your completion code

It’s also possible for the completion to be called early if the animation has no effect, e.g. setting the alpha of a view to the value it already has.