Apple Maps Guides

Thanks for confirming that. If you’re using BundleProgram then there’s only one copy of your daemon on the system at any given time, the one embedded within your app. Which brings us to this: [quote='804561021, BenderNym, /thread/804561, /profile/BenderNym'] I have a theory, that sending the daemon a command to kill itself after app update, would load the latest daemon. [/quote] That’s what I’d expect. Please give it a whirl and let us know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

laszlolaszlo et al, Keep in mind that this is Apple Developer Forums, where the goal is to help developers with code-level problems. If you’re having problems with a third-party product, I recommend that you reach out to its developer via their support channel. Apple folks can’t help you with a third-party product, and it’s quite unlikely that anyone from the third-party product’s support team is hanging out here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='861496022, Vigyanlabs, /thread/794800?answerId=861496022#861496022, /profile/Vigyanlabs'] Tried stapling … but it fails with Error 65. [/quote] There are two common causes of error 65, as I explain in Resolving Error 65 When Stapling. If you look at the details of the error, you should be able to figure out which one you’re hitting, and follow the resolution steps from there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='862370022, kargoedev, /thread/771265?answerId=862370022#862370022, /profile/kargoedev'] they should have a compiler flag you can add that requires you to declare all variable types [/quote] You should feel free to pitch that idea via Swift Evolution. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sure. You need to do your own security assessment here, of course, but IMO there’s not much point trying to defend yourself against the user running a malicious installer package (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='862666022, nikhil2701, /thread/787570?answerId=862666022#862666022, /profile/nikhil2701'] I have a followup question on this [/quote] I’m gonna recommend that you put your question in a new thread. Use the App & System Services > Networking so that I see it go by. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='862030022, krpaul, /thread/802801?answerId=862030022#862030022, /profile/krpaul'] I have reproduced the bug and collected a sysdiagnose [/quote] Thanks. I took a quick look at your bug (FB20479096) and it’s definitely in the right place. As to this mysterious error 7, that’s actually pretty generic. The more interesting error is error 14, in your second snippet, which is specific to URL filters. That is .unknown: print(NEURLFilterManager.Error.unknown.rawValue) // -> 14 Usually errors like this come are accompanied by more hints in the system log. I explained that idea in this post yesterday. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FYI, I’m gonna close this thread. See this post for an explanation as to why. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='861858022, Foplik, /thread/802184?answerId=861858022#861858022, /profile/Foplik'] we can't reproduce this issue in the iOS simulator. [/quote] OK. I asked that for a bunch of reasons: The simulator offers more network debugging options. If something reproduces in the simulator, I’d expect it to reproduce on macOS itself, which opens up further options. The next step is to file a bug, and the best way to do that depends on the platform. IMO you should file a bug about this. It’d be ideal if you could include: A small test project that reproduces the problem. A sysdiagnose log taken on the device immediately after reproducing the problem. After having installed the Network Diagnostics debug profile from our Bug Reporting > Profiles and Logs page. An RVI packet trace of the fast and slow cases. Presuming that just enabling RVI doesn’t resolve the problem, of course (-: Please post your bug number, just for the record. [quote='802184021, Foplik, /thread/802184, /profile/Foplik'] Attempted to collect ql

[quote='861588022, tommyjc, /thread/763494?answerId=861588022#861588022, /profile/tommyjc'] In October 2025 this is still an issue [/quote] That gels with my reading of FB15094270, which remains unresolved. Has anyone else filed any bugs about this? If so, please post the bug numbers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='862856022, _JC, /thread/803846?answerId=862856022#862856022, /profile/_JC'] making sure connection.cancel() is called before we throw away a connection! [/quote] That’s something I recommend. Connections will automatically cancel when you release the last reference, but that makes cancellation somewhat non-deterministic, in that it’s easy for a reference to last much long that you might expect. And if you accidentally ‘leak’ a reference then the consequences are much worse if you don’t explicitly cancel. I also recommend that you nil out the various handlers installed on the connection. Without that, it’s easy to form a retain loop that prevents the auto cancellation. And even if you explicitly cancel, older versions of Network framework can still leave you with a retain loop. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We have added the following note: Tested on iOS 26.1 release: The following effects can be observed, if for the locale en-US, an Apple voice is selected (e.g. Evan): Speech Controller (Read & Speak -> Speak Screen -> Show Controller) play button reads with selected Apple Voice (i.e. not the Apple default voice Samantha) the Swift API method AVSpeechSnythesisVoice(language:) still returns Samantha (bug !) To observe the reported bug, you really need to install a 3rd party voice, i.e. a non-Apple voice. You can test it without subscription fee with e.g. Símarómur on the App Store: https://apps.apple.com/is/app/s%C3%ADmar%C3%B3mur/id6745481689 Install Símarómur, select the Steinn voice in Accessibility -> Read & Speak -> Voices -> English -> Steinn (en-US). Test functionality of voice via pressing Play Button inside the Settings (works). Then try to use the Speech Controller to read an English Text e.g. in the Safari browser -> Suddenly uses Samant