Quick description / drawback
After I push from a tab bar root navigation controller to a brand new display, the navigation bar again button jumps (strikes misplaced) briefly in the course of the push animation after which snaps again. That is constant for the primary push from the tab root. If I push deeper (improve stack depth) the leap doesn’t occur. This doesn’t happen on iOS 18. Console exhibits no warnings which are constant sufficient to detect any patterns.
It looks as if a battle with iOS 26’s new Liquid Glass navigation animations and I’ve the compatibility flag on on Data.plist (UIDesignRequiresCompatibility set to True). I’m questioning if there’s a answer or workaround that preserves the outdated design (till Liquid Glass adoption) or in any other case explains methods to keep away from the leap, if doable.
What I’ve already tried
Checked Xcode console for warnings — none related.
Verified conduct on Simulator and actual units.
Tried setting navigationItem.backButtonDisplayMode / setting express (empty) again button title to take away label structure modifications. No enchancment.
Thought of eradicating UIRequiresDesignCompatibility (which makes app undertake Liquid Glass) — that seems to keep away from the mismatch, however I have to know if there’s a technique to hold compatibility mode and keep away from this leap.
Tried guaranteeing constant largeTitleDisplayMode on root/element (no impact).
Questions
Is that this a identified iOS 26 beta bug / anticipated conduct when UIRequiresDesignCompatibility is ready?
Is there a advisable workaround that preserves the compatibility (outdated look) with out the back-button leap?
Are there UINavigationBarAppearance or transition APIs I can override to forestall the system trying the brand new “merge” animation whereas operating in compatibility mode?
Further particulars
App makes use of customized subclasses for tab and navigation controllers; the conduct reproduces with plain UINavigationController too.
Just one fundamental tab within the app (so it’s all the time root-from-tab state of affairs).
No third-party structure engines are concerned.
Thanks — I can paste logs, display recordings, or a pattern challenge if that helps. Any steering appreciated.