Static方法buildExpression要求DescriptionInputView遵循AccessibilityRotorContent协议问题排查

错误原因 #

这个报错本质是SwiftUI视图类型推断或无障碍转子（AccessibilityRotor）相关的类型约束冲突，常见触发场景：

• 在ForEach结合switch语句使用时，不同case返回的视图未保持完全一致的类型，SwiftUI在尝试统一视图类型的过程中触发了隐晦的协议约束校验失败。
• 自定义视图的参数传递（比如@ObservedObject类型的viewModel）导致SwiftUI无法生成符合AccessibilityRotorContent协议的视图构建表达式。

解决方案 #

1. 统一switch case的视图返回类型 #

给每个case的视图包裹AnyView，强制统一返回类型：

ForEach(items, id: \.id) { item in
    switch item.getType().rawValue {
    case "TEXT":
        AnyView(DescriptionInputView(
            viewModel: viewModel, title: item.title,
            audioRequired: item.audioRequired,
            videoRequired: item.videoRequired,
            imageRequired: item.imageRequired,
            documentRequired: item.documentRequired
        ))
    case "OTHER_TYPE":
        AnyView(OtherCustomView())
    default:
        AnyView(EmptyView())
    }
}

2. 显式声明自定义视图的构造器 #

给DescriptionInputView添加显式构造器，消除SwiftUI类型推断的模糊性：

struct DescriptionInputView: View {
    @ObservedObject var viewModel: ContentViewModel
    @State private var description: String = ""
    var title: String
    var audioRequired: Bool
    var videoRequired: Bool
    var imageRequired: Bool
    var documentRequired: Bool

    // 显式构造器
    init(viewModel: ContentViewModel, title: String, audioRequired: Bool, videoRequired: Bool, imageRequired: Bool, documentRequired: Bool) {
        self.viewModel = viewModel
        self.title = title
        self.audioRequired = audioRequired
        self.videoRequired = videoRequired
        self.imageRequired = imageRequired
        self.documentRequired = documentRequired
    }

    var body: some View {
        // 原有body代码不变
    }
}

3. 检查子视图的类型一致性 #

如果AttachmentView存在类型冲突或不符合View协议的问题，也会传递到父视图引发报错，确保AttachmentView是标准的SwiftUI视图实现。

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