Cannot connect to iTunes sandbox

Same error here 😟

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

Same error here

{NSErrorFailingURLStringKey=https://sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, NSErrorFailingURLKey=https://sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, _kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4, NSLocalizedDescription=The request timed out.}}, NSErrorFailingURLStringKey=https://sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, NSErrorFailingURLKey=https://sandbox.itunes.apple.com/WebObjects/MZFinance.woa/wa/inAppBuy, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=Cannot connect to iTunes Store}

same error here

We are facing this issue in India. showing "Cannot connect to iTunes Store".

reason:Error Domain=NSURLErrorDomain Code=-1001 "Cannot connect to iTunes Store"

Getting same error in UK.

["NSLocalizedDescription": Cannot connect to iTunes Store, "_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, "NSUnderlyingError": Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}, "_kCFStreamErrorCodeKey": -2102]

It appears that the issue with sandbox testing affects some of you, but not everyone. It also turns out the the use the ping command can indicate a false positive for the problem. We’ve identified cases where the ping fails, but the In-App Purchase app is able to connect with the sandbox server and complete transactions.

In order to investigate this issue, the iTunes Server engineers have asked that bug reports be submitted with more complete information, including a sysdiagnose archive from the device. Such device will show additional information about the problem which a ping cannot.

First, here are the instructions to capture the sysdiagnose archive - please log into the Apple Developer Bug Report Profiles and log web page - <https:/

If you do this on the test device using the Safari browser, you can install the profiles to the device directly from the web site.

Install the following profiles

1. “App Store/iTunes Store for iOS” profile

2. “sysdiagnose for iOS” profile.

After all profiles are installed, please restart the device.

Please review the instructions for triggering the sysdiagnose profile and how to use iTunes to download the archive file by syncing with the device.

Make sure you are familiar with triggering the sysdiagnose log, then perform the steps to replicate the problem. When the failure occurs, trigger the sysdiagnose profile, wait 5 minutes, then sync the device with the iTunes app and find the sysdiagnose archive file. While reproducing the problem it will help to capture screenshots showing evidence of the connection failure.

To submit the bug report, please follow these instructions. Please use the Apple Developer Bug Report web page - http:/

After logging in, select the Product “Other”.

Fill out the bug report form. In the description section -

make sure to include the application ID

add a sequence of steps that a new user will take to use the app to find the In-App Purchase item

describe the evidence provided by the app that a network failure occurred. If there is a delayed response, indicate the approximate delay time.

Please include the sysdiagnose archive as an attachment to the bug report.

If you have a TestFlight build of the sandbox version of the app, please send an invitation to “apps_test@icloud.com”. Please include the bug report number in the invitation so that the test engineer knows which bug report to associate with the invitation.

Thank you for your assistance with this matter.

rich kubota - rkubota@apple.com

developer technical support CoreOS/Hardware/MFI

When I proxy the request using Charles, I see that the sandbox calls are succeeding but it is taking almost a minute for the response. I believe that the StoreKit api times out because the response is slow and therefore returns the "Cannot connect to iTunes Store" error

Submitted a bug report with the sysdiagnose files.

During the last year, I have suffered through many incarnations of this issue. For most of the year, I would typically get the "cannot connect to iTunes Store" message the first time when attempting an in-app purchase in the TestFlight environment. However, a second attempt would usually succeed.

In the last 2 months, things have deteriorated badly. The current situation with our app is that in-app purchasing works with some IAPs in the TestFlight environment and not with others. The experience from one TestFligtht user to another does not match. Tester A may be able to purchase IAP X while Tester B cannot.

In my case, it seems as though purchases that I successfully made many months ago cannot be made again while purchases that I successfully made recently can be repurchased.

In addition to the foregoing, we have not been able to use the "restore purchases" feature in TestFlight for the last year—althoug it works in the public version of our app.

A senior advisor with iTunesConnect asked me to send in the sysdiagnose archive. I followed all of the instructions and repeatedly attempted to generate the file using an iPad Pro. The file could not be generated. I have also provide a tester account.

Weeks are going by with no resolution and no direct contact with anyone who can comment directly on this matter. It's quite a disgrace, not to mention damaging to my efforts at business development.