"Cannot connect to iTunes Store" in apps

I'm having problems testing my in-app purchases. I return valid product identifiers, but when I buy, I get the scary "Cannot connect to the iTunes Store." Interestingly, recovery attempts seem to work - the iTunes icon appears.

At me: - It is checked that my purchases in the application are deleted for sale - It is checked, it is verified that my source code is synchronized with the Apple documentation - Suitable test users are added - the application identifier does not contain a template - purchases in the application are associated with the application (the application itself is located in deviation from the developer, purchases are ready to be sent) - waited - reinstalled application, cleared solution, all voodoo materials

+55
ios cocoa-touch in-app-purchase
Sep 13 2018-11-11T00:
source share
8 answers

Make sure you are signed out of any production iTunes accounts on your device.

I was getting this error on my test phone that was logged in with my actual iTunes account. You cannot test applications using your iTunes account, and therefore an error. I just want Apple to provide the best mistake to avoid this hunch ...

+73
Dec 02 '12 at 3:40
source share

see App Purchase FAQs: Cannot Connect to iTunes Store

Your app is running in the Simulator, which does not support In-App Purchase 

For testing when buying applications, always use real devices.

+25
Dec 17 '13 at 15:51
source share

For beginners, make sure your purchase product status is in the Ready to Submit app, with no "missing metadata." In my case, there was no localization of the subscription group.

enter image description here

+9
Nov 16 '16 at 12:48
source share

I had this problem and am convinced of its error. I filed an error message with error message 10108270

The problem is that the test user gets "blocked" and may have something to do with trying to purchase an application in an already released application with this account.

My workaround was to create a new test user, but until Apple comes back to me, I cannot offer any better solutions. I will update this answer when I receive answers.

+5
Sep 13 2018-11-11T00:
source share

I'm doing the same thing. For me, this happens after this sequence:

  • Install the application on a device registered with a UK account in iTunes.
  • Launch the application and use a test user in the USA.
  • A message is displayed stating that the account is only valid in the United States. Closes the application and automatically launches iTunes
  • Open the app and try again. Receive products, but there is no other callback or error.

I don't know if this is an issue on the IAP platform, but I would like to get an error / callback to somehow handle it in my code.

To continue testing your IAPs, follow these steps:

  • Delete the Provisioning Profile in the settings area, uninstall the application and exit the "Save to Settings" menu. Then go to Xcode and change the signature IDs to β€œDon't Know” and then return them (I know how that sounds :), but try) OR
  • Hard reset all settings on your device (Settings β†’ General ...). Obviously, you will lose all settings on this device ...
  • Kill the iTunes application on the device (multitask menu) and exit the store in the settings

If none of the above works, it could be a problem on the IAP platform, see my comments below.

+2
Sep 13 '11 at 2:55 april
source share

This is an old thread that is related to the problem that I encountered today.

In my case, I was able to test purchases on the device on my device until yesterday, but today it did not work. It turned out that Apple pushed me to revise and agree to the Amendments for Paid Applications. As soon as I agreed with the amendment (without reading, of course), everything started working again. There was no need to create a new test user or any other workaround.

There can be many reasons for not working inside the application, but make sure that you are properly configured for itunesconnect or that you cannot test in-app purchases.

+1
Aug 19 '14 at 5:12
source share

Make sure the system status is ready https://www.apple.com/support/systemstatus/

I have an iphone, reboot it worked for me

+1
Apr 12 '17 at 2:00
source share

This problem remains unchanged in 2016. Incredible. Here is my solution:

Add build number. Target> General> Identities> Build.

0
May 11 '16 at 18:32
source share



All Articles