Xcode问题：设置自定义类后子视图控制器无法正常加载

Hey there, let's break down the most common reasons why your child view controller stops showing up after assigning a custom class—this is a super common pitfall when working with container views for the first time!

1. You’re missing a proper initializer in your custom class #

If you’ve overridden initializers in your child VC, you might be breaking the Storyboard instantiation process. Container views rely on the init?(coder: NSCoder) initializer (since they’re loaded from Storyboard), so you must call the superclass initializer here.

For example, this will cause issues:

class MyChildVC: UIViewController {
    required init?(coder: NSCoder) {
        // ❌ No call to super.init(coder:)
        setupCustomStuff()
    }
}

Fix it by always calling the super initializer first:

class MyChildVC: UIViewController {
    required init?(coder: NSCoder) {
        super.init(coder: coder) // ✅ Critical line
        setupCustomStuff()
    }
}

If you also need a custom init() method, make sure to handle both cases:

class MyChildVC: UIViewController {
    override init(nibName nibNameOrNil: String?, bundle nibBundleOrNil: Bundle?) {
        super.init(nibName: nibNameOrNil, bundle: nibBundleOrNil)
        setupCustomStuff()
    }
    
    required init?(coder: NSCoder) {
        super.init(coder: coder)
        setupCustomStuff()
    }
    
    private func setupCustomStuff() {
        // Your custom setup code here
    }
}

2. Incorrect Storyboard identity settings #

Double-check the Identity Inspector (the third tab in the right panel) for your child view controller:

• Ensure the Class field is set to your custom class (typos happen easily!)
• Make sure the Module dropdown is set to your app’s module (not None). This is especially important if you’re using CocoaPods, frameworks, or multiple modules in your project—Xcode sometimes defaults to None, which prevents it from finding your class.

3. Accidental view hiding or broken constraints in your custom class #

Sometimes the child VC is loading, but its view isn’t visible. Check:

• Did you set view.isHidden = true anywhere in your custom class (like viewDidLoad or viewWillAppear)?
• Use Xcode’s Debug View Hierarchy (the button that looks like three squares in the debug bar) to inspect if the child view exists but is off-screen or hidden. Embed segues should automatically add constraints to pin the child’s view to the container, but if you modified these constraints manually, they might be broken.

4. Wrong segue type #

Confirm that the connection between your container view and child VC is an Embed segue. If you accidentally created a different segue type (like Show or Present), it won’t embed the child VC into the container—instead, it might present it modally or push it, which won’t show up in your container.

5. Xcode cache glitches #

Xcode can be finicky with cached data. Try these steps to rule out cache issues:

• Clean the build folder: Press Cmd + Shift + K
• Delete derived data: Go to Xcode > Settings > Locations > Derived Data and click the arrow to open the folder, then delete its contents
• Restart Xcode entirely, then rebuild and run your project

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