iPadOS 17.7.7

The “tapping the x in the search field cancels the search” issue has been in iPadOS 26 since beta 1. iPadOS 26 now emulates how Mac Catalyst apps have behaved for years. The issue doesn’t apply to iOS 26 since that shows a separate Cancel button. You can use FB17888632 as a demonstration of the issue. That is another search related issue I filed against iOS 26 beta 1 that still isn’t fixed in iPadOS 26 beta 9. It’s impacting my app and it also easily demonstrates the issue with the search getting cancelled when tapping the x icon to clear the search.

@Manuelinh0 What happens in Software Update? Is anything listed for update, but it fails to install, or is nothing listed to install? Can you turn off developer beta updates, and turn them back on? You could try wiping it and putting it back to iPadOS 18, then enabling developer betas again?

I'm on the latest beta and I'm still not seeing the dividers in my iPadOS menu bar.

I encountered the same issue. On iPadOS 17 and earlier systems, data packets could be sent multiple times within a single connection interval, but on iPadOS 18, they could only be sent once. Using a packet capture tool, I found that within a connection interval, iPadOS 17 sends a packet of data with the More Data attribute set to True, whereas iPadOS 18 sends it with the attribute set to False. As shown in the figure, multiple transmissions can occur within a very short time interval, whereas in iPadOS 18, only one transmission is allowed with an interval of 30ms Has your problem been solved? I would like to know if this issue is due to some restrictions imposed by iPadOS 18 or if there is a problem with our program configuration. I am looking forward to your reply

I encountered the same issue. On iPadOS 17 and earlier systems, data packets could be sent multiple times within a single connection interval, but on iPadOS, they could only be sent once. Using a packet capture tool, I discovered that within a connection interval, iPadOS sends a packet of data with the More Data attribute set to True, while iPadOS sends it with the attribute set to False. As shown in the figure, multiple transmissions can occur within a very short time interval. In iPadOS 18, only one transmission is allowed with an interval of 30ms Has your problem been solved? I would like to know if this issue is due to some restrictions imposed by iPadOS 18 or if there is a problem with our program configuration. I am looking forward to your reply

It looks like your goal here is to report a bug. If so, please do that using Feedback Assistant. See Bug Reporting: How and Why? for further advice on that front. IMPORTANT When filing bugs about the on-the-‘wire’ behaviour of Wi-FI, follow the Wi-Fi for iOS/iPadOS instructions on our Bug Reporting > Profiles and Logs. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I had no trouble replacing the View menu with code similar to the following: override func buildMenu(with builder: any UIMenuBuilder) { super.buildMenu(with: builder) if builder.system == .main { let cmd = UIKeyCommand(title: Hello, image:nil, action:#selector(doStuff), input: 1, modifierFlags: .command) let menu = UIMenu(image: nil, options: .displayInline, children: [cmd]) if let view = builder.menu(for: .view) { let newView = view.replacingChildren([menu]) builder.replace(menu: .view, with: newView) } } } With that code the View menu only shows the one menu item I created. Tested with Xcode 26 beta 7 running on a simulated iPad running iPadOS 26 beta 6.

Hi @curve, Please see the following page to learn how to submit an interoperability request: Requesting interoperability with iOS and iPadOS in the European Union https://developer.apple.com/support/ios-interoperability/ For more information on Apple's compliance to the European Digital Markets Act, please see the following page: European Digital Markets Act (DMA) https://www.apple.com/legal/dma/ Cheers, Paris X Pinkney |  WWDR | DTS Engineer

We are tracking some similar issues with the A16 iPads, and looking for a fix in an upcoming iOS/iPadOS While we believe your issue could also be resolved with an upcoming fix, it does not hurt to have more data points, as the remote devices the iPads interact with vary, and would be good to cover as much as we can. To that end, we would like to see some diagnostic logs to understand why this might be happening on your end. To create that log, please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then, once the logging profile is installed: reproduce the problem, keeping track of the actual time of the actions you take and the result you see. please have your app use os_log() statements to indicate what CoreBluetooth actions it is taking if you have a small project demonstrating the issue, please include that. Once the problem is reproduced, follow the instructions at the above link to t