iOS8 scale glitch when calling drawViewHierarchyInRect afterScreenUpdates:YES

Question

I was converting a project from iOS7 to iOS8 which uses custom transitions and needs to capture the modal after it finishes loading afterScreenUpdates:YES and was seeing that the entire screen scale up for a second and scale back down. I also see this happening in the Flickr app for iOS between sections and on Yelp app when transitioning to a photo on iOS8.

  UIGraphicsBeginImageContextWithOptions(self.view.frame.size, YES, 22.0); 
  [self.view drawViewHierarchyInRect:self.view.frame afterScreenUpdates:YES];
  UIGraphicsEndImageContext();

Adding a larger scale factor helps emphasize the glitch more... but i'm just calling this on a button press in the example.

EDIT This appears to happen on iPhone 6 and 6 plus not on the 5.

scale glitch

Sample project github

`[view.layer renderInContext:UIGraphicsGetCurrentContext()];` is a workaround for now but would prefer to not do it the ios6 and older way — glued, Sep 27 '14 at 01:50
It happens on almost all the pre-iPhone 6 devices running on iPhone 6 and 6 Plus. Definitely a UIKit bug regarding screen sizes/resolution/graphic context/scale factor. — Can Poyrazoğlu, Oct 01 '14 at 17:24
I don't see this bug if I turn off scaling in the simulator (by providing 6 and 6+ launch images). Looks like a bug in the way iOS scales up apps to fit the screen. — Brian Nickel, Oct 01 '14 at 17:33

Jan-Dawid Roodt · Answer 1 · 2015-05-04T03:41:35.743

13

Do you NEED it to draw after the screen updates? because I'm using:

[view drawViewHierarchyInRect:view.bounds afterScreenUpdates:NO];

and it seems to work fine on iOS7 and iOS8. I imagine this isn't a great solution for capturing images regularly (like multiple times a second) but it seems to work for a once off blur.

edited May 04 '15 at 03:41

answered Oct 22 '14 at 03:21

Jan-Dawid Roodt

489
5
13

score 5 · Answer 2 · answered Oct 01 '14 at 20:33

5

You have to provide @3x launch images for the 6 and 6 plus. The 6 being scaled at 750x1334, and the 6 plus image being scaled at 1242x2208.

answered Oct 01 '14 at 20:33

Zach

153
1
6

This does indeed fix the issue. – mbogh Feb 24 '15 at 10:07

score 2 · Answer 3 · answered Nov 21 '14 at 18:39

Even it looks like bug in API, you can call drawViewHierarchyInRect with afterScreenUpdates set to NO to build snapshot AFTER screen updates if you use cunstruction like this:

typedef void (^CompletionHandlerWithId)(id result);

-(void)imageContaining:(CGRect)rect afterScreenUpdates:(bool)afterScreenUpdates opaque:(BOOL)opaque completion:(CompletionHandlerWithId)completion
{
    bool success __block;
    UIImage *snapshotImage __block = nil;

    CompletionHandler block = ^{

        // Create the image
        UIGraphicsBeginImageContextWithOptions(self.bounds.size, opaque, [[UIScreen mainScreen] scale]);

        success = [self drawViewHierarchyInRect:self.bounds afterScreenUpdates:NO];

        if (success)
        {
            snapshotImage = UIGraphicsGetImageFromCurrentImageContext();

            CGImageRef imageRef = CGImageCreateWithImageInRect(
                                   [snapshotImage CGImage],
                                   CGRectMake(
                                          snapshotImage.scale*rect.origin.x,
                                          snapshotImage.scale*rect.origin.y,
                                          snapshotImage.scale*rect.size.width,
                                          snapshotImage.scale*rect.size.height));

            // or use the UIImage wherever you like
            snapshotImage = [UIImage imageWithCGImage:imageRef scale:snapshotImage.scale orientation:UIImageOrientationUp];

            CGImageRelease(imageRef);
        }

        UIGraphicsEndImageContext();

        if (completion)
        {
            if (! success)
            {
                NSLog(@"Error: [UIView drawViewHierarchyInRect] failed on %@", self);

                (completion)(nil);
            }
            else
            {
                NSLog(@"Success: [UIView drawViewHierarchyInRect] on %@", self);

                (completion)(snapshotImage);
            }
        }
    };

    if (afterScreenUpdates)

        [CATransaction setCompletionBlock:^{
            (block)();
        }];

    else

        (block)();
}

score 1 · Answer 4 · answered Nov 17 '14 at 07:11

This bug also exists when you run on an iPad2 running iOS7.

Fix: set afterScreenUpdates: to NO

My app has some moving UIButtons, so I don't allow the blur transition until after the movement has stopped. As far as I have found so far, there is no difference in YES or NO.

score 0 · Accepted Answer · answered Sep 22 '15 at 02:33

0

Appears to be fixed in iOS9 / XCODE 7 builds

answered Sep 22 '15 at 02:33

glued

2,579
1
25
40

score -1 · Answer 6 · edited May 23 '17 at 12:09

I found a solution for me to solve this problem.

I add @3x launch images to my project. And choose launch Screen file to "Main". This will make app run at original resolution, smaller bounds when run at iphone6, but not glitch when calling drawViewHierarchyInRect. Like this.

Then, scale my view to fullscreen when viewDidLoad.

- (void)viewDidLoad{ 
       [super viewDidLoad];
       UIScreen *mainScreen = [UIScreen mainScreen];
       CGRect tempFrame=mainScreen.bounds;
       double aspect=tempFrame.size.width/320;
       self.view.transform = CGAffineTransformScale(CGAffineTransformIdentity, aspect, aspect);
}

Hope helpful :)

iOS8 scale glitch when calling drawViewHierarchyInRect afterScreenUpdates:YES

6 Answers6

Linked