“Request failed with http status code 503”

I'm developing an ACME server to issue identity certificates to macOS/iOS devices for MDM attestation, following RFC 8555. Per RFC, the client creates an order, performs authorization, verifies the challenge, and finalizes the order by submitting a CSR to the CA. In my setup, the CA sometimes takes longer to issue the certificate (around 50 seconds). According to RFC 8555, if certificate issuance isn’t complete after the /finalize call, the server should respond with an order object with a processing status. The client should then send a POST-as-GET request to the order resource (e.g., /order/) to check the current state. If the CA still hasn’t issued the certificate, the server should return the order object with the same processing status and include a Retry-After header, indicating when the client should retry. The client is expected to poll the order resource at this specified interval with POST-as-GET requests. However, it seems the Apple ACME client ignores the Retry-

Hi all, Every year about 20 or 30 fee-paying developers attempt to notarize their mac apps and during the process they get a rejection response that says Status Code 7000: Team ID not yet configured for notarization. No one has ever been able to get their team ID configured for notarization if they get hit by the 7000 status code error. Every month we get 5 or 6 new posts by people saying they got hit with it, and NEVER once has anyone posted a follow-up that they had the issue resolved. As Apple Engineers, can you provide any insight into this problem?

hi, since yesterday I'm getting 503 error in my process. I'm using API v3: https://api.searchads.apple.com/api/v3/search/apps?returnOwnedApps=true but my cert are not expired yet. Could you please confirm it is still ok to use API v3. API v4 is also based on domain api.searchads.apple.com and on a site which I use to check if url is up or not: https://www.isitdownrightnow.com/ I'm getting response that service is unavailable so even API v4 is affected? Does anyone else is also having problems to connect to API v3 or API v4?

I am getting the following error: Code signing INFOnlineLibrary.framework failed. I can not release my app.

Having resolved the previous problems with code signing my evaluate now fails considerably later with code sign failed with non zero code. Anyone give me a hint for this please?

Hello All, I'm in the process of adding new screenshots for our product page. I deleted all watch related screenshots from both languages to add the new ones. It worths noting that the older screenshots that I deleted were taken from Watch Series 4, the new ones on the other hand are from Watch Series 6. What happens is that the upload starts, then immediately the process gets stuck with no conclusion on the UI of App Store Connect. So I checked the console from Safari here is the result: terrors : [ { ttid : ae556f72-dd1e-45b6-93c6-7b5ef6f17cab, ttstatus : 409, ttcode : STATE_ERROR, tttitle : The request cannot be fulfilled because of the state of another resource., ttdetail : Screenshot Set Already Exists! t}, { ttid : cfc6190c-35da-4e76-a22b-5c36930a5674, ttstatus : 409, ttcode : STATE_ERROR, tttitle : The request cannot be fulfilled because of the state of another resource., ttdetail : Screenshot Set with type WATCH_SERIES_4 Already Exists! t} ] } Unfortunately I can't see any screenshot

We have an app that is partly powered by a WKWebView. For various reasons irrelevant to this question, we're using a local webserver to serve content and act as a proxy to the WKWebView. The local web server is http (and not easily changed to https). The webview's baseURL is https. In iOS 8, we received console warnings about loading insecure content (as expected). In iOS 9, it appears the requests to the local webserver are sometimes blocked, and sometimes not, as indicated in the screenshot here: http://d.pr/i/11Tvy/36DWnMtt+Most are marked as [blocked], however the second one is not, even though nothing from the warning would indicate why that one would be allowed through and the others not.Is there any insight as to why some requests are blocked and not others, or under what conditions a request is blocked?To be clear: I'm very aware of why this warning is being printed, and why loading http from https could be a bad idea. I'

Hi, I would like to create a class with 4 parameters : IoT IP address and 3 additional strings received from the http request. the constructor will receive an IP address and create a class member with the IP address and additional 3 strings received from the request. Appreciate anyone help. Thank you.

Hi,We are facing an issue where the launch daemons fails to work with the authenticating proxy configured in System Preferences.We tried both NSURLConnection and NSURLSession APIs and both fails with following error:Error with NSURLConnection:Error Domain=kCFErrorDomainCFNetwork Code=311 There was a problem establishing a secure tunnel through the web proxy server. UserInfo={NSErrorFailingURLStringKey=https://google.com/, NSErrorFailingURLKey=https://google.com/, _kCFStreamErrorCodeKey=-2097, _kCFStreamErrorDomainKey=4, NSLocalizedRecoverySuggestion=Please check your proxy settings.For help with this problem, contact your system administrator., NSLocalizedDescription=There was a problem establishing a secure tunnel through the web proxy server.}Error with NSURLSession: Error Domain=kCFErrorDomainCFNetwork Code=311 (null) UserInfo={_kCFStreamErrorCodeKey=-2097, _kCFStreamErrorDomainKey=4}Same binary works fine when run as command line tool with this proxy c

Hello there,When I want to distribute my .ipa file, I'm getting code signing failed error at the end of process.The distribution standard log: code = 306; description = Failed to resolve rpath for Alamofire: Could not resolve @executable_path for @executable_path/Frameworks from Alamofire; info = { }; level = WARN; }, { code = 306; description = Failed to resolve rpath for SwiftKeychainWrapper: Could not resolve @executable_path for @executable_path/Frameworks from SwiftKeychainWrapper; info = { }; level = WARN; }, { code = 330; description = Failed to resolve linkage dependency SwiftKeychainWrapper i386 -> @rpath/libswiftCore.dylib: Unknown arch i386; info = { }; level = WARN; },The distribution pipeline log:2018-09-22 21:17:51 +0000 /var/folders/tm/1dmb5cd92zx5txhhfz_5jbpm0000gn/T/XcodeDistPipeline.gwn/Root/Payload/MyApp.app/Frameworks/SwiftKeychainWrapper.framework: code object is not signed at all2018-09-22 21:17:51 +0000