Does adding a new localization (language) in iTunes Connect for an iAP require the IAP to be (re)-approved? - app-store

I have an existing app in the AppStore that has in app purchases (IAP) configured and approved in English. If I add a language for localisation (e.g. dutch), does the IAP need to be re-submitted for approval?

You've likely already figured this out but for those who come across this looking for an answer.
The IAP itself will not need to be re-approved however the title and description for that new localization will be reviewed by Apple, so you will see a yellow dot next to it until this has been reviewed and will turn green if it is accepted and red if it isn't.

Related

In App purchase is getting rejected again and again

i have implemented the in app purchase in my application and added few in app purchases. on itunes connect i have filled all the details for the in app purchases. Initially the status of in app purchase was "waiting for review" and i was able to test in app purchase in sandbox env. but after every 4 days, in app purchases gets new status "developer action needed" and in the language section there is a "rejected" sign of in app purchase. so to make this use able again i have been using to make little change in description, which makes the in app purchase again in review
as history of the project is: right now application version 1.0 is available on app store in which in app purchases are not implemented
and i have added new application version 2.0 which is in "rejected by developer" state
so i just want to know why itunes connect team is rejecting in app purchase again and again?
also im not getting any email regarding this rejection
any one guide me what is the solution to this problem or any one else has faced this issue before?
Have you uploaded new version on apple store which is having in-app purchase code implemented ? if not then they will reject the in-app purchase items.
also if apple is rejecting your in-app purchased , then have you provided all the details to them. As if they find the in-app purchase improper then they can can reject it. Provide them proper details and proper screen shot for the same.
Also if apple is rejecting your in-app purchase then you may can ask apple review team about the issue. Use the Link. they will let you know the exact issue.
Hope this will help you.
I recently had this problem with an app submitted to Apple.
There is a fallback system that needs to be in place for server side in app purchase validation.
It is documented in Apple, but VERY well hidden in tech note :
http://developer.apple.com/library/ios/#technotes/tn2259/_index.html
Here is the way to do it :
"Always verify your receipt first with the production URL; proceed to verify with the sandbox URL if you receive a 21007 status code.
Following this approach ensures that you do not have to switch between URLs while your application is being tested or reviewed in the sandbox or is live in the App Store."

Do I have submit an actual binary in order to test In-App purchase?

I have many versions released so far for an App (without In-App purchase).
Do I have to submit anything to be able to test In-App purchase?
What do I have to do?
I've implemented this - http://troybrant.net/blog/2010/01/in-app-purchases-a-full-walkthrough/ - so far, nothing happens when hit Product Details, or Purchase.
No, there exists an In-App Purchase Sandbox. All you have to do is creating the App in iTunes Connect (under "Manage my applications") to add your In-App purchase items.
You don't need to submit and reject a binary in order to advance your development process or test In-App Purchase. The link you're referring to, although helpful, is now out of date and the quirks in iTunes Connect that it refers to are gone, so don't follow it blindly!
The Apple doc is much more reliable and I recommend you use it instead. I actually wish I had started with the Apple docs rather than the link you provided when I implemented In-App Purchase in my app a few months ago--I can't recall the details but I do remember that it led me astray, particularly regarding the need to submit and reject a binary.

iPhone Dev. Apps: "Promo Codes" button in iTunes is missing

I have got a few apps in my iTunes Developer Backend.
Since yesterday the "Promo Code" button is missing in some of my apps details view. The rest of my apps have still this button and I can download promocodes. Does any one know this problem and maybe solved it?
Thx :-)
Thank you for contacting Apple
Developer Support with regard to
iTunes Connect Promo Codes. Please
know that applications which are rated
17+ will not be provided Promotional
Codes for distribution. As such, the
usual button to request Promo Codes in
iTunes Connect will not be visible for
these applications on the Version
Details page.
If one controls what you ship, is it censorship or dictatorship?
Are you looking under the currently shipping version? should be alongside the Manage Localizations
They did move around in the update to iTunesConnect a few months back.
Is your app rated 17+ ?
Apple recently turn off promo codes for applications rated 17+.
I had this same problem so I emailed Apple. Here is their reply:
Thank you for contacting Apple Developer Support with regard to iTunes Connect Promo Codes. Please know that applications which are rated 17+ will not be provided Promotional Codes for distribution. As such, the usual button to request Promo Codes in iTunes Connect will not be visible for these applications on the Version Details page.
That solved the mystery for me.
Just in case anyone is still looking, I found the Promo Codes button under the Features tab NOT the App Store tab of the app details page in iTunes Connect.

When does App Store promotional code become effective?

I just submitted my app to the App Store and it's in the reviewing process (3 Degrees of Wikipedia). I have set the "Availability Date" to a future time as some blogs want to cover my app, and I want the release of the actual app come out at the same time as the reviews.
My Problem is: will the promotional code work for the blog reviewers, because the app is not actually in the public App Store? In other words, can the reviewers try out my app during this past-approval-yet-not-public stage of the app.
Thanks,
Ivan
The short answer is no, you can't.
In order to redeem a promotional code the app needs to be available to download under iTunes.
If you want to give blog reviewers a chance to look at your app before it's released. Send them a Ad Hoc version of your app. This is the recommend way in sharing your app with a limited circle of reviewers/testers.
You can find out more information on Ad Hoc under the Apple iOS Developer section

iPhone app activated before associated in-app-purchase activated?

I recently submitted my iPhone app for review. I also approved the in-app-purchase for my app (and provided the in-app-purchase screenshot). It's a few days later and the app status has been updated from "waiting for review" to "in review"... while the in-app-purchase status is still "waiting for review". Could the app go live in the store before the in-app-purchase? If so what happens when the user tries to make the in-app-purchase? Anything the developer can do to remedy this?
Set the app availability date to a time in the future, then when the in-app purchase is accepted, set both dates to the present.
You should also uncheck the "Cleared for Sale" checkbox in the In-App Purchase page in iTunes Connect. This means the IAP won't go on sale (even after being approved) until you decide it should.
You should have a check in your app to see if an IAP is actually available, and only display it if it was found in the App Store.
The same thing happened to us on one of our submissions. The Apple reviewers wanted to see our in-app-purchase experience before they approved the app. So in the course of the review they made sure the in-app-purchase was up to par, and approved them both at the same time.
I'm not sure if this is the standard among app reviews, so I'd play it safe and go with #nevan's suggestion as well, because if the app goes through without the in-app purchase items enabled, the purchases will fail.