Apple Maps Guides

Thanks for your post, you mentioned you do not want to provide that information publicly. I suggest you continue this conversation with one of our DTS Engineers privately. If you have a focused sample you can share. To do so, please submit a code-level support request. When you create the request, indicate that you were referred by someone at Apple and make sure to include a link to this thread. Albert Pascual
  Worldwide Developer Relations.

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome Albert Pascual
  Worldwide Developer Relations.

Thank you for your post. Could you please provide more information? Are you unable to locate a crash file on your device using the sysdiagnose. Additionally, the post does not include the version of iOS or any other relevant details that would allow me to determine the cause of the crash. Could you utilize Xcode to debug the application and reproduce the crash? Providing additional information would be beneficial in guiding you to obtain the crash file. Kindly submit a comprehensive crash report, adhering to the guidelines outlined in Posting a Crash Report. Hope this helps: https://developer.apple.com/forums/thread/688669 Looking forward to figure it out. Albert Pascual
  Worldwide Developer Relations.

Thanks @azamsharp! That is almost definitely a bug with the guardrails. Can you file a Feedback report? In the Playground Canvas, on the far right of the Playground has encountered an error card, you should see a ! icon that will let you directly file a Feedback bug report. To help us track down the issue, would you also be willing to share your Siri language setting? That can be found in the Settings app > Apple Intelligence & Siri > Language. The guardrails have some language-specific behavior, so there's a known issue we're tracking where guardrails are over-triggering for some languages and locales.

Still hoping for an update on this. I have yet to receive a response within Apple Feedback.

[quote='861033022, DTS Engineer, /thread/802846?answerId=861033022#861033022'] I’m still researching the exact details of those limitations [/quote] Hey hey, that went quicker than I expected. As things currently stand on iOS 26, an app can only host extensions that it contains. Needless to say, this significantly undermines the utility of the ExtensionKit. While it’s possible that you might find a creative use for it, there’s one specific situation where it’s super useful, namely, using an extension to host code that is either unreliable or deals with untrusted data. For more on that last point, see Creating enhanced security helper extensions. There’s obviously a lot of demand from third-party developers to broaden the scope of ExtensionKit on iOS. If you have a specific use case in mind, feel free to file an enhancement request with the details. That’s particularly important if your use case is limited in some way. As I mentioned above, we already have an ER for the sort of general support we have on macOS

I’m not sure what you’re asking for here. Based on your contribution to other threads (like here), I get the feeling that you’re looking for a sample that shows how to communicate between iOS and Android apps. We don’t have such a sample, and it’s not something I’m create for you here on the forums. If you’d like to see that, please do file an enhancement request for it. And post your bug number, just for the record. If I’ve misunderstood your message, I’d appreciate more details on what you’re looking for. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not sure what you’re trying to convey with your latest reply. I’ve already: Explained that this is a bug. Recommend that you file a bug about it. Suggested a workaround that will at least allow your code to build. What else are you looking for? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860886022, interferon, /thread/802423?answerId=860886022#860886022, /profile/interferon'] I filed FB20484368. [/quote] Thanks. [quote='860886022, interferon, /thread/802423?answerId=860886022#860886022, /profile/interferon'] I was worried it was related to something in my code. [/quote] You are right to be worried here. While the problem isn’t with your code, the issue could affect your code. Lemme explain… Actually, that explanation got way too long so I’ve moved the first part of it here: Waiting for an Async Result in a Synchronous Function You can think of the unsafeForcedSync code as being like the mySynchronous(…) function from that post, except that it checks whether it’s being called from a Swift async function and logs if that’s the case. That log is not just noise: It tells you that you’re potentially exposing yourself to Swift concurrency thread pool exhaustion, and hence to a deadlock. But what you do about it is one of those classic engineering trade-offs. Do you leave it for Apple

Ah, I thought might be the case. The simulator works a bit like macOS, where Xcode sets things up so that your app can load a framework from the build products directory. That won’t work on a real device, where the framework must be embedded in the app’s bundle. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com