shouldChangeTextIn越界崩溃：如何添加范围有效性检查？

Absolutely! This is a super common edge case when dealing with text input and tab switching—let’s break down how to fix it properly.

Why the Crash Happens #

When you switch tabs quickly while text is still updating, the text object (or even the text field/view itself) might no longer be tied to the active tab. The NSRange you’re using was calculated based on the old text state, but by the time replaceCharactersInRange: runs, the current text length could have changed, or the text field might belong to an inactive tab that’s no longer in the view hierarchy—leading to an out-of-bounds range error.

Adding Safety Checks in shouldChangeTextInRange: #

You absolutely can add validation steps to prevent this crash. Here’s how to implement them properly:

1. Validate the Current Text and Range #

First, make sure you’re working with a valid text string, and that the provided NSRange falls within the bounds of that string.

2. Check if the Text Field/View Belongs to the Active Tab #

Since the crash happens when switching tabs, we need to ensure we’re only modifying text for controls in the currently selected tab.

Example Code (Swift) #

func textField(_ textField: UITextField, shouldChangeCharactersIn range: NSRange, replacementString string: String) -> Bool {
    // Fallback to empty string if text is nil to avoid nil errors
    guard let currentText = textField.text ?? "" else {
        return false
    }
    
    // Validate the range is within the bounds of the current text
    guard range.location >= 0, 
          range.location + range.length <= currentText.count else {
        print("Invalid range detected—skipping text update")
        return false
    }
    
    // Make sure we're only modifying text for the active tab's field
    guard isTextFieldInActiveTab(textField) else {
        print("Text field belongs to inactive tab—skipping update")
        return false
    }
    
    // Proceed with your text modification logic
    let updatedText = NSMutableString(string: currentText)
    updatedText.replaceCharacters(in: range, with: string)
    
    // Update your 3 labels here
    updateLabels(with: updatedText as String)
    
    return true
}

// Helper to check if the text field is part of the currently selected tab
private func isTextFieldInActiveTab(_ textField: UITextField) -> Bool {
    guard let activeTabView = tabBarController?.selectedViewController?.view else {
        return false
    }
    return activeTabView.contains(textField)
}

Example Code (Objective-C) #

- (BOOL)textField:(UITextField *)textField shouldChangeCharactersInRange:(NSRange)range replacementString:(NSString *)string {
    NSString *currentText = textField.text ?: @"";
    
    // Validate the range is within the bounds of the current text
    if (range.location < 0 || (range.location + range.length) > currentText.length) {
        NSLog(@"Invalid range detected—aborting text update");
        return NO;
    }
    
    // Ensure we're only modifying text for the active tab's field
    if (![self isTextFieldInActiveTab:textField]) {
        NSLog(@"Text field belongs to inactive tab—skipping update");
        return NO;
    }
    
    // Proceed with text modification
    NSMutableString *updatedText = [NSMutableString stringWithString:currentText];
    [updatedText replaceCharactersInRange:range withString:string];
    
    // Update your 3 labels here
    [self updateLabelsWithText:updatedText];
    
    return YES;
}

- (BOOL)isTextFieldInActiveTab:(UITextField *)textField {
    UIView *activeTabView = self.tabBarController.selectedViewController.view;
    return [activeTabView contains:textField];
}

Final Notes #

These checks act as a safety net—they’ll catch invalid ranges and skip text updates for inactive tabs entirely, eliminating the NSRangeException you’re seeing. You can adjust the helper method for checking active tabs to match your specific tab bar implementation, but the core validation logic stays the same.

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