渲染UIView为图片时应用崩溃，遇CALayerInvalidGeometry错误求解决

Hey there, let's dig into this crash you're facing! The error CALayer bounds contains NaN: [0 0; 1.25987e-321 nan] tells us exactly what's going wrong: your UIView's layer has invalid bounds values (specifically a NaN height), and the system can't render a layer with non-numeric dimensions. Looking at the layer info, your view's frame and bounds are both (0 0; 0 0)—that's a red flag too, since you can't render a zero-sized view properly.

Here are the steps to fix this: #

1. Add a Pre-Check for Valid Bounds

First, we'll add a safety check before attempting to render the image. This will catch invalid dimensions early and prevent the crash:

- (UIImage*)imageOfSelf {
    CGRect viewBounds = self.bounds;
    
    // Check if bounds are valid (not NaN/Infinite, and have positive size)
    if (isnan(viewBounds.size.width) || isnan(viewBounds.size.height) ||
        isinf(viewBounds.size.width) || isinf(viewBounds.size.height) ||
        viewBounds.size.width <= 0 || viewBounds.size.height <= 0) {
        NSLog(@"Skipping render: Invalid view bounds - %@", NSStringFromCGRect(viewBounds));
        return nil; // Or return a placeholder image if needed
    }
    
    UIGraphicsBeginImageContextWithOptions(viewBounds.size, NO, 0);
    [self.layer renderInContext:UIGraphicsGetCurrentContext()];
    UIImage *imageOfSelf = UIGraphicsGetImageFromCurrentImageContext();
    UIGraphicsEndImageContext();
    return imageOfSelf;
}

This check will log the problematic bounds so you can track down which view is causing the issue, and avoid the crash entirely.

2. Find the Root Cause of Invalid Bounds

The real fix is to figure out why your view has invalid bounds in the first place. Here are things to check:

• Constraint Issues: Do you have conflicting auto-layout constraints on this view? Or are you using constraints that depend on a value that's not properly initialized (like a NaN from a division by zero)?
• Manual Frame/Bounds Setup: Are you setting the view's frame/bounds manually somewhere with a calculation that could result in NaN? Double-check any math operations (like dividing by a value that might be zero).
• Timing of Render Call: Are you calling imageOfSelf too early, before the view has finished laying out its subviews? For example, calling it in viewDidLoad instead of viewDidLayoutSubviews (when the view's final frame is determined) can lead to zero or invalid bounds.

3. Use a More Reliable Rendering Method (iOS 10+)

Apple introduced drawHierarchyInRect:afterScreenUpdates: in iOS 10 as a more robust alternative to renderInContext:. It handles complex layers (like WKWebView, or views with shadows/effects) better and is less likely to crash with edge cases:

- (UIImage*)imageOfSelf {
    CGRect viewBounds = self.bounds;
    
    if (isnan(viewBounds.size.width) || isnan(viewBounds.size.height) ||
        viewBounds.size.width <= 0 || viewBounds.size.height <= 0) {
        NSLog(@"Skipping render: Invalid view bounds - %@", NSStringFromCGRect(viewBounds));
        return nil;
    }
    
    UIGraphicsBeginImageContextWithOptions(viewBounds.size, NO, 0);
    [self drawHierarchyInRect:viewBounds afterScreenUpdates:NO];
    // Set `afterScreenUpdates` to YES if you need to capture the latest UI changes
    UIImage *imageOfSelf = UIGraphicsGetImageFromCurrentImageContext();
    UIGraphicsEndImageContext();
    return imageOfSelf;
}

内容的提问来源于stack exchange，提问作者Kishore Suthar