Request failed with http status code 503

Thanks for the post, I would recommend to look the information on the first error at the link provided on the error: https://developer.apple.com/documentation/bundleresources/ information_property_list/uisupportedinterfaceorientations. And also there is not entitlement supported for 'com.apple.developer.icloud-container-environment' and Xcode is letting you know to remove it. 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 let myEmail = eskimo + 1 +

I'll answer my own question. It turns out the solution is quite simple 😏. To fix this error, you need to reduce the size of the App Clip to less than 15 MB (I managed to do this by adding the -Osize parameter to the Swift compiler settings) and rebuild it for iOS 16. This is actually mentioned in the official documentation: https://developer.apple.com/documentation/appclip/choosing-the-right-functionality-for-your-app-clip

I saw it here, and it disappeared after I agreed. https://developer.apple.com/account

[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 … -[WKNavigationR

I'm experiencing a similar issue that occurs after an overlay installation and re-granting permissions to NEFilterDataProvider. Currently, I don't know how to resolve it. Similar issue: https://developer.apple.com/forums/thread/804992 https://developer.apple.com/forums/thread/803399

Thanks for bringing this to the forums. As a first step I recommend that you extract this code into a small test project and see if the problem reproduces there. Ideally that project would not be tied to the presence of a smart card, but instead display a test certificate that’s embedded in the app. If your test project reproduces the problem then none of the other code in your app is at fault, and that focuses the blame on SFCertificateView itself. In that case the next step is to file a bug against that API, making sure to include: A sysdiagnose log taken shortly after reproducing the problem [1]. Your test project. Please post your bug number, just for the record. As to a workaround, I very much doubt there is one, but that’s unlikely to be a problem. Unless this leak is huge, it’s unlikely to affect the user in practice because there’s a limit to how fast they can show and hide your certificate viewer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmai