Apple Maps Guides

Based off that, it feels like I should NOT rely on the BGContinuedProcessingTask notifications (or whatever they are called) to communicate state. It seems like instead what I should do is do something like local notifications to communicate state and handle it more in my app, is that correct? This is one of those questions where the right answer really depends ENTIRELY on the exact details of what you're trying to do. The simple end of the spectrum here are things like short-lived, single jobs, where putting up extra” UI to manage a single task which isn't going to take very long anyway might be unnecessary. At the other end of things, I think there are lots of situations where the work the app is doing doesn't nicely map directly to the task model and you'll absolutely want to use other tools/APIs to tell the user what's going on. As one example, if an app is doing lots of small network transfers, using an individual processing task for each transfer is probably a mistake. At a technical level, the

[quote='868157022, gingerlemon, /thread/806870?answerId=868157022#868157022, /profile/gingerlemon'] the tab is empty on both my personal user and the alias account. [/quote] So, lemme get this straight: You have a .p12 containing your signing identity, that is, your certificate and its private key. You created a new user on your Mac (that “alias account”). Using Keychain Access you successfully imported that .p12 into your keychain. And then you switched to My Certificates. But its shows no digital identities. Is that right? Are you sure that you: Imported the .p12 into your login keychain? And then, in step 4, you selected the login keychain on the left? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi Apple team, Thanks for the follow up. Here are the details you requested: Platform: iOS (running on iPhone hardware; built with Xcode 15, iOS 17 SDK). Extension type: Network Extension provider packaged as an app extension (appex) within the main app target. Keychain configuration: The main app and the extension both have the Keychain Sharing capability enabled with the same access group (for example, ABCD1234.com.example.shared). We also tried the common app group and specifying the access group via kSecAttrAccessGroup, including variations such as $AppIdentifier.KeyChainSharingGroup. Error observed: When the extension attempts to access the shared keychain, SecItemCopyMatching returns status 25291 (errSecNotAvailable), which Xcode reports as No keychain is available. The same code and access group work from the containing app. Could you advise whether additional entitlements are needed for Network Extension providers on iOS, or if there are specific packaging or provisioning steps we should doub

Use ASO tools like Appvector to map competitors’ ranked keywords, identify intent-based gaps, and quickly expand your own keyword list with high-value, relevant terms.

[quote='808875021, dhoelzl, /thread/808875, /profile/dhoelzl'] Am I missing something? [/quote] Other than that certificate revocation checking is a tangled mess? No )-: I’ll likely have more to say about this in a bit — I’m just checking on some details internally — but I wanted to reply now and ask about your high-level goal here. Why are you doing explicit revocation checking? What behaviour in your product will change based on the result? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867992022, pepipox, /thread/808699?answerId=867992022#867992022, /profile/pepipox'] The whole concept already works if launched from Xcode as root. [/quote] Running code as root from Xcode is very tricky. It puts you in a mixed execution context, where you’re running as user ID 0 but your non-BSD execution context is that of the GUI login session. Weird things happen in that case. In this case those weird things seem to be beneficial, but in reality they’re just misleading )-: [quote='867992022, pepipox, /thread/808699?answerId=867992022#867992022, /profile/pepipox'] My idea is that the user launches some app [/quote] If you have a GUI app and you’re using Personal VPN, why not call NEVPNManager directly from it. Why do you need these extra running-as-root bits? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Right. You certainly have a bunch of options for that, but it’s hard to say exactly which one is best. For example, I played around with the -all_load flag and it seem to do pretty much what you wanted. However, that’s a really heavy hammer, in that it pretty much disables all dead stripping. Whether that matters depends on your exact circumstances. Again, I recommend that you read the ld man page to learn more about these options. It’s terminology is… well… dense, so you might want to avail yourself of An Apple Library Primer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868001022, Hylus-Arbor, /thread/808897?answerId=868001022#868001022, /profile/Hylus-Arbor'] maybe the Accessibility is compromised in the same way with 26.1 [/quote] Yes. This bug seems to affect a wide range of privileges controlled by System Settings > Privacy & Security. I haven’t explored the full list, but others have noticed that it also affects Screen & System Audio Recording, so it wouldn’t surprise me if it affected Accessibility as well. [quote='868001022, Hylus-Arbor, /thread/808897?answerId=868001022#868001022, /profile/Hylus-Arbor'] I updated my own Mac from 15.7 to 26.1. [/quote] My recommendation is that you test this stuff in one or more VMs. That way you have direct control over what system software is installed, and you can revert to a known ‘clean’ snapshot between each test. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The only DTLS APIs on iOS are those in Network framework. But you’re not using that, right? Rather, you’re using BSD Sockets? Presuming that, there are at least two layers between the system delivering a UDP packet to the socket buffer and you receiving a DTLS message. Specifically: You have to implement some sort of mechanism to learn about data arriving on the socket. You can do this using select, kqueues, Dispatch sources, and so on. You have to implement DTLS on top of UDP. A failure at either of these levels could result in the problem you’re seeing. Given that, my advice is that you try to set up a test case that eliminates them. First, use an RVI packet trace to ensure that the packet was actually delivered to the iOS device. IMPORTANT It’s possible that this RVI setup might mask the issue. If that’s the case, lemme know, because it would be an interesting data point in and of itself. Next, get DTLS out of the picture. Just for testing purposes, set up a simple UDP echo server and ping it on the VoIP w