iOS SKProductsRequest returns products as invalid identifiers

I'm testing my iOS app In-App Purchase module and SKProductsRequest started returning inconsistent results.

On one request it returns my product in "invalidProductIdentifiers" property and after a few requests it returns it as valid in "products" property. I don't see a consistent pattern in this.

I've read TN2259(https://developer.apple.com/library/ios/technotes/tn2259/_index.html) and all the steps are fulfilled, or they seem to be.

My product is a consumable "Ready to Submit", attached to an app version that is in "Prepare for Submission".


I've tested with a different bundle identifier, code signing and provisioning profile from an app where this behaviour dosen't apper, which leeds me to think that there is something in the way my app is configured in iTunes Connect or signed.


Ideas why SKProductsRequest returns my product as invalid sometimes and valid other times?

So I recently experienced this issue and here is how I resolved it:

My account had recently "auto-renewed"
I found that my pricing "start dates" had been post dated, despite the fact that they hadn't changed in months.
The issue had been occuring for several days, but by the time I checked, the "start date" was Today, Monday November 28th (I'm not sure if they had just kept rolling over or what, or been auto advanced to the beginning of the next work week.)

However, while it was November 28th ~12:30 AM EST (my location), by PST (Apple) it may not have been. I don't know if the last time I had checked the app was before or after 12AM, but in the interim I had done the following:


I went into one of my in-app products, and removed it from sale, saved, re-enabled it, and saved again.
I then when in and "scheduled a price change" setting it to the same price, "Today" for the start date, and "No End Date" for the end date (although this was the original case as well, so I'm sure you could set it to whatever you need it to be), and saved again.


After that i relaunched the app and all my prices were there, not just the changed one. So I'm not sure what actually resolved it but it appears that:


The prices get their "start date" reset to some point in the future, so you just need to schedule a price change for the earliest possible date (Today at the bottom of the calendar), and then set the price and "end date" to whatever they should be. In my case I only had to do this for one item, but it could be conceivable that you may need to do it for all items.

Hi Did you fix the issue? I have the similar one.

No luck..Tried with updating price info & clear for sale.Still all the product IDs are coming invalid after membership renewal. 😠

Also, keep in mind that agreeing to the Paid Applications cotract is not enough. You also have to fill out the contact, bank and tax information for that agreemant specifically, for it to be considered done.

I'm having the same issue with my product identifiers intermittently coming back as invalidProductIdentifiers for a small subset of users. This problem has persisted for the last 9 months, across various releases, certificate renewals, a developer program renewal et cetera. This is for an auto-renewable subscription in-app purchase for an already released app. I've only recently been able to determine that this is the problem, since a lot of customers have trouble making in-app purchases for other reasons (logged in with different Apple-IDs, no up-to-date payment method for this Apple-ID, buggy Mac App Store app - lots of bugs there, and others).


The last week alone this issue has cost me around $200 in lost sales, which really hurts me as an indie developer. For that 30% cut I expect Apple to do (much) better, especially since I'm doing all the work and buying ads to bring these leads to my app. Having to field support questions for this issue is agonizing since there is nothing I can do for the user.


I would like to get some feedback that this issue is being worked on, what the problem is and when it can be expected to be resolved. I collect the Apple-IDs from users who are having problems (and get back to me; I suspect that some just give up before reaching out) and add them to the bug report I've filed on the issue. I tried raising a DTS request but it was refunded as this is an iTunes team issue. As it stands I can complain here or I can move my app off the Mac App Store. Complaing here is less work but problably less effective…

This issue will only be investigated when you submit a bug report. I can't explain why this issue occurs intermittently, but I've replicated the issue myself using developer applications to know that this is a real issue, but one which affects a very samll subset of applications. The issue has to do with the handling of the SKProductsRequest by the iTunes Store server. For 99.9% of StoreKit apps, the server responds correctly. For the other 0.1%, the server fails - sometimes always, sometimes intermittently. Unless the issue is reported to the StoreKit team, they will not know which apps are being affected.


To submit a bug report for investigation by Apps Ops Engineering, please use the Apple Developer Bug Report web page - http:/

After logging in, select the iTunesConnect Product.

Fill out the bug report form. In the description section - please include

1. the application ID

2. if applicable, the iTunes Store that the purchase was attempted - US, Canada, Mexico, China, Russia, etc. (sometimes the issue has to do with a sepcific Store)

3. The in-app purchase identifiers that are failing to be purchased

4. The steps to find the in-app purchase items. If the application is is other than English, please include screenshots showing now to navigate the app to find the in-app purchase items.

5. mention that the issue occurs with the production environment.

If you send me the bug report number I'll peruse it quickly and verify that the issue gets assigned to the Apps Ops Engineering QA team.


rich kubota - rkubota@apple.com

developer technical support CoreOS/Hardware/MFI

If anyone else comes across this: I've found that the common denominator for all users affected by this problem is that they are running macOS 10.11.

iOS SKProductsRequest returns products as invalid identifiers
 
 
Q