This is exactly what I did for one of my apps when I moved the codebase from Objective-C to Swift and SwiftUI. Zero issues. I'm not sure the OP has explained their issue very well. As I said in my reply above, if the OP has uploaded a new binary and it's 'turned into a new app' then they have to have created a new app in App Store Connect otherwise Xcode will not upload the binary.

The email says: "If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect." That suggests we have to submit updates to our apps before January 31st. I have a life outside of writing apps that no one buys, and don't really have time to do this. If it were a simple matter of updating the ratings for the versions currently on the App Store, no one would have an issue. This has been handled extremely badly by Apple.

Well, yeah, obvs. I meant that this isn't the main place you chat about bugs, and posting something here isn't really going to be on anyone's radar (pun intended) unless it's raised 😇

Nope. I don't use AI when there are perfectly good humans available. Besides, you've used AI on this and told me there are several issues but not actually provided any fixes, which is really rather unhelpful.

Fair enough. I do think this version of iOS has been rushed. Now that they've naming OSes after the year (iOS 26, 27, 28...) they're definitely going to push something out each year. I miss the days when we got an OS when it was ready.

iOS 26.1 has been released, so please check that the issue is no longer present in the released version. If it is, please raise a feedback report at: https://feedbackassistant.apple.com/ then post the FB number here. Secondly, don't hijack someone else's thread. Your issue is unrelated to the original post, and you should create your own thread instead.

Doesn't sound like you understand that these forums aren't here for advertising. And they aren't here for insults either.

@Tinn_Vision That's the sort of information you should put in the original post so people don't have to ask you for it. You put a giant red X to show that it doesn't work on visionOS, but then didn't say_ why i_t doesn't work.

Glad you've fixed it. I always find it easier to log stuff out to see whether I'm missing some other state. With regards to debugging and logging: 1. Make sure you pair a watchOS Simulator with an iOS Simulator in the "Devices and Simulators" window. 2. Run your iOS target on the iOS Simulator. 3. Run your watchOS target on the watchOS Simulator that's paired to that iOS Simulator. 4. The output should be displayed in the console window as usual.

The Apple Support Community will bounce it back here because it's about the iPadOS 26 beta.

Claude doesn't have to direct you anywhere other than not here. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. We don't advertise apps on here; that's not what these forums are for. Go to any Mac/iPhone app related forums.

You can raise a bug at https://feedbackassistant.apple.com/

Yeah, it's a different form of .sheet, as the DTS Engineer noted on line 23 of their fix: .sheet(item: $selectedTransaction) { transaction in. But I was right :) You do need to send the variable in.

You might want to update your feedback report to include that it seems like this was blocked because it's for c u e, which is rude when read out loud.

Yeah, even if it's just there during the beta period for a new major release, i.e. iOS 27, 27, 28 not 26.0.1 etc.