It looks like the @availability check we apply to the extension that adds an Observable conformance prevents iOS 17+ deployment targets from calling the correct version of access, which leads to errant perception checks.
While I think we probably could merge this as cleanup, I'm not seeing the overload working consistently across projects, so this branch may not fix the underlying behavior just yet.
It looks like the
@availability
check we apply to the extension that adds anObservable
conformance prevents iOS 17+ deployment targets from calling the correct version ofaccess
, which leads to errant perception checks.