iPadOS 17.7.7

Hi all, My Unity app was rejected for running in portrait mode on an iPad Air (5th gen) with iPadOS 18.6. My Unity Player settings are configured for landscape-only (Auto Rotation with Landscape Left and Landscape Right enabled). On my older iPad (5th gen) with iPadOS 16.7.11, the app works correctly and stays in landscape. Has anyone seen similar orientation issues with Unity builds on M1/M2 iPads running iPadOS 18? I suspect this is a bug with the new OS on specific hardware. Any insights are appreciated. Thanks.

FB: FB19828741 Maybe I am doing something wrong with the new LiquidGlass sidebar using iPadOS 26 Beta 7, but when using this code, in stead of the List being centered between the sidebar and the rest of the screen, the cell itself extends beneath the sidebar but the content stays clear of the sidebar, giving a weird visual effect. Not my expected behavior at least. Any ideas? Or just a bug? import SwiftUI struct ContentView: View { var body: some View { NavigationSplitView { Text(Test) } detail: { List { Text(ContentMargin) } .contentMargins(.horizontal, 100.0) } } } #Preview { ContentView() } This was on iPad OS 18:

I'm creating an iPad app using Xcode 26 Beta 6. I have the following simple code and web page, but when I tap the file selection button, nothing appears. Do I need to add any additional code? code struct SwiftUIWebView: View { @State private var webPage = WebPage() private let url = URL(string: https://www.xxxx.com/)! var body: some View { WebView(webPage) .onAppear { webPage.load(URLRequest(url: url)) } } } web page Test

Now using Xcode 26 beta 6, and iOS/iPadOS 26 beta 7 - and I found the codes do not compiled with localized name. Since I have been buidling the codes since beta 1, the app might have localized name in the past. Even Localizable file is there with proper translation. I have however, started to build icon using Icon Composer (before that was not). I have also tried to add in CFBundleDisplayName and CFBundleName in Localizable file, and same (English is shown). What have I done wrong or forget to do?

All of these issues appear when the search controller is set on the view controller's navigationItem and the search controller's searchBar has its scopeButtonTitles set. So far the following issues are affecting my app on iOS/iPadOS 26 as of beta 7: When the scopeBarActivation of UISearchController is set to .onSearchActivation, the preferredSearchBarPlacement of the navigationItem is set to .integratedButton, and the searchBarPlacementAllowsToolbarIntegration is set to false (forcing the search icon to appear in the nav bar), on both iPhones and iPads, the scope buttons never appear. They don't appear when the search is activated. They don't appear when any text is entered into the search bar. FB19771313 I attempted to work around that issue by setting the scopeBarActivation to .manual. I then show the scope bar in the didPresentSearchController delegate method and hide the scope bar in the willDismissSearchController. On an iPhone this works though the display is a bit clunky. On an iPad, the scope

Hi, I'm updating my iPhone app (iPhone only) to be ready with iOS 26. I'm building my app using Xcode 26.0 beta 6 (17A5305f) and testing it on an iPad running iPadOS 26 (23A5326a). I found an issue with my new app icon updated using Icon Composer and I was able to find the issue. An iPhone only app running on iPadOS 26 doesn't use the provided app icon. It always displays the standard light icon. I just added iPad in Supported Destinations and the app icon now respect light/dark/translucent/tinted modes on the Home Screen. I submitted feedback FB19768667

How can I remove the recents section from long-pressing on my app icon? I've added the following to my AppDelegate, which removes it from the top MenuBar, but not from the app icon context menu. My app has registered a custom filetype, but it is not a document based app. Opening files imports them into the app's user library, and so does not make sense to have a recents list. override func buildMenu(with builder: any UIMenuBuilder) { super.buildMenu(with: builder) builder.remove(menu: .openRecent) }

Hello everyone, Last year I built an application for tvOS and iPadOS that enables device-to-device communication. I based it on Apple’s sample code, available here: https://developer.apple.com/documentation/Network/building-a-custom-peer-to-peer-protocol At that time, everything worked flawlessly. However, this year I had to revisit the project to add new features, and now it no longer works as expected. The first time the app runs it connects fine, but if we relaunch it (on either the iPad, the Apple TV, or both), the connection fails. Most importantly, this is not an issue with my own code — I tested it directly with the original Apple sample code, and the exact same problem occurs there too. Here’s what I see in the logs: nw_endpoint_flow_setup_channel [C1 TicTacToe,65E91B02-890E-4D30-88B8-CE2AB9677BF9 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: utun0, scoped, ipv6)] nexus assignment error Connection refused nw_endpoint_flow_failed_with_error [C1 TicTacToe,65E91B02-

According to the WWDC25 Presentation Track workouts with HealthKit on iOS and iPadOS, there is supposed to be a new property for restoring an active workout after a crash on iOS/iPadOS. The developer documentation also supports this. However, this property does not seem to exist in the latest Xcode 26 beta, even in projects targeting iOS 26.0 as the minimum version. Am I missing something? Has this property not been made available yet? It is actually looking like all of the new iOS 26.0 properties are missing UIScene.ConnectionOptions on my system.

On iPadOS 26 (up to beta 7), .sheet backgrounds have a dark green tint on Dark Mode and a gray tint on Light Mode. This is clearly noticeable on both the Canvas/Simulator and a physical device. Here's a sample View that shows the issue: import SwiftUI struct ContentView: View { @State private var isPresenting: Bool = false var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Text(Hello, world!) Button(Show Sheet) { isPresenting.toggle() } } .sheet(isPresented: $isPresenting) { VStack { HStack { Spacer() Button(Cancel, systemImage: xmark.circle.fill) { } .foregroundStyle(.secondary) .labelStyle(.iconOnly) .buttonStyle(.plain) .contentShape(.circle) } TabView { Tab(Tab 1, systemImage: cart) { Text(Hello, tab 1) } Tab(Tab 2, systemImage: cart) { Text(Hello, tab 2) } } } .scenePadding() } .padding() .preferredColorScheme(.dark) } } #Preview { ContentView() } Is this the expected behavior with the new OS? Anyone else seeing this?

Request: Unlock full custom date setting on iPad (even pre-2001) with internet on I’d like to request a feature in iPadOS that allows the system date to be set to any value — even before January 1, 2001 — without disabling or breaking internet access. This is important for: Historical and educational simulations Timeline-sensitive app testing Calendar research and UI behavior in legacy periods Currently, iPadOS blocks dates before 2001. It also may bug out or disable networking features when dates are changed too far back. 📎 I've submitted this request to Apple via the official Feedback Form, and I’ve created a public GitHub repo to invite further support: 🔗 https://github.com/RubixCubeExpert/ipad-date-unlock-request If other developers support this, please reply or upvote. Thanks!

Hi. We are writing to report a critical issue we've encountered following the recent release of iOS 26 beta 6. After updating our test devices, we discovered that our application is no longer able to establish HTTPS connections to several of our managed FQDNs. This issue was not present in beta 5 and appears to be a direct result of changes introduced in beta 6. The specific FQDNs that are currently unreachable are: d.socdm.com i.socdm.com tg.scodm.com We have reviewed the official iOS & iPadOS 26 Beta 6 Release Notes, particularly the updates related to TLS. While the notes mention changes, we have confirmed that our servers for all affected FQDNs support TLS 1.2, so we believe they should still be compliant. We have also investigated several of Apple's support documents regarding TLS connection requirements (e.g., HT214774, HT214041), but the information does not seem to apply to our situation, and we are currently unable to identify the root cause of this connection failure. https://support.ap