“Request failed with http status code 503”

I found that Xcode 7.3 is no longer able to launch unit tests requiring iOS simulator. Xcode 7.2.1 was able to. I am seeing this with GitLab-CI and using a runner on my iMac where I updated to Xcode 7.3 two days ago:You now get the error message after the unit test build:Failed to authorize rights (0x1) with status: -60007.For some reason OS X now requires some user interaction when launching the simulator which is not possible because there is no interaction allowed, the runner runs as daemon. If you google for this message then you find solutions related to the keychain. But in this case no code signing occurs since this is a simulator build.Anybody know how to work around the issue? Is that an Xcode 7.3 bug?cheersOliver

Hello, I am well aware from searching and reading other members' posts that NSURLConnection is going to be deprecated starting iOS 9 and replaced with NSURLSession. I am also aware that NSURLSessions cannot make requests to http domains without modifying the info.plist file. However, when I was using the previous version of iOS9 (beta 3), I was able to successfully use NSURLConnections to make requests to http domains without being blocked by ATS. After upgrading to beta 4, even NSURLConnection requests are being blocked.Is this intentional as part of Apple's movement to only support HTTPS requests, or will I be able to make http requests without modifying info.plist as long as I use NSURLConnections?Thanks

The documentation says Server errors are not reported through the error parameter. The only errors your delegate receives through the error parameter are client-side errors, such as being unable to resolve the hostname or connect to the host, but on iOS8.3 and 8.4 we're finding that non-successful HTTP status response codes are being translated into NSError objects.For example if the HTTP repsonse is a 404, the error parameter is an instance of:Domain=NSURLErrorDomain Code=-1100 The requested URL was not found on this server. UserInfo=0x17347f0c0 {NSErrorFailingURLKey=..., NSLocalizedDescription=The requested URL was not found on this server., NSErrorFailingURLStringKey=...This does not happen on iOS9. On iOS9 the error parameter is nil for a 404 HTTP response.Is this a bug in NSURLSession on iOS8? Or is there something I'm doing wrong?

Having an issue today where archives on Xcode Cloud are failing at the Code Signing step. The error reported by Xcode Cloud has been one of the 2 following: 502 error from developerservices2.apple.com Unexpected character 'u' (I assume this is in some way related to the HTTP failure above, but please correct me if I'm wrong) Sometimes they even appear together, with the HTTP error as a warning and the unexpected character as the error I assume this is some kind of Xcode Cloud / developer tools outage. I saw another post on the forum from 3 weeks ago that reported the same errors coming from Xcode Cloud. I also saw that there is a Resolved Outage with Xcode Cloud from 8/19 (maybe that is related)? Has anyone found a way around this? Any updates on when this will be resolved? It has been happening for us consistently since the first Xcode Cloud archive that we ran today (around 10AM EDT).

My app has consumable in-app purchase products. The app is using Original API for In-App Purchase. When the user purchase in-app product, the app sends the receipt to our web server which then validates the receipt throw the App Store api. The App Store validates the receipt and gives us the response with a status code. The problem is here. It's obvious how to handle a 'valid receipt' response status code which is 0. But the document is not straight about handling response code which isn't 0. Should we call finishTransaction when the response code isn't 0? or should we not? If we don't call finishTransaction, we are worried that the transaction will stay alive and loop forever. If we call finishTransaction, we are worried that we might ignore a valid purchase and not give the consumable product that user purchased. Is there a right way to handle this? Original API for In-App Purchase: https://developer.apple.com/documentation/storekit/in-app_purch

Every time I try to upload a app to App Store Connect Code signing OSM.app failed. this happens when ever I try to every app

When I test an in-app purchase with the sandbox the post request to the sandbox url https://sandbox.itunes.apple.com/verifyReceipt returns data: { environment: 'Sandbox', status: 21003 } Is this expected? I'd assumed my test receipt would be considered valid for the sandbox environment and return a status of 0.

I have my IAP setup all working, but one thing I am not sure about is how to react to each of the status codes that can be generated for Receipt Validation on the server.Status of 0 is success. That is clear, but of the others, which ones say conclusively This is definitely not a valid receipt? Seems like a fundamental question, but it is not clear to me from the docs: https://developer.apple.com/library/content/releasenotes/General/ValidateAppStoreReceipt/Chapters/ValidateRemotely.htmlEg.21002 is clearly a problem with the request, so doesn't necessarily mean the receipt is false.21005 is clearly not a receipt problem.21007 and 21008 are simply asking the wrong server, not a receipt problem.21010 does seem to indicate the receipt is invalid.21003 says the receipt could not be authenticated. Does that mean the user mistyped their password? Or is this, just like 21010, conclusive proof the receipt is invalid?Thanks in advance.Drew

Hello.I am to use wifi connection without http, https only.My SKProductsRequest failing with error: “Cannot connect to the iTunes Store”description:{ NSErrorFailingURLKey = http://sandbox.itunes.apple.com/bag.xml?ix=6&os=10&locale=en_EN; NSErrorFailingURLStringKey = http://sandbox.itunes.apple.com/bag.xml?ix=6&os=10&locale=en_EN; NSLocalizedDescription = Cannot connect to iTunes Store; NSUnderlyingError = Error Domain=kCFErrorDomainCFNetwork Code=-1001 (null) UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}; _kCFStreamErrorCodeKey = -2102; (long)72057594037925834 _kCFStreamErrorDomainKey = 4;}NSErrorFailingURLKey and NSErrorFailingURLKey contain http host instead https. Why http? How fix it?If switch to wifi connection with http then SKProductsRequest succefully.ipad. sandboxios 10.0.1xcode 8.1Thanks

I created a code level support request over a month ago and have not heard anything back about it. I am wondering if I missed an email or something. I had thought that the page listing my cases would have a link showing the history of my request including the original request info but all I see is a list containing 2 items:Case ID: 673523773 CREDITRequested by: <email>Created: September 19, 2017Case ID: 673523773 USERequested by: <email>Created: September 18, 2017How do you get more details on your case id?What does 'Credit' and 'Use' mean here?Is there some documetation some where explaining this?

I am trying to do merchant validation in Java. Before that, I completed these steps:- Registered Merchant Id, generated CSR, created merchant id and payment processing certificates. Registered and verified domain & allowed Https connection to sandbox IPs on port 443 and whitelisted IPs for domain verification. generated validation Url , using it to create ApplePay Payment Session. Below is a snapshot of my code: String file=classLoader.getResource(/merchant.p12).getFile(); FileInputStream fileN=new FileInputStream(file); clientStore.load(fileN,keyStorePassword.toCharArray()); KeyManagerFactory kmf = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm()); kmf.init(clientStore, keyStorePassword.toCharArray()); KeyManager[] kms = kmf.getKeyManagers(); SSLContext sslContext = null; sslContext = SSLContext.getInstance(TLSv1.2); sslContext.init(kms, null, new SecureRandom()); HttpsURLConnection.setDefaultSSLSocketFactory(sslContext.getSocketFactory()); URL url= new URL(validati