Apple Maps Guides

Haven't been able to solve this one yet. I have some new evidence though. It appears there's difference in behavior between Intel and Silicon based systems. My machine is Intel, and most of my team is on Apple Silicon. We recently updated a couple of our build machines (Intel-based), and they started seeing the same issue. Our Apple Silicon machines do not see this issue. Our build machines were updated from: OS: Sonoma 14.5 -> Sequoia 15.7.1 XCode: 16.1 (or earlier) -> 16.4

If you'd like Apple to consider adding the functionality you have described, please file an enhancement request using the Feedback Assistant. If you file the request, please post the Feedback number here. Also, please review Apple's Unsolicited Idea Submission Policy. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review. For more information, see TN3186: Troubleshooting In-App Purchases availability in the sandbox.

Thank you for your post. I am not aware of any delays. Please give that team a few more days. If next week there is still no activity. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Hope this helps. Albert Pascual
  Worldwide Developer Relations.

I am working through the Apple Developer Foundations Models Code Along. Last week I successfully completed Chapter 1.6 and got the app to run with Generate Itenerary output. However, this week, I'm now getting a new error and the foundation model is now giving a console error that says Safety guardrails were triggered. If this is unexpected, please use LanguageModelSession.logFeedbackAttachment(sentiment:issues:desiredOutput:) to export the feedback attachment and file a feedback report at https://feedbackassistant.apple.com.

So, the tl;dr here is that this issue is now resolved. There may be other outstanding issues, but you can now: On a macOS 15 or later host, install macOS 15 or later in a VM. On the guest, log in using an Apple Account in System Settings. And install Xcode. And add your Apple Account to Xcode. And then build and run a Mac app. Even if it uses a restricted entitlement. If you’re interested in how I tested the above, I’ve included a summary at the end of this post. If you’re encountering other issues, please start a new thread with the details. This thread is already long enough |-: If you’re interested in the history, I have a summary of that in this post. That was from 13 Jun 2025. Since then there’s been one critical change, namely that on 9 Oct 2025 we rolled out a Developer website update that fixes the provisioning UDID issue (r. 149209127). And on that note, I think I can finally put this issue to bed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple

@swfitwave , Can you provide a little more context for that comment? Are you suggesting that command as a workaround? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='862780022, lucaDG, /thread/804615?answerId=862780022#862780022, /profile/lucaDG'] Following my Bug Report: FB20763245 [/quote] Thanks. I took a look at that and ran into a few problems: There’s no crash report. And no sysdiagnose log from which I might extract a crash report. You’ve attached what I suspect is a test project, but something went wrong with the attachment process because the zip archive is only 29 bytes long )-: And the code you posted above doesn’t compile )-: So, I created a new test project from the iOS > App templates and added your code to the test suite. With that I was able to trigger a crash, but it’s not clear that it’s the same crash you’re seeing. Specifically, the backtrace is quite different from the one you posted: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 JavaScriptCore … WTF::RunLoop::dispatch(WTF::Function&&) + 48 1 WebCore … WebCoreObjCScheduleDeallocateOnMainRunLoop(objc_class*, objc_object*) + 76 2 WebKit … -[WKNavigationResponse dealloc] +

I’m not sure what’s going on here, but it seems to be something specific to your project. Here’s what I did: Using Xcode 26.0.1 on macOS 15.7.1, I created a new test project from the iOS > App template, choosing SwiftUI for the UI. I modified the top of ContentView.swift to look like this: import SwiftUI import PhotosUI let something = PHPickerViewControllerDelegate.self I build the app for the simulator and the device. Both worked fine. My recommendation is that you repeat these steps. If those work for you, that’ll confirm that this issue is tied to your project rather than something environmental. I’ll also give you know good and known bad cases to compare. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com