解析「No visible @interface for xxxxxx」错误的根本原因（含AVCamera适配场景）

Hey there! Let’s dig into the universal root causes behind that frustrating "No visible @interface for [Class]" error in Objective-C—since you’re working with a legacy 2014 project that’s gone through dozens of updates, understanding the core issues will help you fix not just your current AVCapture problem, but the other similar errors in your codebase too.

This error pops up when the compiler can’t find a declared method (or property) in the public interface of the class you’re interacting with. Here are the most common scenarios:

• Mismatched Object Type vs. Declared Type
  This is exactly what’s happening in your AVCapture code. You swapped from AVCaptureStillImageOutput (which has the setOutputSettings: method) to AVCapturePhotoOutput, but the new class doesn’t expose this method in its public interface. The compiler checks the declared type of stillImageOutput (now AVCapturePhotoOutput) and can’t find the method you’re trying to call.
  Generically, this happens whenever you:

  • Assign an instance of a different class to a variable (e.g., storing a UIButton in a UILabel* variable) and call methods unique to the original class
  • Refactor code to use a new class but forget to update method calls to match the new API

• Missing or Outdated Header Imports
  If you haven’t imported the header file for the class you’re using, the compiler has no idea what methods/properties it has. For example, if you’re using AVFoundation classes but forgot to add #import <AVFoundation/AVFoundation.h> to your file, the compiler won’t recognize AVCapturePhotoOutput’s interface at all.
  This also applies to outdated headers: if your project uses old framework versions or custom headers that haven’t been updated to include new methods, the compiler will act like those methods don’t exist.

• Private or Undeclared Methods
  If you’re trying to call a private method (one not listed in the class’s public header), the compiler will throw this error because it can’t see the method in the visible interface. For custom classes, this happens if you define a method only in the .m file (not in the .h header) and try to call it from another class.

• Deprecation & API Replacement
  Legacy projects like yours are prone to this. Apple regularly deprecates old classes and replaces them with new ones that have different APIs. AVCaptureStillImageOutput was deprecated in iOS 10 in favor of AVCapturePhotoOutput, which uses a completely different workflow for setting output settings (you’ll need to use AVCapturePhotoSettings instead of setOutputSettings:).
  Other examples include switching from UIWebView to WKWebView—the new class doesn’t have all the same methods as the old one.

• Typos or Method Signature Mismatches
  A simple typo in the method name (e.g., setOutputSetting: instead of setOutputSettings:) or a mismatch in parameter types (e.g., passing a NSString* when the method expects an NSDictionary*) will make the compiler think the method doesn’t exist in the class’s interface.

Your two additional "No visible @interface" errors and the "No known class" error likely tie back to these same causes:

• "No known class" usually means the class’s header isn’t imported, or the class was renamed/removed in a framework update.
• The other interface errors are probably mismatched types, missing imports, or deprecated method calls.

To fix any instance of this error:

1. Confirm the actual type of the object you’re working with (not just the declared variable type)
2. Verify you’ve imported the correct, up-to-date header for the class
3. Check Apple’s official docs (for system classes) to confirm the method exists on the class you’re using
4. Double-check for typos in method names and parameter types
5. Look for deprecation warnings—if the class/method is marked deprecated, you’ll need to switch to the replacement API

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