The earlier entry said only "suspect what the test does not control".
Having now found it, the specifics are worth more than the warning.
State leaks between UI tests because @AppStorage is UserDefaults and the
simulator keeps them for days; the fix is a debug hook writing to the
normal domain, because launch arguments land in NSArgumentDomain and
outrank the app, making settings unchangeable rather than merely
predictable. Elements below the fold of a lazy container genuinely do not
exist, which reads exactly like a bug. Both cost a full evening.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
TomUviandClaude Opus 5
463f45cacb