İOS 26 beta battery %1

Are all of you posting bug reports with Feedback Assistant? Make sure you do. Be sure your report includes the steps needed to reproduce the issue and include the sysdiagnose attachment. What version of macOS is everyone seeing this issue with? In my case I'm running macOS 26.0.1. I don't know if the version of macOS matters or not. I see the issue with both Xcode 26 and Xcode 26.1. It's just requires starting an iOS/iPadOS 26.1 simulator. I have no issue when running an iOS/iPadOS 26.0 simulator.

Thanks for reporting the issue. Do you have a feedback report yet? If not, would you mind to file one for us and share your report ID here? Best, —— Ziqiao Chen  Worldwide Developer Relations.

Some questions. By SwiftUI instrumentation, do you mean profile your app in Instruments with the SwiftUI instrument? What version of Xcode are you running? What version of iOS is the device running? The new SwiftUI instrument Apple added in Xcode 26 requires iOS 26+. If your device is running an earlier version of iOS, you can't use the new SwiftUI instrument. If you can't use the new SwiftUI instrument in Xcode 26, click the Add Instrument button above the timeline pane graphs and add the legacy View Body and View Properties instruments to profile the app. Also, remove the SwiftUI instrument from the trace.

Been having the same issue currently on iOS 26.1 and it’s still showing up for me

Never use the comments feature here in the forums. They don't trigger notifications and people don't notice them. This was an annoying bug for me so I wanted to double-check and close the loop. Otherwise, I might have forgotten about it and never seen your comment. But my bug does seem to be fixed. I actually got thrown off when you said NTFS. I was thinking about the NTFS driver. You're actually talking about SMB file shares. I just tested that and it seems to work fine for me. However, I have a special use case. I don't actually need to look at the data. But curiously, the bookmark I restore is NOT the same one I saved. When I save a bookmark to the root filesystem of the startup volume, the url I decode is file:///.nofollow/. So dig into your code and see if the url you are decoding from the bookmark is actually the same url you encoded. I'm not seeing this behaviour on a network volume, but I'm using a Mac as a server.

Within the Apple Home API, the Matter Framework is an add-on, provided by Apple, and which is a subcomponent of the larger connectedhomeip. No, not exactly. The Matter framework is NOT part of HomeKit; it’s a new (and much broader) framework that specifically implements the controller side of the Matter communication protocol. In architectural terms, HomeKit's Matter support is implemented using the Matter framework. subcomponent of the larger connectedhomeip. In case this wasn't clear, the connectedhomeip GitHub project is the open-source project for the entire Matter protocol/specification. That project hosts not just the Matter framework but accessory support libraries and accessory reference implementations. Strictly speaking, the Matter framework isn't an Apple Framework but is actually an open-source library that we contribute to and then include as part of the system. The only connection to HomeKit here is that one small subcomponent of the Matter framework which can be used to create a limite

Something is really strange with the battery on my iPhone 16 Max running ios 26.1 prerelease beta. Yesterday morning I made a 1 hour facetime call (my phone was at 98% before the start of the call). After the call finished, I terminated (swiped up) facetime, and then checked Battery. It said that facetime had used 11%. About 1/2 hour later I checked battery and it said that facetime had now used 18% even though it still said that it was 1 hour on screen and 0 background. About 2 hours later, battery said that facetime was up to 20% with the same on screen and background. In desperation I deleted facetime from the phone, reinstalled in from the App store and restarted my phone. An hour later it reported Recently deleted app was now up to 30%! Either something is buggy with the battery reporting or something is really wrong with the ios operating system.

this bug has been fixed in the official ISO 26.1 release. Thank you for resolving it in the new version! You're very welcome. I'm sorry I couldn't be more specific in my earlier post, but when I posted my earlier email the fix was already making it's way into the final build. I’m not sure if my report prompted the fix, but I truly appreciate it nonetheless. Yes, your bug played a significant role in making sure this got fixed. 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 That's feedback we hear a lot. I'd love to see it as well, but the volume of bugs and our own secrecy requirements make it a difficult issue to address. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

I would like to know whether BGContinuedProcessingTaskRequest supports executing asynchronous tasks internally. Yes, this is 100% supported. FYI, it uses the same approach as the other task types, so everything I'm describing equally applies to the other task types in the background task framework. or if it can only execute synchronous tasks within BGContinuedProcessingTaskRequest? No, not at all. You CAN choose to do your work inside the task block, but you are under no obligation to do so and, in fact, properly implemented solutions for work like you're describing: ...(such as video encoding/decoding & export). However, our export interface is an asynchronous function, for example, video.export(callback: FinishCallback). ...probably SHOULDN'T try and force their work into the task block model. Doing so would mean either compromising performance by constraining yourself to a single thread or something like a semaphore to artificially block the task block, both of which are not ideal. And, yes, the code s