İOS 26 beta battery %1

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

We discovered the iOS version is not the culprit. All models starting with 14 series iPhones and onward are affected by this problem, even on iOS 17. Must be some glitched interaction of hardware and software feature. Affected models do not produce any audio, magnitude logging from C++ engine doesn't produce anything. static OSStatus mixerPlaybackCallack(void *inRefCon, AudioUnitRenderActionFlags *ioActionFlags, const AudioTimeStamp *inTimeStamp, UInt32 inBusNumber, UInt32 inNumberFrames, AudioBufferList *ioData) { AudioEngine *self = (AudioEngine*)inRefCon; uint32_t toget = inNumberFrames << 2; //printf(mixerPlaybackCallack: bus: %u, frames: %un, (uint32_t)inBusNumber, (uint32_t)inNumberFrames); if (inBusNumber < kMaxRemoteLines) { auto& audiobuffer = self->m_remoteBuffers[inBusNumber]; int32_t len = 0; if (uint8_t *buf = audiobuffer.tail(len)) { int32_t tocopy = len > toget ? toget : len; memcpy(ioData->mBuffers[0].mData, buf, tocopy); audiobuffer.consume(tocopy); if

Did you find anything out on this? We are experiecinging a similar issue with hls playback not starting right away on iOS 26, but it will start immediately on iOS 18. This is on a local network so internet speed is not an issue.

I've tried your code with my iOS 26.x device + Xcode 26.1 beta 2 (17B5035f) and can't reproduce the behavior. Have you tried with the latest version system and tool? I am curious if you still see the behavior there. I'd say changing the selectedTextRange of the text field is the right way to go, but the system can indeed override the result, and so you might try to delay your change a bit. The following code makes the change 100ms later: func textFieldDidBeginEditing(_ textField: UITextField) { DispatchQueue.main.asyncAfter(deadline: .now() + 0.01) { let end = textField.beginningOfDocument textField.selectedTextRange = textField.textRange(from: end, to: end) } } Best, —— Ziqiao Chen  Worldwide Developer Relations.

Please verify and report back if you're able to reproduce the issue using Bringing Photos picker to your SwiftUI app sample on iOS, iPadOS 26.1 RC & macOS. Thanks

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.