Re: iTunes Sandbox Extremely Slow

Same issue here. Any update about the sandbox status?

We are seeing the same issue as well. The sandbox very slow to return product prices, make purchases, and restore purchases. It also repeatedly asks us to verify our Apple ID in the Settings app, even though it is just a sandbox user. We have been working with IAPs for years and have never run into these kinds of issues.

Same issue here...

Hi, today we're seeing a very erratic behavior from the IAP sandbox.

For some time,purchaes take way too long and trigger timeouts and then, after a while, they start responding fast, then back to long waiting times.

It doesn't seem like this website is 100% trustworthy...

https://developer.apple.com/system-status/

Did you guys find any work around /fix ?

Same issue here.

It's nightmare as I can't debug my app even in TestFlight build.

I found a similar issue, but this have been left for over one year...

https://forums.developer.apple.com/thread/75076

Same here. Really slow connection for the itunes sandbox environment. I've opened a bug and it was closed as a duplicate. Hopefully it's going to be fixed soon.

I have same problem. 2 days ago it worked, but now it does not work.

I can not test in-app purchase feature in sandbox environment(TestFlight) before release app.

SKProductsRequest returns an error in sandbox environment.

The error is:

Error Domain=SSErrorDomain Code=109 "Cannot connect to iTunes Store" UserInfo={NSLocalizedDescription=Cannot connect to iTunes Store, SSErrorHTTPStatusCodeKey=404}

Same for me. about 80% of request fail. 2700 tests constantly in failed state with same timeout....

Since yesterday morning is same for me!

From PHP i use https://sandbox.itunes.apple.com/verifyReceipt, very slow but works.

From iOS in iTunes sandbox ,  is extremely slow and about 90% of requests fails. Most of times i get:

Error Domain=NSURLErrorDomain Code=-1001 "Imposible conectarse a iTunes Store" UserInfo={NSUnderlyingError=0x1c0647a40 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, NSErrorFailingURLKey=https://p100-sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=Imposible conectarse a iTunes Store}

Same here. We've been having problems for some time now. Today it has been almost impossible to succeed a purchase in TestFlight beta. Also the iTunes sign in prompt shows in erratic fashion, sometimes in a loop. Sometimes the sign in promp appears even if the tested app is closed. This puts our pipeline pretty much to a halt.

Same issue for me. After few tries it seems to work well for some time. I thought there is a problem in my code, even I've not changed it

This bug also seems to cause the device to keep requesting for sanbox login. I just reset my iPhone and restored a recent backup and guess what. It wants my password to process some sandbox crap. So the failure is stored into a backup.This bug not only destroys your production line, it also corrupts your device.

I'm ATM unable to create even a bug report because the device just keeps asking for the password for the sanbbox purchases. It looks like there's an endless supply of previously failed purchases in some queue.

I have the same issue. Somethimes it working but I have more failure than success

Transaction Failed with error: Error Domain=SKErrorDomain Code=0 "Cannot connect to iTunes Store" UserInfo={NSLocalizedDescription=Cannot connect to iTunes Store}

...

This issue appears to be happening quite frequently as well. All Sandbox purchases that were attempted today are now timing out.

I'm looking for some suggestions on how to proceed.  Are there any workarounds?  It has been going on for so long that I am not sure how to move forward.  Are people simply releasing into the production environment and hoping for the best?

March 20th.

Have several devices - for hours the same result, not able to connect to IAP sandbox AT ALL.

Tried multiple times, multiple devices, over a period of multiple hours. Always unable to connect to iTunes store.

Totally ridiculous, IAP sanbox has always been a joke and totally fragile, just ridiculous.

I have the same issue.

Even when open the sandbox verify receipt link in the browser it is very slow.

while it is very fast in the production link

https://sandbox.itunes.apple.com/verifyReceipt

https://buy.itunes.apple.com/verifyReceipt

Nice, I thought I was going crazy because the same code was working fine before... submitted a bug report too as suggested by the apple engineer. The bad thing is our app has been rejected now for three times because of their bug and we cannot get patches in...

Good afternoon. Previously, there were problems with payments - it took a lot of time, most often on the client were given a error about incorrect payment data, in 9 out of 10 cases. Today, suddenly, the payment began to work very quickly. What has changed? Did you fix it?

Thank you.

I'm back to borderline unusable and ping's failing .

ping -c 5 sandbox.itunes.apple.com

PING sandbox.itunes-apple.com.akadns.net (17.154.66.159): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

--- sandbox.itunes-apple.com.akadns.net ping statistics ---

5 packets transmitted, 0 packets received, 100.0% packet loss

I'm having the same issue everyone else in this thread is. I can sometimes get an IAP to successfully go through in the Sandbox, but it is very, very slow. I'm working on code right now for a feature where I need to be able to hit verifyReceipt and get a usable response, but that is never working no matter how many times I try.

Here's the Terminal output from the ping rich from Apple mentioned trying:

$ ping -c 5 sandbox.itunes.apple.com

PING sandbox.itunes-apple.com.akadns.net (17.154.66.159): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

--- sandbox.itunes-apple.com.akadns.net ping statistics ---

5 packets transmitted, 0 packets received, 100.0% packet loss

Same issue. And the App review team reject us with 2.1 Performance, because IAP failed

I am also having network problems connecting to sandbox.itunes.apple.com.

Going to contact apple tech support.

I'm experiencing the same problem.

App successfully gets the list of in-app purchases.

Than asks AppleID/Password only 1 of 30 times

And gets unknown error(SwiftyStoreKit). (kCFErrorDomainCFNetwork - "Cannot connect to iTunes Store" 0x00000001af03d138)

It worked fine about a week ago.

It goes to "confirm in-app purchase" if I login with real(not sandbox) iTunes account.

But than also gets an error.

And now I'm requested to submit a video of in-app purchase process, but I can't.

MacBook-Pro:~ user$ ping -c 5 sandbox.itunes.apple.com

PING sandbox.itunes-apple.com.akadns.net (17.154.66.159): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Same here in Hong Kong. It's basically unusable

Sandbox testing is working fine now!

Thank you!

Working on server-side receipt validation myself. Seeing random Sandbox response times (2s to 180s) and many connection reset errors (ECONNRESET). Ping results in timeouts as well.

It's the same for me in Sweden. My binary got rejected in review because the IAP fails due to Apple's sandbox server...

Same here in San Francisco. All our games cannot be tested which is blocking release.

Created a bug report with a client log and ping results.

OK Guys!! I think I'm up to something here... Turns out, if I activate my test account, It seems it doesn't hang any more. Or Apple in her great majesty, fixed our sandbox. Either way, my last two purchases went through some what ok.

Although, A better error than '0 "Cannot connect to iTunes Store"' would be nice!!!!

cheers!

Same here.
ping sandbox.itunes.apple.com fails now

Same extremely low performance issue here, in Brazil. Cannot test StoreKit functionalities because of Itunes Sandbox no availability.

Trying ping the server:

Flying-Fortress:~ marcelmendesfilho$ ping -c 5 sandbox.itunes.apple.com

PING sandbox.itunes-apple.com.akadns.net (17.154.66.159): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Xcode messages while app's waiting for a response from sandbox server when trying to validate a receipt:

validateAppReceipt() the upload task returned an error: Optional(Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={NSUnderlyingError=0x1c8041140 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 "(null)" UserInfo={NSErrorPeerAddressKey=<CFData 0x1c4096ad0 [0x1b4669538]>{length = 16, capacity = 16, bytes = 0x100201bb119a429f0000000000000000}, _kCFStreamErrorCodeKey=-4, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://sandbox.itunes.apple.com/verifyReceipt, NSErrorFailingURLKey=https://sandbox.itunes.apple.com/verifyReceipt, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-4, NSLocalizedDescription=The network connection was lost.})

2018-04-18 08:02:35.574765-0300 Canário[14466:7422871] Task <2E837F50-7B1D-4CEB-BBC2-29904827ABCC>.<1> finished with error - code: -1001 validateAppReceipt() the upload task returned an error: Optional(Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x1c0240150 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://sandbox.itunes.apple.com/verifyReceipt, NSErrorFailingURLKey=https://sandbox.itunes.apple.com/verifyReceipt, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.})

Yesterday I wasn't able to make a purchase in sandbox environment. Receiving "Cannot connect to ITunes Store. Try later." all afternoon (GMT -3). Tried 6+ times with no success. Gave up and tried 4 hours later. Got 1 answer, all others failed.

What's happening?????

Please solve this!! I'm wasting a time I cannot afford on this!

I've opened a bug report: 39523855

Marcel

Same here.

$ ping -c 5 sandbox.itunes.apple.com

PING sandbox.itunes-apple.com.akadns.net (17.154.66.159): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

--- sandbox.itunes-apple.com.akadns.net ping statistics ---

5 packets transmitted, 0 packets received, 100.0% packet loss

Looks like Apple is rotten.

Although the system status at https://developer.apple.com/system-status/ is showing as Issue Resolved,

Still sandbox services are slow.

Trying since Two day...loosing precious business days...hope Apple is listening...

Same here. Can't use sandbox for last two days. I even rebuilt my current live app (where purchasing works) with ABSOLUTELY no changes other than switching to sandbox and it constantly gets cannot connect to appstore error.

When iterating the products list to register them - it registers the first product - then fails the minute it tries to register the .when callbacks for it.e

I've built with xcode 8 and xcode 9 with the same results.

I'm preparing to submit an official bug report but I can't see how this can be anyone's problem except Apple. If they're using their own sandbox with no issues then perhaps it's a regional DNS issue. I can no longer ping the sandbox address at all (and could previously)

But seeing people say that they are being rejected because of sandbox issues that seems like reviewers are seeing the same problem.

Slow sandbox testing here too almost non exsitant. Getting frustrating not being able to reliably test purchases and then have apple reject because they cant test them.

Seems to have been resolved for me as of Today 12:30 PM PT.

Failed on second attempt, but all subsequent attempts have been successful.

Sometimes works, sometimes errors... Unreliable at the moment

Again sandbox services down....

its too much...