onGeometryChange(for:, of:, action:) seems to have a similar issue as GeometryReader

[josh-arnold-1]

Hey team, has anyone noticed that the onGeometryChange(for:, of:, action:) modifier seems to have a similar issue when accessing perceptible state?

Specifically, its totally fine to access our perceptible state inside of the action: block — but if we try to access our perceptible state inside of the first of: closure, we run into a runtime warning about our perception state not being tracked.

myView
    .onGeometryChange(for: Bool.self) { _ in
        return myPerceptible.someValue // <-- this access is untracked
     } action: { _ in
        // do work
     }

With the geometry reader, we can just wrap our view inside of WithPerceptionTracking however, since the of: block returns a generic value, theres no easy way to leverage WithPerceptionTracking to ensure our access to our perceptible properties are tracked.

Does anyone have thoughts on this? Is this a known limitation?

I think it can potentially be solved by just doing something like this, but I'm wondering if we have a better solution.

myView
    .onGeometryChange(for: ...) { geo in
        return geo // just pass through the geometry information
     } action: { geo in
        // access perceptible state here
     }

Thanks!

[prateem]

To add to the original report -- my observation is that even though the access is untracked and triggers the Perception checker, the code inside of the of: block does still run fine / as expected.