Request failed with http status code 503

I suspect their is broad support for implementing a renewal status notification which is sent on every renewal of an auto-renewing subscription. I suggest that you submit an enhancement request for iTunesConnect to implement such support. You can submit the enhancement request using the Apple Developer Bug Report web page - http://bugreport.apple.com.rich kubota - rkubota@apple.comdeveloper technical support CoreOS/Hardware/MFI

I reread the docs and saw that the Feedback Service was listed in the Legacy Information section of the reference below. In that section, when a remote notification cannot be delivered because the intended app does not exist on the device, the feedback service adds that devices's token to its list. This information is returned in the connection. The new HTTP2 interface looks like it takes care of the feedback service as seen in one of the status codes available in the the request's response.In the section Apple Push Notification Service: Communicating with APNs, it has a status code for the APNs response: 410 The device token is no longer active for the topic.The whole point of the feedback service was to provide information on when to stop sending remote notifications that will fail to be delievered. This feedback is now available in the 410 status code.You don't need both services. The provider server should use the new HTTP2 protocol as the pre

ok I was able to do it with the API I followed a medium post called Generating JWT Tokens for App Store Connect API to get the signed JWT with my api key (apple won't let me link to it) https://medium.com/xcblog/generating-jwt-tokens-for-app-store-connect-api-2b2693812a35 2) then I went to the download codes link that failed and was able to get the ID from that (copy link address) e.g https://appstoreconnect.apple.com/iris/v1/subscriptionOfferCodeOneTimeUseCodes/#######/values (the ###### is the id) then I was able to make a request 3) > curl -X GET https://api.appstoreconnect.apple.com/v1/subscriptionOfferCodeOneTimeUseCodes/######/values --HEADER Authorization: Bearer KEY-GENERATED-IN-STEP-1 which spit out all of the codes you can add > codes to the end of command to write to a file called codes

When you use the URLSession convenience APIs the completion handler is called asynchronously. This works in normal apps because the app keeps running. In XCTest, however, the process running the tests terminates before the task completes. There are two ways you can tackle this: Using expectations Using Swift concurrency With expectations, you set up an expectation at the start of your task and then wait for it be fulfilled at the end. Then, in your completion handler, you fulfil the expectation. For example: func testWithExpectation() throws { print(did start test) let expectation = self.expectation(description: task completion) print(will start task) let url = URL(string: https://postman-echo.com/delay/3)! let request = URLRequest(url: url, cachePolicy: .reloadIgnoringLocalCacheData, timeoutInterval: 60.0) URLSession.shared.dataTask(with: request) { (data, response, error) in if let error = error as NSError? { print(task did fail, error (error.domain) / (error.code)) } els

Verify applecdn is available。 curl -v https://app-site-association.cdn-apple.com/a/v1/YourDomain eg. fail request curl -v https://app-site-association.cdn-apple.com/a/v1/www.123.com * Trying 59.108.139.130:443... * Connected to app-site-association.cdn-apple.com (59.108.139.130) port 443 (#0) * schannel: disabled automatic use of client certificate * ALPN: offers http/1.1 * ALPN: server accepted http/1.1 * using HTTP/1.1 > GET /a/v1/www.123.com HTTP/1.1 > Host: app-site-association.cdn-apple.com > User-Agent: curl/8.0.1 > Accept: */* > * schannel: remote party requests renegotiation * schannel: renegotiating SSL/TLS connection * schannel: SSL/TLS connection renegotiated * schannel: remote party requests renegotiation * schannel: renegotiating SSL/TLS connection * schannel: SSL/TLS connection renegotiated < HTTP/1.1 404 Not Found < Content-Type: text/plain; charset=utf-8 < Content-Length: