Confused About How to Add An In-App Purchase To an Existing App

I have an app that has been out for about 9 months.  I want to add an in-app purchase for a new feature.  I have implemented it as much as I can, but I am confused about how to go about testing it with Apple and Google.

For Apple I went in and added an in-app purchase, and gave it the Product ID and screenshot.  One question answered on StackOverflow said I could submit the in-app for review and set Cleared for Sale to NO, and Apple would approve it based just on the screenshot.  My assumption was that once that happened I could test the in-app purchases with a test account.  But when I went to do this, it says:

  • Your first In-App Purchase(s) must be submitted with a new app version. Select them from the In-App Purchases section of the Version Details page and then click Ready to Upload Binary.

Questions 1: Do I upload the new version to get the in-app purchase approved, but not allow it to be publicly distributed so that I can revoke the binary if/when I find out it doesn’t work?  If it doesn’t work, does that mean they won’t approve it

Question 2: What the heck does that message above even mean?  Specifically what does “select them” mean?  I can’t find any way in Itunes connected to identify that the in-app purchase is tied to the new version.   

On Google Play I just want to validate the steps:

Upload a new version as an alpha or beta

Add the in app purchase

Add test users

Test.

When it works release as production

Question:  If I find bugs will I have to increase the version number when I release it to production (ie I’m on 18 now, but if I upload a beta, find a bug will my version number have to be 19 when I release it as production?)  I would like to keep the version numbers the same between ios and google play.   

Thank you in advance if you know the answer to any of these questions!  

Sometimes just typing it all out, makes it easier to find answers and I think I found some.

Question 1: I think if I have a provisioning profile for the in-app, and a test account, then the in-app purchase testing will work without having to get approval first? This is the sandbox?

Question 2: On the version detail screen, right before the EULA is a section for in-app purchase, click that and check the checkbox for the in-app you are adding.

Sometimes just typing it all out, makes it easier to find answers and I think I found some.

Question 1: I think if I have a provisioning profile for the in-app, and a test account, then the in-app purchase testing will work without having to get approval first? This is the sandbox?

Question 2: On the version detail screen, right before the EULA is a section for in-app purchase, click that and check the checkbox for the in-app you are adding.