İOS 26 beta battery %1

this bug has been fixed in the official ISO 26.1 release. Thank you for resolving it in the new version! I’m not sure if my report prompted the fix, but I truly appreciate it nonetheless. That said, I hope in the future the bug-reporting website can provide real-time acknowledgment—something like “received, under review”—instead of one-way submission with zero feedback. Thank you!

Please find the crash report attached- SSOExtension-2025-11-04-110555 copy.txt Please clarify if WKWebView usage inside extensions is officially unsupported as of iOS 26, and if so, recommend an alternative approach for handling SSO flows.

Adding some more context to this as I'm determining how best to set up my CloudKit zones: Option A (Current) - 1 zone per Root parent collection Option B - 1 zone per collection With Option A, I’d need to handle cross-zone migration whenever a SavedItem moves between Collections, or when a Collection’s parent changes (since that effectively moves an entire sub-tree of data into a new/different zone). With Option B, where each Collection has its own zone, I’d only need to worry about migrating SavedItems and Extracts when they move between Collections - parent/child changes between Collections themselves would just update references. Trade-off becomes: Option A → Simpler sharing (since sharing a single Collection would automatically include all its subcollections), but I’d need zone-migration logic for all object types — Collections, SavedItems, and Extracts. Option B → I’d still need zone-migration logic for SavedItems and Extracts, but not for Collections. However, sharing a Collection that

I didn't really find anything in Apple docs on how to debug my extension using Xcode (so not saying it doesn't exist). It doesn't exist. I found a current Stack post on it, with several devs all stuck. Gotta love the internet, eh? In 2024 someone said run the Preview Extension, select Finder as the test app, then in a Finder window select a file of the correct type and tap space. It's hard to debug what someone once said. QuickLook has been redesigned a couple of times. Maybe they were still trying one of the old designs. The easiest solution is to write a test rig. I was going to include a preview of folders in my new app, but then decided against it. But the QuickLook test rig will be useful in the future. Here's part of that code: This is view controller for QuickLook: import Cocoa import Quartz class PreviewViewController: NSViewController, QLPreviewingController { @IBOutlet weak var folderController: FolderController! override var nibName: NSNib.Name? { return NSNib.Name(PreviewViewController) }

Hi @SebGaming , I'm an engineer working with GameKit. From your example it looks like you're testing on macOS 15.6. Is that correct? If so keep in mind that these APIs are only available on macOS 26 and higher.

There are two main network level requirements for device connectivity with Xcode: The network supports Bonjour The network supports IPv6 with link-local traffic It's likely that the network where you can't connect the devices to Xcode is missing one of those requirements, and you need work with the network owner to address those configurations. If the network owner here is a corporate IT department, the link above to TN3158 tackles a particular slice these configuration requirements for some VPN and security configurations, so your IT organization may get some value from reading through that document, though there are many other types of IT configurations that fall beyond the scope of that document. There isn't a way to configure a device connection with just an IP address, neither with IPv4 or IPv6. You're correct that was possible a long time ago, but the inner workings of how Xcode and paired iOS devices communicate has significantly evolved since that time. — Ed Ford,  DTS Engineer

First off, I need to clarify the vocabulary here a little bit: Apple-specific Controller (Home Pod or Apple TV) In terms of the Matter specification and my own vocabulary, an ecosystem controller is any component (software or hardware) that maintains its own set of Matter ecosystem credentials, allowing it to directly communicate with Matter accessories. Most ecosystem vendors sell some kind of external hardware/accessory, but nothing about Matter actually requires that. Home Hub is the name HomeKit uses for a device that's located in the home that HomeKit can use to centralize the routing of commands to accessories. See this support article for more background. HomeKit does require a Home Hub to support Matter; however, this is best understood as a practical engineering choice on our part and not a fundamental limitation of Matter. I had an additional clarification request. Does using Apple’s Home exposition of the Matter API require using an Apple-specific Controller (Home Pod or Apple TV), or can any type

I tried to post the same post in Apple support community and was sent this reply: Thanks for participating in the Apple Support Community. We removed your post “OS 26 dictation repeating sentences... because it contained information about beta software. To comment or ask questions about beta software, go to our Apple Developer Forums page: https://developer.apple.com/forums/ Here you can share your OS 26 dictation repeating sentences... post, make comments, and ask questions.

This issue appears to have been fixed in iOS 26.

We conducted a test in our legacy KEXT environment, and the results indicate a behavioral difference between the KEXT and DriverKit frameworks in handling I/O requests. So, the first thing to understand is that IOKit and DriverKit are NOT fundamentally different/separate technologies. The best way to understand DriverKit is that it's implemented as a very specialized user client built on to our existing IOKit infrastructure. Note that this dynamic is quite direct- for example, a DEXT's IOKitPersonalities dictionary doesn't just look like an IOKit match dictionary, it IS an IOKit matching dictionary. How DEXT loading/matching actually works is: The matching dictionary is added into the kernels KEXT matching set just like any KEXT would be. When hardware is attached, that matching dictionary is used to match and load an in kernel driver in EXACTLY the same way ANY other KEXT would be. Once the kernel driver finishes loading, the system then uses the DEXT keys inside that matching dictionary to create your DEXT