“Request failed with http status code 503”

According to https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.7 6.5.7. 408 Request Timeout The 408 (Request Timeout) status code indicates that the server did not receive a complete request message within the time that it was prepared to wait. A server SHOULD send the close connection option (Section 6.1 of [RFC7230]) in the response, since 408 implies that the server has decided to close the connection rather than continue waiting. If the client has an outstanding request in transit, the client MAY repeat that request on a new connection. The client MAY repeat the request (I believe it does not have to be idempotent actually)! Because when safari tried to reuse a connection that determined to be closed during transit (in the server) but the client(safari) doesn't know yet (delay of microseconds) the transmission of data fails (socket is not open afterall the connection was closed), and so the request w

It’s better if you reply in as a reply rather than in the comments. See Quinn’s Top Ten DevForums Tips for more on that, and for lots of other hints and tips. My application is a GUI application, and my packaging adopts the Direct Distribution mode of Xcode. This is working for me. Here’s what I did: Using Xcode 16.1, I created a new project from the macOS > App template template. In Signing & Capabilities, I enabled App Sandbox > Outgoing Connections (client). I modified the content view to issue a request to a server on my local network. The exact code is below. I ran this on my main Mac and confirmed that it worked there. I chose Product > Archive. In the Xcode organiser, I clicked Distribute App and followed the Custom > Direct Distribution > Export workflow. I copied the app a ‘clean’ VM running macOS 15.1. On that VM, I launched the app from the Finder. I clicked Test. The system presented the Local Network alert. I clicked Allow. Back in the app, the status

I am also facing the same issue please provide some solution for it.Following output i am getting2018-03-29 20:59:07.733425+0530 MyApp[617:181515] TIC Read Status [28:0x1c436a140]: 1:602018-03-29 20:59:07.733994+0530 MyApp[617:181515] Task <7224DF11-4CDB-480D-907D-ADEBC425ABAB>.<0> HTTP load failed (error code: -1001 [1:60])2018-03-29 20:59:07.734178+0530 MyApp[617:181702] NSURLConnection finished with error - code -10012018-03-29 20:59:22.418536+0530 MyApp[617:181627] TIC Read Status [19:0x1c0362c40]: 1:602018-03-29 20:59:22.420972+0530 MyApp[617:181627] Task <311A377E-1CD9-4BF3-8074-3C0FBA087A97>.<0> HTTP load failed (error code: -1001 [1:60])2018-03-29 20:59:22.422615+0530 MyApp[617:181517] NSURLConnection finished with error - code -10012018-03-29 20:59:28.955711+0530 MyApp[617:181517] TIC Read Status [30:0x1c036c6c0]: 1:602018-03-29 20:59:28.958396+0530 MyApp[617:181517] Task <B17

Nothing like a public question to un-wedge the debugging muscle. Debugging this some more, I found that I had not run with DEBUG=electron-notarizer, and turning that on, shows the following output: 2021-12-23T19:09:25.522Z electron-notarize notarizing using the legacy notarization system, this will be slow An unhandled rejection has occurred inside Forge: Error: Failed to upload app to Apple's notarization servers *** Error: Notarization failed for '/var/folders/w8/hsj6918d0fsb8hxb127hqgp00000gn/T/electron-notarize-JveOtm/CloudInstance.zip'. *** Error: Unable to upload your app for notarization. Failed to get authorization for username 'jwatte@observeinc.com' and password. ( Error Domain=NSCocoaErrorDomain Code=0 Status code: 0 UserInfo={NSLocalizedDescription=Status code: 0, NSLocalizedFailureReason=The auth server returned a bad status code.} ) (-1011) { NSLocalizedDescription = Unable to upload your app for notarizati