How to use Perception 2.0

[buscarini]

We are using TCA with Perception fixed to 1.3.4, and we want to migrate to the latest version of Perception. However, there is a failing test that uses snapshot testing to record a sheet with a binding. No matter how many WithPerceptionTracking I use, the test still fails. I have tried to move from supporting iOS 16 to iOS 17, removing all uses of WithPerceptionTracking, but now I get thousands of warnings like "Perceptible state was accessed from a view but is not being tracked.". If I add WithPerceptionTracking then I get deprecation warnings. What should I do?

[mbrandonw]

Hi @buscarini, everything you are describing is not how I would expect Perception to behave, and so can you provide a minimal project that demonstrates the problems you are seeing so that we can investigate?

[buscarini]

I managed to solve this. The issue, at least when using Perception, is that I had an @ObservableState State, and the sheet was presenting a struct that also had the @ObservableState applied to it:

`@Reducer
struct PresenterFeature {
@ObservableState
struct TextInSheet: Equatable, Hashable, Sendable, Identifiable {
var string: String

	var id: String {
		string
	}
}

@ObservableState
struct State {
	public var content: [String]
	@Presents var sheet: TextInSheet?
}

enum Action: Equatable, Sendable {
	case present(String)
	case close
	case sheet(TextInSheet?)
}

var body: some ReducerOf<Self> {
	Reduce { state, action in
		switch action {
			case let .present(string):
				state.sheet = TextInSheet(string: string)
			case .close:
				state.sheet = nil
			case let .sheet(sheet):
				state.sheet = sheet
		}
		
		return .none
	}
}

}`

I guess this is expected but it would be nice to have this included in the Perception warning; I checked all the fixes there and they didn't work.

I'm not sure if this might be the issue I'm seeing when using iOS 17. In that case it would be nice to adjust the warning, because suggesting to add WithPerceptionTracking when it's deprecated doesn't help.