iPadOS 17.7.7

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. we do not wish to create a driver visible by the entire system. Well, that certainly simplifies things. For example, it makes an EA-based solution feasible (although the EA-based solution still requires MFi hardware). Are there any APIs that give an application access to a raw USB interface … in userspace? Not on iOS. On macOS you can do this using the I/O Kit API [1]. And on iPadOS you can achieve similar functionality using DriverKit. But iOS has neither of those options. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You can also do it using the KPI, but that just complicates things unnecessarily.

You don’t have a lot of options in this space. [quote='802640021, nam-common, /thread/802640, /profile/nam-common'] we have been informed DriverKit is only available on iPadOS, not iOS. [/quote] That’s correct. [quote='802640021, nam-common, /thread/802640, /profile/nam-common'] First being IOkit [/quote] macOS is the only platform that supports I/O Kit drivers [1]. [quote='802640021, nam-common, /thread/802640, /profile/nam-common'] the second being External Accessory Session (EASession). [/quote] There are two problems here: External Accessory framework can only talk to accessories that are built under the aegis of the MFi programme. If you have an existing accessory that wasn’t built that way, you can’t talk to it with EA. External Accessory framework allows apps to talk to hardware. It doesn’t let you publish a network driver that’s visible to the rest of the system. I think your best option here is to work with your chip vendor to update their firmware to work with iOS’s built-in USB Ethernet dr

Although the code may not be using the best or latest practices, that is not the main concern. It seems that most methods that modify the layout of the tableView, either directly or indirectly, results in the strange auto scrolling behavior. Or maybe the issue is triggered when the tableView does not fill the entire view. The mechanics of the bug are not fully known. The conditions behind this do not seem to make sense. navigationControllerWithVC.navigationBar.isTranslucent = false for example, may not be using best practices, but why does that cause the table to start auto scrolling when being reloaded? The same can be asked for the safeArea top anchor scenario in the original code. Disregarding all of the navigation bar stuff, consider another case where we may want to present a label or some other content above the tableView. If the setupTableView() function is replaced with the code below, this will also trigger the auto scrolling issue: func setupTableViewWithLabelAbove() { tableView.delegate = self tabl

@DTS Engineer What's the point of filing a bug report? Will it actually get fixed? I'm asking a serious question because I've already filed several iOS/iPadOS 26 bug reports related to UISplitViewController and UIKit. Several were reported against beta 1. Those bug reports include trivial sample apps and step-by-step instructions demonstrating the issue. None have been fixed as of iOS/iPadOS 26.0 GM. I also have several outstanding bug reports for broken functionality about UISearchController/UISearchBar under iOS/iPadOS 26. Again, several since beta 1. All include trivial test apps that demonstrate the issue. Again, none have been fixed. All of these outstanding issues are impacting my app. I'm very frustrated and disappointed. I'm sorry but I no longer have the ambition to file more bug reports that will never be fixed. I truly hope Apple gets back to the days of it just works. That era seems to be lost at the moment. Every year iOS and others are updated with lots of new features

Happy to help answer some of these! Yes. The Foundation Models framework uses the on-device system foundation model. It's an ~3 billion parameter model designed and trained by Apple. Is the language model provided by FoundationModels designed and trained by Apple? Or is it based on an open‑source model? The exact same on-device model is available on iOS, iPadOS, macOS, and VisionOS on all devices that support Apple Intelligence. Is this on‑device model available on iOS (and iPadOS), or is it limited to macOS? No. The general on-device model you access via Foundation Models is not a coding model and isn't suitable for most code tasks. Xcode on Mac has a separate built-in coding model to help with code completion. When I write code in Xcode, is code completion powered by this same local model? If so, why isn’t the same model available in the left‑hand chat sidebar in Xcode (so that I can use it there instead of relying on ChatGPT)? Yes and no. You can give the on-device model access to that ki

This behavior still exists in iOS 26.0.1 and iPadOS 26.0.1 even after upgrading the Apple Configurator host to macOS Tahoe 26.0.1. On every restart, Software Update Complete is displayed, along with: Your iPad has been updated to iPadOS 26.0.1. Your iPhone has been updated to iOS 26.0.1. Followed by the Welcome screen with the Get Started button. (Upgrading the Apple Configurator host to macOS Tahoe 26.0.1 did, however, fix the blank Profiles bug in Apple Configurator Version 2.18 10A23.)

The source code of the App is now public. A sample project for iOS/iPadOS that searches ARKit's rawFeaturePoints for geometries using FindSurface's real-time geometry detection capabilities.

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. You wrote: this error occurred when iPhone17Pro connecting to our Wi-Fi device OK. I can’t do much to help you with on-the-wire Wi-Fi problems here on the forums. My general advice is that you file a bug report about such issues. In the case of Wi-Fi issues specifically, 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

Thanks. I got so focused on getting this added to the context menu I forgot about the “Paste and Match Style” item appearing in the Edit menu bar. Of course that only helps with the iPadOS 26 and Mac Catalyst versions of the app. For iPhones and for iPads on iPadOS before 26, my only option is to use the context menu. I guess I’ll stick with my buildMenuWithBuilder: approach.

The same problem occurs with ipadOS 18 and 26. As described in the previous posts, the external keyboard can't be used for TextField on Swift Playground. When I disconnect the external keyboard, the onscreen keyboard works as expected. I had OS 18 and installed 26.0 hopping it may fix the issue but is did not. I tested the code above and got this exact same result. Thank you for any advice or update.

Hi, We are experiencing the very same behavior and working with our transcoding partner trying to resolve this, but been unsuccessful. However on ipad (10th gen) we had the same issue until we upgraded to iPadOS 26, then the issue disappeared and it's now working on ipad. Unfortunately the issue is still present on iphone 13 with OS26, although with longer gaps between the freezing. But since this issue has been resolved by OS26 update on ipad, it clearly signals that this is a Fairplay issue that has to be resolved by Apple. The issue was introduced in IOS 18. Can someone at Apple pleas acknowledge this and inform us if you are working on solving this?