apple pencil battery life

[quote='860711022, GlacierSec, /thread/802691?answerId=860711022#860711022, /profile/GlacierSec'] will the DNS Settings API allow it to be turned on and off from within the app? [/quote] Sure. In the DNS settings API you use NEDNSSettingsManager to apply your settings, and it has an isEnabled property that does what you want. IMPORTANT The limitations on DNS proxy providers are privacy focused. A DNS proxy has a privileged network position, allowing on-device code to see all the DNS names used by the user. The DNS settings API doesn’t work that way, because you just apply settings that are then used by the built-in resolver. That’s why you can use the DNS settings API in any context, where DNS proxy providers have hard deployment limits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What platform are you testing this on? [quote='860810022, krpaul, /thread/802801?answerId=860810022#860810022, /profile/krpaul'] I've submitted a bug report: FB20479096 [/quote] OK. But it has no sysdiagnose log, which is gonna limit its ability to get traction. I recommend that you grab a sysdiagnose log immediately after reproducing the problem and then attach it to your bug. See our Bug Reporting > Profiles and Logs for more on sysdiagnose logs. Oh, and while you’re there, have a read of the VPN (Network Extension) for the platform you’re targeting and enable the extra diagnostics. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m gonna start with your first question, for reasons that I hope will be obvious. You wrote: [quote='802846021, herman602, /thread/802846, /profile/herman602'] Can this method described in the article be built with Xcode 26 and run on iOS 26? [/quote] And then: [quote='802846021, herman602, /thread/802846, /profile/herman602'] Or is it restricted to run only on iOS 26 [/quote] Huh? I think one of those 26’s is meant to be a different number. That or I’ve completely misunderstood your point. Please clarify. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is clearly a bug. We either need to fix the SDK or fix the docs. I encourage you to file a bug to that effect. Please post your bug number, just for the record. You’ll be able to get your code building by conditionalising it like so: #if canImport(DeclaredAgeRange) import DeclaredAgeRange #endif And likewise for the places you use the API. Still, that leaves you without this functionality )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

My general advice on this front is to avoid temporary exception entitlements where you can. This is critical for App Store apps, but generally a good idea for products that you directly distribute using Developer ID signing. In this case there’s a standard way for sandboxed programs to use XPC without needing temporary exception entitlements, namely an app group. If you set up an app group, grant your app and your appex access to that group, and then have your daemon publish its named XPC endpoint ‘within’ that group, the sandboxed processes should be able to access that service without the need for a temporary exception entitlement. See App Groups Entitlement for info on how that works. Well, the app certainly will be able to. The situation with the appex is more nuanced, because appexen run in a custom sandbox that doesn’t always align with the standard App Sandbox used by apps. Which is probably the reason why your temporary exception entitlement is failing. I think the app group approach will help here, b

You tagged your thread with Mac and mentioned that the app “bounces”, which seems like a Dock thing, but you then specifically called out that this is “new IOS provisioning profile”. So I’m a bit confused. What sort of app is this? And if it’s an iOS app, are you trying to run it on your Mac? That is, using the iOS Apps on Mac feature? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The lesson from that other thread is that Apple reserves the right to change such values extra-ordinarily — that is, without the user specifically changing their biometrics — and your app should be designed to handle that gracefully. The doc comment you’re looking for isn’t on the domainState property, but rather on the various stateHash properties in . Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you testing this on a real device? Or in the simulator? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. there's some another way to read the current value instead of waiting for events? Not that I’ve seen. Certainly, the vm.memory_pressure value you mentioned in your other thread is not the droid you’re looking for. If you want to see what that returns you can look at the implementation in Darwin; it’s clearly part of this equation, but it operates at a much lower level. Likewise for things like kern.memorystatus_level. I think your best option is to assume that memory pressure is normal until you get an event via the Dispatch source. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hey Dawich, I'm following a similar implementation and using capacitor with stripe subscriptions in my ios application. I came across the capgo plugin and tried that approach but based on apple guidelines, it seems like we must use the in app purchase natively with Storekit. Were you able to find a solution to this?

Well Apple has pretty much dropped Objective-C and moved fully to Swift and SwiftUI becuase its faster and better to use. Worth learning it though.