Xcode中NSEException与signal SIGABRT报错排查求助

Hey there! Let's walk through how to track down that frustrating crash you're facing. SIGABRT errors with libc++abi.dylib exceptions almost always link to broken Interface Builder (IB) connections or mismatched array handling—let's break down the steps to fix this:

1. Verify Outlet Collection Integrity #

• Open your Storyboard/XIB, select your ViewController, and switch to the Connections Inspector (the arrow icon in the right sidebar).
• Check the labels and buttons Outlet Collections:
  • Make sure none of the connections have a red exclamation mark (this means a connection is broken, like a deleted control or mismatched outlet).
  • Critical: Confirm the number of items in labels matches exactly with buttons. Your code uses the same index to link buttons and labels—if one array is shorter, you'll hit an index-out-of-bounds crash when accessing labels[i].
  • Double-check no controls are accidentally added to the collection multiple times, and all intended controls are included.

2. Validate Tag & Array Order Matching #

• In viewDidLoad, you assign tags starting at 0 based on the order of buttons in the collection—but here's a gotcha: Xcode orders Outlet Collection elements by the order you added them to the collection, not their position on the screen.
• Add these print statements to confirm the array order matches your expected button-label pairing:

  // First, set restorationIdentifiers for each label/button in Identity Inspector
  print("Labels order: \(labels.map { $0.restorationIdentifier ?? "Unnamed Label" })")
  print("Buttons order: \(buttons.map { $0.restorationIdentifier ?? "Unnamed Button" })")
  

  This will show you if the array order aligns with how you want buttons to map to labels.

3. Add Guard Clauses to Prevent Index Out-of-Bounds #

• Your loop uses 0...buttons.count-1, but if labels.count < buttons.count, this will crash when accessing labels[i]. Add an assertion at the start of viewDidLoad to catch this early:

  assert(labels.count == buttons.count, "Labels and Buttons collections must have the same number of elements!")
  

  This will trigger an immediate warning when your app launches if the counts don't match, instead of crashing randomly later.

4. Check for Duplicate IBAction Connections #

• You're using button.addTarget to bind the action programmatically, but if you also manually connected the button_action IBAction to any buttons in Storyboard, this creates duplicate bindings that can cause exceptions.
• In the Connections Inspector, look under the Actions section of ViewController—if button_action appears multiple times, delete the Storyboard-based connections (click the X next to them) since you're handling bindings in code.

5. Dig Into the Full Crash Log #

• The SIGABRT signal is a generic crash indicator—look up in the Xcode console for the actual exception message. For example:
  • Index out of range: Means you're accessing an array index that doesn't exist.
  • unrecognized selector sent to instance: Means a control is trying to call a method that doesn't exist (or a broken action connection).
  • nil while unwrapping Optional value: Means one of your Outlet Collections is nil (no controls bound to it).
• You can also check the Call Stack (in the Debug Navigator) to see exactly which line of code caused the crash—this will point you directly to the problematic line (e.g., labels[i].isHidden = true).

6. Reset IB Connections Entirely #

• Sometimes Xcode's IB cache gets corrupted, even after cleaning the project. Try a full reset:
  1. Delete the @IBOutlet var labels: [UILabel]! and @IBOutlet var buttons: [UIButton]! lines from your code.
  2. Back in Storyboard, select all labels/buttons that were part of the collections, and delete their connections in the Connections Inspector.
  3. Recreate the Outlet Collections: Hold Ctrl and drag from the first label to your ViewController code, select Outlet Collection, name it labels, then add all other labels to it. Repeat the same process for buttons.

Quick Optimization Tip #

Instead of relying on tags (which depend on array order), you can directly find the tapped button's index in the collection—this is more reliable:

@IBAction func button_action(_ sender: UIButton) {
    guard let tappedIndex = buttons.firstIndex(of: sender) else { return }
    
    for (index, label) in labels.enumerated() {
        if index == tappedIndex {
            label.isHidden.toggle()
            if !label.isHidden {
                label.text = "The right text"
            }
        } else {
            label.isHidden = true
        }
    }
}

内容的提问来源于stack exchange，提问作者Lynn Bou Nassif