I was told the change in behavior for Catalyst is by design. To me, since it worked before and still works this way on the iPad, this is a regression.

100% agree there needs to be a way to disable this. Having it be automatic with no way to disable it can break more complex UIs and operates under the assumption that it is a better approach, which it may not be for a given app. It also has some unwanted effects with Catalyst apps, such as forcing a title bar/toolbar at the top of the window containing the tabs from the tab view, even if the app wants to hide the titlebar. Again, I think it is an erroneous assumption that every app should want this and there needs to be an opt out. The accepted solution does not accomplish this. I'm not sure why it was marked as such.

A quick update. This is caused by the new tab bar for iPadOS. If you have a complicated app that uses UITabBarController in multiple ways, you can end up with a title bar with unwanted tabs that completely breaks your UI. There does not seem to be a way to disable this behavior, which I wish Apple would implements ASAP.

100% agree the current implementation seems half-baked, and that's being generous. It also doesn't fit with some designs so to effectively remove existing behavior in favor for one that isn't workable seems silly. It also breaks some behavior in Catalyst, even though it should not change anything on that side. Not having an opt-out is extremely frustrating and the Feedback system has shown itself to be woefully inadequate in getting things fixed. At the very least an opt-out option allows developers time to figure out how to rework their apps to integrate it properly while still being able to take advantage of other features in iPadOS 18. This is just yet another thing that has me losing faith in Apple and makes me question on whether its a worthwhile platform for future projects.

I went over everything again and noticed that my developer Team ID was prepended to the app's bundle id for the denial entry in swcutil_show.txt. The documentation (https://developer.apple.com/documentation/xcode/supporting-associated-domains) says the appIDs entry should be in the form of .. I'd assumed Application Identifier Prefix was the Apple ID of the app as I've seen these used interchangeably before. Anyway, I added the Team ID as a prefix and all is working. Not sure if this is an error in the documentation or if app's Apple ID is used in production. As a hedge I added both variants (prefixed by Team ID and prefixed by App ID) to the appIDs entry.

I filed a feedback (FB14293963) on issue with the Mac and tab bars, complete with a sample app to reproduce the problem, in mid July. After hearing nothing for a while (feigned surprise), I contacted DTS. They told me they were aware of the issue and keep watching my feedback on the problem. That it still hasn't been addressed or responded to makes me think Apple just doesn't care. The entire feedback system is fundamentally broken is so many ways. The past few years it seems like a complete in time. Next year, I don't think I'll bother filing anything.

If anyone wants to dup it, I created Feedback FB15838445 and Apple is responding to it, asking how I used the feature. Fingers crossed they reinstate it.

Same. Code that was working in Beta 1 now produces this error in Beta 2. Hopefully someone from Apple is watching this. I know, I know, "File a feedback!", but after years of them being ignored, it's not worth the time that could better be spent elsewhere.

This is fixed in beta 3.

Is anyone else running into an issue with SpeechAnalyzer not releasing properly in iOS 26 Beta 4? You can test this with the speech to text sample app by create a story and recording some speech multiple times. On the third story I'm getting a "Maximum number of recognizers reached" error when trying to record. I'm seeing this behavior in our own app too on the third attempt at using speech to text in the app. Feedback filed for this: FB19003031

I duped this one as well (FB20547079 for iPadOS 26, FB20376452 for macCatalyst 26.1, and FB20376479 for iOS 26.1). The problem still exists in beta 2.

This is still broken in 26.1 Beta 3. Is there anyway to find out if it will be fixed by the time 26.1 releases?