[deleted]

Xcode 26.4.1 (17E202), released yesterday (Apr 16) fixed it for me. 🙌 No mention in the release notes, but in light testing I confirmed I can now paste in the simulator.

Welp, I just pulled TipKit from my app as this is still not fixed in iOS 26.5 (23F5043k). I was only using it for one tip, so not a big loss. Still, it’s a shame—TipKit has a lot of potential, but there are too many limitations and paper cuts like this one.

On a more positive note, the feedback I filed now shows “More than 10” similar reports. Maybe that helps its chances of getting fixed? 🤷

@SLB13 , unfortunately, I never found the root cause. Once I saw it repro in Shortcuts, I stopped digging as it seems like a framework issue. The only workaround I’ve found is to avoid the zoom transition entirely and use a standard navigation push instead. That said, my app’s main screen is built around the zoom transition, so that’s not a great option for me. Just hoping it gets fixed soon, but it’s not looking promising as it still repros in the latest beta: iOS 26.5 (23F5043k)

One more thing… I recently heard about this from a friend who was part of an effort to form an Apple developer union—free trial support was one of their core gripes. Wired, 2018: Fed Up With Apple’s Policies, App Developers Form a ‘Union’ —Lauren Goode Relevant excerpt Apple has given developers some ability to offer free app trials, for time periods ranging from three days up to a whole year. But a free trial can only accompany a subscription app. This means that when opting to get the free trial, the customer has to authorize Apple to automatically charge them when a trial ends, developers say. The ideal situation, they say, would allow them to offer free trials for all apps, at lengths they determine, and without barriers that might make people shy away from trying their apps. Eight years later, that “without barriers” line still hits.

It’s been two months since I posted this and there’s still no official response from Apple, so I wanted to bump the thread. There are a few comments here now from others trying to figure out the same thing, so this doesn’t seem like an isolated question. I’m just trying to understand what Apple expects devs to ship here. Is the $0 IAP workaround still the right approach, or is there a better path now?

@DTS Engineer , here you go… Passwords: FB22216684 Messages: FB22216811 Calculator: FB22216904 Thanks for the workaround info.

Hey @DTS Engineer Travis, A workaround would be helpful, but ideally this would be fixed in the framework so it benefits all affected apps, not just mine. I've already had to implement quite a few workarounds with iOS 26. Looking at my open feedbacks and posts here, several remain unresolved. I have workarounds for most, but could clean up my code if they weren't necessary.

I really need some kind of alert system for posts like this so I don’t waste 20 minutes trying to fix something I can’t fix. ChatGPT (eventually) led me to this thread…thank goodness.

Here’s an even simpler repro sample that removes List and .searchable entirely: struct ContentView: View { var body: some View { NavigationStack { Text("Hello, World!") .navigationTitle("Toolbar Repro") .toolbar { ToolbarItem(placement: .bottomBar) { Menu { Button("Action 1") { } Button("Action 2") { } } label: { Label("Actions", systemImage: "ellipsis.circle") } } } } } }

Also confirmed this is still broken in iOS 26.3 (23D127). My feedback is FB21078443 filed Nov 2025. If anyone can’t repro it, here’s a minimal example. Tap a color, then swipe back from the left edge—the source view will disappear after the transition. Easier to repro on physical device, but also possible in sim with a solid swipe. import SwiftUI struct ContentView: View { @Namespace private var namespace private let colors: [Color] = [.red, .blue] var body: some View { NavigationStack { VStack(spacing: 16) { ForEach(colors.indices, id: \.self) { index in NavigationLink(value: index) { RoundedRectangle(cornerRadius: 16) .fill(colors[index]) .frame(maxWidth: .infinity, minHeight: 200, maxHeight: 200) .matchedTransitionSource(id: index, in: namespace) } .buttonStyle(.plain) } } .padding(20) .navigationTitle("Zoom Transition Issue") .navigationSubtitle("Tap card, then swipe back from left edge") .navigationDestination(for: Int.self) { index in Rectangle() .fill(colors[index]) .ignoresSafeArea() .navigationTransition(.zoom(sourceID: index, in: namespace)) } Spacer() } } }

Still an issue in iOS 26.3 public release. Updated FB21078443 with simplified minimal repro.

Looping back to mark this as resolved. Not sure when it was fixed, but it doesn't repro on iOS 26.2.1 (23C71).

@DTS Engineer Thanks for the suggestion. I did try hiding the system back button and replacing it with a custom toolbar button. However, that disables the left-edge swipe gesture, which felt like a worse tradeoff. Most people expect swipe-to-go-back, so a mismatched toolbar button seemed like the lesser issue. Unless there’s a way to preserve the swipe gesture while using a custom back button, I’ll just hope for a fix.