inAPP purchase testing procedure

Question

I\'m going crazy testing my app for inApp purchase. I cannot get any valid product.

I\'ll try to make some questions here, hope someone could answer.

1. Do

Answer 1

There is no need what-so-ever to submit the application binary before testing in-app-purchase in SANDBOX environment.

The In-App-Purchase product'll 've state READY TO SUBMIT.

Answer 2

You do not have to upload a binary. You can set up your app in iTunes Connect, and then set up your products associated with it. The "Waiting For Review" on your products will stay waiting for review until you submit a binary and submit the app and it gets approved. You can still test, however, even with your products "Waiting For Review". There is (IIRC) a transitional state which you as developer must mark your products as approved after you have tested them.

Note: Once you create the app in iTunes Connect, you have 90 days to submit a binary before they take your app name away from you.

Note 2: When testing with your debug build before submission, you have to use the development sandbox servers. See the IAP documentation for more info.

Answer 3

Ensure that the project Bundle ID is the same as the registered for the application in itunesconnect.

Answer 4

Those of you having trouble with In-App Purchase (IAP) make sure a few things are done correct,

• create your app in iTunes as you do for release
• setup In-App Purchase (supply everything including screenshot)
• create test users (very important as you cannot use a real user to test while in Sandbox)
• go to your app View Details and make sure you see the In-App entry that you've setup show up there, if not "edit" that section to choose the appropriate In-App entry (very important)
• click on "Ready to upload binary" button (again, very important). Don't worry about uploading binary at that time as you have 90 days from then to upload your binary.
• implement IAP in your code (there are many samples out there, I prefer http://xcodenoobies.blogspot.com/2012/04/implementing-inapp-purchase-in-xcode.html)
• if you are testing it on a device make sure to signout (Settings > iTunes & App Store > Signout (very, very important)

Once all these are done you should be able to make In-App purchases using those test accounts. It worked after a few hair pull-offs for me.

Answer 5

i had the same problem. for me helped 2 things in combination:

1. remove "rejected" status via uploading the binaries again
2. don't use a jailbroken device

But in FAQ 6 are some more reasons for this problem listed:

• You did not complete all the financial requirements (see the "Contracts, Tax, and Banking Information" section of this document).

• You did not use an explicit App ID.

• You did not use the Provisioning Profile associated with your explicit App ID.

• You did not use the correct product identifier in your code. See Technical Q&A, QA1329, 'In App Purchase Product Identifiers' for more information about product identifiers.
• You did not clear your In App Purchase products for sale in iTunes Connect.
• You might have modified your products, but these changes are not yet available to all the App Store servers.
• If you or App Review rejected your most recent binary in iTunes Connect.

hope this will help some more of you.

Answer 6

I spent waay too much time on this exact problem too.. you do not need to upload a binary to get the in app purchase testing, what that means in iTunes connect there is that you cant add additional products to an existing product on the iTunes shelves. For example if your app is live and at version 1.0, and v1.0 was submitted with only one in app purchase connected with it, there can never be a 2nd in app product for v1.0, to add a 2nd (or many more) in app products you need to resubmit, go up to 1.01 or whatever. The key thing that I was overlooking, and I hope this helps, is YOU MUST BE USING A PROVISIONING PROFILE FOR THAT IS MADE FOR THE APP IN QUESTION, not the generic profile that xCode's little helper wizard thing just builds stuff on by default. Try that