Leaks in basic project for iOS 16

[lilidotshi]

Hi there! Wondering if I could get a second set of eyes here for an issue I'm seeing in some pretty basic code. I'm running into an issue where I have a super basic app and I'm running into a ton of <decode: bad range for [$@] got......> errors. I believe I've wrapped everything correctly with WithPerceptionTracking, but I'm still seeing it. Wondering if I could grab any extra eyes.

If I swap to iOS 17 only, and get rid of the WithPerceptionTracking everything is fine, but we still need to support iOS 16. I've seen discussions from a while ago that were resolved, particularly this one, but there was no resolution.

I'm running with Xcode 26 beta 4, on iOS 26 iPhone 16 Plus simulator with TCA version 1.21.0. I've also attached the basic repro.

BigTest.zip

[mbrandonw]

Hi @lilidotshi, good catches! We just released TCA 1.21.1 that fixes this issue.

[lilidotshi]

Wow thanks for the quick fix! Weird question: is this actually an issue? It seems like non-debug builds would still be accessing this value the original way, so wouldn't we see this in prod logs?

[stephencelis]

@lilidotshi The warnings are just debug info to catch missing WithPerceptionTracking views when testing your application. This was just a case of TCA missing a place where that instrumentation needed to take place. There could be others lurking out there that we also need to fix, but to your question, no this shouldn't actually be an issue and none of this logging occurs in release/production builds :)

[lilidotshi]

much thanks!