Search results for

Request failed with http status code 503

191,139 results found

Post

Replies

Boosts

Views

Activity

Reply to I'm currently using macOS 26 and Xcode 26, but I'm unable to download iOS 26 simulators.
I wanted to follow up on my previous message regarding the simulator download issue in the latest Xcode. I’ve already provided all the requested details, but I haven’t received any update yet. To be honest, I’m becoming increasingly frustrated with the lack of response and progress. This issue has completely blocked my development work — I’m unable to run or test any iOS projects until this is resolved.
1w
SwiftUI TextField selection - strange initial values with iOS
When using a TextField with axis to set to .vertical on iOS, it sets a bound selection parameter to an erroneous value. Whilst on MacOS it performs as expected. Take the following code: import SwiftUI @main struct SelectionTestApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct ContentView: View { @FocusState private var isFocused: Bool @State private var text = @State private var textSelection: TextSelection? = nil var body: some View { TextField(Label, text: $text, selection: $textSelection, axis: .vertical) .onChange(of: textSelection, initial: true) { if let textSelection { print(textSelection = (textSelection)) } else { print(textSelection = nil) } } .focused($isFocused) .task { isFocused = true } } } Running this on MacOS target gives the following on the console: textSelection = nil textSelection = TextSelection(indices: SwiftUI.TextSelection.Indices.selection(Range(0[any]..<0[any])), affinity: SwiftUI.TextSelectionAffinity.downstream) Running the code on iO
2
0
111
1w
How to debug SecurityAgentPlugins?
Hi, I’ve developed a custom Authorization Plugin and placed it under: /Library/Security/SecurityAgentPlugins/AuthPlugin.bundle I also updated the corresponding right in the authorization database (authorizationdb) to point to my plugin’s mechanism. However, when I invoke the right, my plugin does not get loaded. The system log shows the following errors: AuthorizationHostHelper: Init: unable to load bundle executable for plugin: AuthPlugin.bundle AuthorizationHostHelper: Processing request: Failed to create agent mechanism AuthPlugin:auth.startup.authenticate, failing authentication! Here’s what I’ve verified so far: The plugin bundle and its executable are signed and notarized successfully. The executable inside the bundle is universal (arm64 + x86_64). The bundle structure looks correct (Contents/Info.plist, Contents/MacOS/..., etc.). Despite that, the plugin fails to load at runtime. Could anyone provide advice on how to debug or trace why the SecurityAgent cannot load t
1
0
36
1w
Reply to App ID Prefix Mismatch When Updating Old iOS App (2010) - "An App ID with Identifier is not available"
[quote='805344021, PeterAndela, /thread/805344, /profile/PeterAndela'] Can I reuse the existing App ID … for a new provisioning profile … ? [/quote] Yes. While unique App ID prefixes are deprecated, they still work. So, there are two paths forward here: You can continue to use the unique App ID prefix. You can transition to using your Team ID as your App ID prefix. The latter has various pros and cons. Most notably: It enables various nice-to-have features, like keychain item sharing between apps from your team, clipboard sharing between apps from your team, and so on. It allows you to publish a Mac version of the same app. It ‘breaks’ access to any existing keychain items. See App ID Prefix Change and Keychain Access. If you decide to make the transition, you can’t do it via the Developer website. Rather, you have to raise a support request. See Apple > Developer > Contact Us. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Reply to Provisioning doesn't do case-insensitive match
You post reads like a bug report, and it would be perfectly reasonable for you to file a bug requesting either of these changes. If you do, please post any bug numbers, just for the record. In terms of workaround, the simplest option would be to create a new VM. That’ll get a new provisioning UDID, which will be registered with the correct case. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
Provisioning doesn't do case-insensitive match
According to the thread at https://developer.apple.com/forums/thread/787500?answerId=863361022#863361022, we should now be able to set VMs provisioning identifiers to run developer builds. However, the identifier check seems to be case-sensitive. I have an identifier from an old VM that was input (automatically via Xcode) to the portal as all-caps. However, now it's showing up as all lower-case (on the device). When I try to launch my application, the system logs report that the provisioning identifer doesn't match, so my application will not launch: # Error log error 13:41:36.173151-0600 taskgated-helper embedded provisioning profile not valid: file:///Applications/my-app.app/Contents/embedded.provisionprofile error: Error Domain=CPProfileManager Code=-212 Provisioning profile does not allow this device. UserInfo={NSLocalizedDescription=Provisioning profile does not allow this device.} # Device's identifier $ system_profiler SPHardwareDataType Hardware: ... Provisioning UDID: 9d136dc4ae3ce8
1
0
100
1w
Reply to Performance issues when using the Network API used to create a web server
Hi Quinn, Thank you for getting back to me. Yes I do mean macOS 26 or macOS 15. Earlier macOS versions do not show the issue. Note that we only tested with macOS 15.6.1, macOS 26.0.1 and macOS 26.1 beta 3 and 4. In the sample code and instructions that I provided, we can reproduce it with curl, but we have seen the issue first in our code where we use URLSession. Let me know if you need additional information. Pierre
Topic: App & System Services SubTopic: Core OS Tags:
1w
Present User an error message when SwiftData save fails
Have a data model that sets certain fields as unique. If the user attempts to save a duplicate value, the save fails quietly with no indication to the user that the save failed. The program is on Mac OS 26.0.1 @Environment(.modelContext) var modelContext @Query private var typeOfContracts: [TypeOfContract] @State private var typeName: String = @State private var typeCode: String = @State private var typeDescription: String = @State private var contracts: [Contract] = [] @State private var errorMessage: String? = Data Entered @State private var showAlert: Bool = false var body: some View { Form { Text(Enter New Contract Type) .font(.largeTitle) .foregroundStyle(Color(.green)) .multilineTextAlignment(.center) TextField(Contract Type Name, text: $typeName) .frame(width: 800, height: 40) TextField(Contract Type Code, text: $typeCode) .frame(width: 800, height: 40) Text(Contract Type Description) TextEditor(text: $typeDescription) .frame(width: 800, height: 200) .scrollContentBackgrou
10
0
247
1w
Reply to Wallet Extension show tips "Cannot Add Card"
Hi @Mars.liu, The Apple Pay servers are purged frequently due to privacy and security policies, so I'll need both to follow the steps in the post below, then reply to this thread once you've created a Feedback report: Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues https://developer.apple.com/forums/thread/762893 Once you've submitted your Feedback with the requested details listed in the post above, I'll be able to provide guidance for you to resolve the reported errors, as well as troubleshoot your implementation and PNO metadata configuration, as needed. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
1w
In App Provisioning PKErrorHTTPResponseStatusCodeKey=500
Hello, we are developing in app provisioning of our American Express network cards. After clicking add to apple wallet in our app, I launch the PKAddPaymentPassViewController and click next. It loads for a few seconds and then I get: [] ProvisioningOperationComposer: Step '' failed with error Error Domain=PKProvisioningErrorDomain Code=5 UserInfo={PKErrorHTTPResponseStatusCodeKey=500} Does anyone have any insight on what this error means?
2
0
665
1w
Reply to In App Provisioning PKErrorHTTPResponseStatusCodeKey=500
Hi @nikhypercard, The Apple Pay servers are purged frequently due to privacy and security policies, so I'll need both to follow the steps in the post below, then reply to this thread once you've created a Feedback report: Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues https://developer.apple.com/forums/thread/762893 Once you've submitted your Feedback with the requested details listed in the post above, I'll be able to provide guidance for you to resolve the reported errors, as well as troubleshoot your implementation and PNO metadata configuration, as needed. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
1w