Is this a brand new app? New apps get any initial in-app purchases appoved with the app. Either it all gets approved or none of it does.
But aside from that special circumstance, they are separate. Your app needs to properly handle the case when one or more in-app purchases are not available. So if you create a new in-app purchase, the app should work until the new purchases get approved and then they magically start working. If you decide to cancel one purchase, your app should gracefully handle it.
In case you are wondering for later, it can take a couple of days for changes to in-app purchases to propagate to all the stores.
Yes it is a brand new app and has never been approved / in the store before. Thank you for the explanation as it was not clear to us is the IAP need to be approved first and then the Binary submitted for approval.
If you would be so kind as to answer another questions.
Do the IAP buttons work in Test flight or will that functionalty only become available when the app is approved? When we try our app in test flight the IAP buttons do not function but we thought that was because the IAP had to be approved first before they would work.
I don't know about Test Flight. I'm primarily a Mac developers. But in-app purchases should work fine in development. They don't have to be approved for that. Are you validating those in-app purchases against both the production and sandbox server?
>Thank you for the explanation as it was not clear to us is the IAP need to be approved first and then the Binary submitted for approval.
In iOS, the first IAPs get approved at the same time as a new binary that codes for those IAPs. The new binary (and no earlier binaries) has those buttons in it that causes the app to access the StoreKit APIs. Prior to approval, an IAP can be accessed in development, in TestFlight and by App Review. When accessed that way an IAP is responding from the 'sandbox' environment'. The only difference between the sandbox environment and the 'production' environment is 1) 'cleared for sale' does not need to be checked 2) the bank contracts do not need to be signed and 3) the receipt can be decoded by a different Apple server.
> When we try our app in test flight the IAP buttons do not function
There is something wrong with your code.
>I would also at this point be happy to......
I am not certain but I believe that such requests are not appropriate for the forum.
Thank you gfor the explanation. We will have to check our code again and make sure it works in test flight.
I appreciate your help.