İOS 26 beta battery %1

You seem to have misunderstood. That note, Note 5, only pertains to the specific cases where Note 5 is referred to, namely: if the app Force Quit by the user Control Center Bluetooth button toggled An app that was force quit was never able to be relaunched before. iOS 26 actually adds the capability for such apps to be launched if they opt in to use AccessorySetupKit. So, this is not a case of apps losing the capability to relaunch, but a case of apps gaining the capability to relaunch in cases where they weren't able to before, if they use AccessorySetupKit.

The only way I could resolve this on an affected device was a factory reset. Strange as dev, QA and personal devices on iOS versions > 18.5 all started having this issue at the same time. Something gone wrong at OS level for this update path when generating apns tokens maybe?

Hello, Did you find any solution about that? We have similar problem on tvOS 26. I also have created post which is https://developer.apple.com/forums/thread/804985

Thanks for all the answers. What you’re dealing with here is the responsible code problem. When a process performs a privileged operation, macOS has to track down the responsible code so that it can check whether that code has TCC privileges or not. In general, macOS will follow the chain from child process to parent process to determine process responsibility. However, things are not that simple: The child process might be doing things to break the chain. There are also situations where macOS doesn’t follow the chain as you might expect. I have a test project that I use to exercise cases like this, and it seems to be working for me. Here’s what I did today: On macOS 15.7.1, I went to System Settings > Privacy & Security > Input Monitoring and confirmed that there’s no entry for my test app there. I used Xcode 26.0.1 to build and run the app. I started input monitoring within the app. The system presented the permissions alert. I clicked Open System Settings. And enabled Input Monitoring in System S

[quote='864383022, spacecash21, /thread/804561?answerId=864383022#864383022, /profile/spacecash21'] it seems like macOS memory protection kicks in and does not allow starting/restarting different executable. [/quote] Hmmm, I’m not sure how memory protection is a factor here. The log snippet you posted suggests that your daemon is crashing. Does that generate a crash report? If so, please post it here. See Posting a Crash Report for advice on how to do that. Also, how are you updating your app? Make sure that you’re not hitting the problem described in Updating Mac Software. Specifically, use the instructions in Check Third-Party Software Updaters to verify that your new daemon was written to a new file with a new inode number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the clarifications. Just FYI, in networking, raw socket usually refers to raw IP sockets, hence my confusion. So, lemme summarise the issue: You have an iOS app. It talks to a Wi-Fi based accessory over TCP. With iPhone 16, this all works as expected. With iPhone 17, things go wrong, such that your TCP socket disconnects after 20 seconds. After that, your app is unable to reconnect. And the only way to resolve the issue is to restart the Wi-Fi subsystem on your accessory. Is that right? If so, this sounds eminently bugworthy. While there are lots of ways that local networking can go wrong, the fact that this fails when the only variable you change is moving from iPhone 16 to 17 suggests that it’s caused by a Wi-Fi level issue on iPhone 17. DevForums focuses on Apple APIs and tools, and isn’t really set up to help with Wi-Fi level issues. Given your description of the problem, I think it makes sense for you to file a bug so that our Wi-Fi engineering team can investigate. In your bug, make

[quote='864274022, TyngJJ, /thread/805696?answerId=864274022#864274022, /profile/TyngJJ'] I'm using the terminology from an older document [/quote] Yeah, the terminology here is confusing, which is why I’ve switch to named XPC endpoint. It’s long and clumsy [1], but it’s very clear. Unfortunately there’s no way to get that older doc fixed, because the Documentation Archive is a read-only snapshot. You can’t use the responsible process constraint on a launchd daemon or agent because its named XPC service is published to a Mach bootstrap namespace that allows multiple clients to connect. The first client starts your process and then subsequent clients trigger a new connection to that same process. Given that, the concept of responsible process doesn’t really make sense [2]. What you’re really trying to do here is to ensure that your agent only does work on behalf of your app, and that’s the problem that XPC peer constraints solve. In the case of an launchd agent, it’s best to apply XPC peer constraints

Following up on this issue, specifically - the edge correction screen top bar positioning issue is significantly impacting our app. To provide more context: The grey strip appearing beneath the status bar (instead of at the bottom) makes the UI appear broken to users. The issue is consistent across all iOS 26 devices we've tested. Custom styling or modifications are not possible to the VNDocumentCameraViewController as per my knowledge. Has anyone else encountered this? We'd greatly appreciate: Confirmation whether this is expected behaviour or a known issue. Any recommended workarounds or API changes we should implement Any guidance from Apple Engineering would be highly appreciated.

Wow, that’s quite a coincidence. One gets no interesting App SSO questions for years, and then two come by that both mention SAML! Anyway, let’s dig into your issue. Earlier you wrote: [quote='805658021, sunil.jakhar, /thread/805658, /profile/sunil.jakhar'] the extension consistently crashes when calling WKWebView.load(_:) [/quote] Please post a full Apple crash report for this. See Posting a Crash Report for hints and tips on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com