SharedReader in an @ObservableObject started to emit "Perceptible state was accessed from a view but is not being tracked." since swift-perception updated to 2.0.0

[cabeca]

Hello,

We have several @ObservableObject ( not @Observable ) where we declare a @SharedReader:

@SharedReader(.somethingContext) var somethingContext

We use the publisher property to derive other @Published properties on init, or simply have computed properties for on-demand reading:

@Published var actionVariant: ActionVariant?
init() {
    $somethingContext.publisher.combineLatest($rowModels)
            .map { [weak self] in self?.actionVariant(for: $0, rowModels: $1) }
            .removeDuplicates()
            .assign(to: &$actionVariant)
}

var showInfoBasedOnProperty: Bool {
    somethingContext.hasProperty
}

We use this pattern because we are not ready to use @Observable yet. This was working fine until swift-perception was updated to version 2.0.0.
Now we get a bunch of runtime warnings stating that "Perceptible state was accessed from a view but is not being tracked." This is an example of such view:

 private var emptyExampleView: some View {
        VStack(spacing: 16) {
            if model. showInfoBasedOnProperty {
                Text("Something)
            } else {
                Text("Something else")
            }
        }
    }

If I wrap the view with WithPerceptionTracking I get this warning: "'WithPerceptionTracking' was deprecated in iOS 17: 'WithPerceptionTracking' is no longer needed in iOS 17+." which is expected because our minimum target is iOS 17.

Other than converting all our models that use the SharedReader to @Observable, or pinning the swift-sharing library to exact: "2.5.2" what are my options here?

Thank you for your help.

[mbrandonw]

Other than converting all our models that use the SharedReader to @observable, or pinning the swift-sharing library to exact: "2.5.2" what are my options here?

Hi @cabeca, we are working on a fix right now, but the simplest thing to do is just add an explicit dependency on swift-perception and pin to 1.6.0.

[cabeca]

Thank you for the quick response!

[mbrandonw]

We think we have a fix. Can you point Perception to perception-2-fixes, and if you are using TCA point it to perception-2-fixes too. Does that resolve the issues you are seeing?

[cabeca]

I have updated my Package.swift with

        .package(url: "https://github.com/pointfreeco/swift-perception", from: "2.0.1"),
        .package(url: "https://github.com/pointfreeco/swift-sharing", from: "2.6.0"),

I did a quick run now, and the issues are gone. Thank you for looking into it so quickly. Will you release a swift-sharing version 2.6.1 that depends on swift-perception 2.0.1 soon?

[mbrandonw]

Hi @cabeca, no we won't do that because that will make our packages unnecessarily restrictive. There may be people out there that want to use Sharing 2.6 with Perception 1.x. But you can always add an explicit dependency on Perception that pins to 2.0.1+ if you want.