自定义MKAnnotationView遇reuseIdentifier只读错误，求初始化及required init解析

Hey there! Let's tackle your two questions step by step:

First, let's break down why you're seeing that error: reuseIdentifier is a get-only property on MKAnnotationView—this means you can read its value, but you can't directly assign to it after the object is initialized.

Even better, you don't need to set it at all! When you call super.init(annotation: annotation, reuseIdentifier: reuseIdentifier), the parent class (MKAnnotationView) already handles assigning both the annotation and reuseIdentifier values to their respective properties. Your manual assignments are redundant, and the reuseIdentifier one is invalid because of its read-only status.

Here's your corrected initialization code:

class JumpSpotAnnotationView: MKAnnotationView {
    required init?(coder aDecoder: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }
    
    override init(annotation: MKAnnotation?, reuseIdentifier: String?) {
        super.init(annotation: annotation, reuseIdentifier: reuseIdentifier)
        // Add your custom setup code here!
        // Example: Set a custom marker image
        // self.image = UIImage(named: "jump-spot-icon")
        // Or enable callout bubbles for the annotation
        // self.canShowCallout = true
    }
}

The required keyword here enforces that every subclass of your JumpSpotAnnotationView must implement this initializer—but more importantly, it's a requirement inherited from UIKit's parent classes.

MKAnnotationView traces back to UIView, which conforms to the NSCoding protocol. This protocol handles encoding/decoding objects, like when loading a view from a Storyboard or XIB file. The system uses init(coder:) to reconstruct the object from its saved, encoded data.

• If you never plan to load your annotation view from a Storyboard/XIB, keeping fatalError("init(coder:) has not been implemented") is totally acceptable. It acts as a safety net: if someone accidentally tries to create your view via decoding, the app crashes immediately with a clear error, making it easy to fix the issue.
• If you need to support Storyboard/XIB loading later, replace the fatal error with actual initialization logic, like this:

  required init?(coder aDecoder: NSCoder) {
      super.init(coder: aDecoder)
      // Add custom setup for decoded views here
      // e.g., self.image = UIImage(named: "jump-spot-icon")
  }
  

In short, required ensures your class follows the initialization rules of its parent classes, so the system can reliably create instances of your class no matter which initialization path is used.

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