İOS 26 beta battery %1

I probably miss something. Why do you compile with Xcode 16 and not directly Xcode 26, as you have added a class defined in Xcode 26 ? Did you set an OS target somewhere ? (__IPHONE_OS_VERSION_MAX_ALLOWED) Please show the code where error occurs.

[quote='864143022, richy6, /thread/805639?answerId=864143022#864143022, /profile/richy6'] using iChat:// results in the behavior we want. [/quote] You seem to have missed the point of my response. Unless you can find Apple documentation for the iChat URL scheme, it could well suffer the same fate as the messages URL scheme. Do not build a product that relies on implementation details. Doing so causes maintenance grief — like this very thread — and could potentially paint you into a corner such that you have to remove features that your users are relying on. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='864082022, Jnosh, /thread/805582?answerId=864082022#864082022, /profile/Jnosh'] Hopefully we get Swift-native and Swift Concurrency compatible support for creating OS activities at some point [/quote] I recommend that you file an enhancement request for that specifically. Please post your bug number, just for the record. As to your comments about how to mix activities and Swift concurrency, I don’t know enough about those interactions to offer an informed opinion. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This seems like a use case worth supporting; can you file a feedback request for it, or share the ID if you’ve already filed one?

I can’t speak to App Store policy issues. My advice is that you start a new thread about the policy side of this in App Store Distribution & Marketing > App Review. Feel free to reference this thread for the technical background to your concern. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for submitting FB20876956. Reading that through, it explains what you want but gives not details as to why you want it. I recommend that you add that context. My experience is that details like that help ERs get more traction. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Glad it’s sorted. I don’t have any details to share here, other than that, based on the resolution of your bugs, it seems like this was a transient outage in the Feedback Assistant service. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, it’s hard to say for sure whether the fix for this will come from Xcode or from WebKit. Given the possibility of the latter, you could try engaging with the WebKit open source effort. Honestly, I’m not sure whether that’d help or not. It’s not a sandbox that I play in. You could also change your testing approach. I’ve never been a huge fan of mocking via a subclass, partly based on similar experiences to this with the Foundation URL loading system types. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='864098022, Pasjonsfrukt, /thread/803580?answerId=864098022#864098022, /profile/Pasjonsfrukt'] Sorry for the late response! [/quote] No worries. I have plenty of other things to do (-: [quote='864098022, Pasjonsfrukt, /thread/803580?answerId=864098022#864098022, /profile/Pasjonsfrukt'] We have not seen the issue when we connect to the AP through Settings > Wi-Fi. [/quote] OK. The reason I asked is that here on the Apple Developer Forums our primary focus is on APIs. If you were able to reproduce the problem in Settings then that’d eliminate any possibility that your iOS code is incorrect. Without being able to reproduce it in Settings, it’s possible that this is a bug in your app (you occasionally pass in the wrong Wi-Fi details) or in the Network Extension layer that you’re calling (as opposed to the core Wi-FI layer that does all the heavy lifting here). However, the actual error you’re seeing here, failed to association error 1, is a strong indication of an issue in the core Wi-

Hmmm, this is the second question I’ve seen about SAML-based SSO in the past week. Are you working on the same product as francisaugustomedeiros over in SAML with SSO extension triggering twice? Or is this just a coincidence? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I pasted a concrete example of calling Swift from C++ in your other thread. Admittedly, this was calling a class not a struct, but it seems like a reasonable place to start. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='805580021, hoppedevz, /thread/805580, /profile/hoppedevz'] Is there any way to retrieve the memory pressure percentage using native libraries? [/quote] Be careful here. In any non-trivial VM-based OS, free memory isn’t a useful statistic. I talk about this in On Free Memory. In most cases you want to respond to memory pressure notifications. You can get those via Dispatch; see the makeMemoryPressureSource(eventMask:queue:) function. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s working but only when I redeem it through the sandbox account management in the developer settings. If I try to redeem it via my app I get a message saying I need iOS 16.3 or later, when I’m clearly on iOS 26. Clear Purchase History is also not working. Even after reinstalling my app it still fetches the redeemed purchase.

This seems like something that the NE team is going to have to investigate. [quote='805679021, davidsansom, /thread/805679, /profile/davidsansom'] I have raised a FB ticket, FB20866080. [/quote] Thanks. That’s the best path forward here. My only other suggestion is that you add a ‘first light’ log point to your sysex and to your NE filter provider, as explained in Debugging a Network Extension Provider. That’ll tell you whether the sysex started and, if it did, when the NE filter provider started within that. If your code isn’t started at all in these failure cases, that’s more evidence that this is an issue on the OS side of things. Note The advantage of using the system for these ‘first light’ log points is that these log entries end up in the sysdiagnose log. You can then point to them, or the absence of them, in the sysdiagnose log that you attached to your bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com