İ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! 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

The message seems to indicate a framework version mismatching, which likely happens when you have a store created with the higher version framework (Persistence-1522) and try to access it with the lower version (Persistence-1518). The store file path has CoreSimulator, and so I guess if it is that the version of your simulator doesn't match. Does the issue happen when you run your app on an iOS 26.1 device? Also, does the version of your simulator match your Xcode version? If not, you can try to remove the simulator and re-install a new one using the UI at Xcode > Window > Devices and Simulators. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Technically, it's totally fine that your app replaces an existing model container with a new one, or use multiple containers. Just be sure that you update with the appropriate container for your views and scene via their modelContainer(_:) method. When that is done, the model context injected to the environment of the view hierarchy should change automatically, which triggers an update for the view hierarchy. Practically, I'd probably only do that if every user has their own store (so I need to switch to another store when a user login happens). Sharing one single model container across an app is good enough for most cases, and makes things simpler. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I got this error only in case the user selected the never and the ask setting for the location. It worked for uns in iOS 18 but no longer in iOS 26

Please test with iOS 26.1 and if the issue persists, please file a Bug Report on this In your bug report we would need some diagnostics logs as well. 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 reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the bug report as well. If you have separate sniffer logs that shows the interaction, also do include those. We would also like to know the peripheral devices you are seeing this issue with. Make/Model and if you know, the BT chipset details (HW/FW versions and manufacturer) would be helpful to track this down. Once done, please share the Feedback ID here, and @mention me in your response so we can take a look at this right away. Argun Tekant /  WWDR Engineering / Core Technologies

Creating bookmarks to the root directory of a volume was broken in earlier versions of 26. It looks like a change was made and that change broke NTFS. Good thing I haven't released yet. I need to double check. My workaround assumed that creating the bookmark would fail. I didn't anticipate success with invalid data. I don't know if my workaround would work for you. I have a special case where I don't actually need to access the data. I just want to know the URL. I can get the data I need without a security scoped bookmark. And it sounds like I need to re-do it anyway.

Hi, I have the same issue. I am not receiving any server to server notifications anymore in the sandbox environment. Last notification I received was yesterday evening November 3th ( UTC + 1 ).

I am experiencing the same bug. On iOS 18 and older, when I move a slider, the last value reported by onEditingChanged returns false, as expected. But now on my iPhone 15 Pro running iOS 26.1 and built with Xcode Version 26.1 (17B55), the last reported value for the slider's onEditingChanged is still returning true for the final value when I lift my finger off the slider.