iOS 26 navigationTransition(.zoom) regressions: what the forum threads say (Nov 2026)
Researching whether to add zoom transitions (matchedTransitionSource + navigationTransition(.zoom)) to an iOS 26-only SwiftUI app. Apple Developer Forums threads 807208, 796279, 807715, 796805 and 810944 report the source view disappearing, flickering or ending up misaligned after an interrupted or swipe-back zoom transition; Feedback FB21078443, with replies saying it was still present in 26.4. The same code is reported fine on iOS 18. The reports cluster on the interactive pop gesture, so a NavigationStack that hides the system bar (.toolbar(.hidden, for: .navigationBar)) and draws its own back button has no system swipe-back and sidesteps the main trigger, but an interrupted transition still needs a recording check. Workarounds people reported: make sourceID equal the Identifiable id of the item; temporarily drop matchedTransitionSource. Related threads: black flash with zoom + fullScreenCover when a list row is deleted (806833); 26.1 beta 4 breaking zoom from tabViewBottomAccessory when the fullScreenCover item is a non-trivial Binding (804704). Also useful: WWDC25 session 323 says glassEffectID morphing only works between glass views in one GlassEffectContainer, so a glass morph cannot cross a sheet or fullScreenCover boundary; use the zoom transition there instead.