You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is correct behavior because the protocol's property isn't @objc. That is, someone else could implement the protocol and subclass NSObject without exposing the property to Objective-C. You can make the protocol @objc to fix this.
Leaving open to potentially improve the error message:
Fatal error: Could not extract a String from KeyPath Swift.WritableKeyPath<main.C, Swift.Bool>: file /Volumes/Data/swift-public/swift/stdlib/public/SDK/Foundation/NSObject.swift, line 91
Additional Detail from JIRA
md5: 1848302fc9a5554dbe3251cbc7003e87
Issue Description:
It looks like you can not observe NSObjects with protocols, even if the underlying class can be observed directly.
This looks different than the other related bugs I've found in the tracker, but I'm not sure.
The text was updated successfully, but these errors were encountered: