AEM Mobile Products IDs – “item you requested is not available for purchase”

JonAshby

18-05-2016

Anyone having this problem when testing non-preflight API or APK Apps on both iOS and Android devices?

We've set up a collection in products and subscription with a product ID, ensure that the collection product is set to "entitled" as per Adobe documentation, but when we test the app and purchase the collection via the article paywall it says either:

“item you requested is not available for purchase” Android

"The content you purchased cannot be displayed at this time" Apple iOS

I can confirm that the collection in quotes is "available" and set to "entitled" but we are getting rejected by iTunesConnect because of this bug and can't get it to work in developer sandbox with either development API or APK on either device.

Any help would be greatly appreciated, thanks in advance, Jon

Accepted Solutions (1)

Accepted Solutions (1)

Bob_Bringhurst_

Employee

18-05-2016

First, check to make sure that you have an in-app purchase (IAP) set up in Google Play Developer Console (for Android) and iTunes Connect. The Product ID of the IAP should match the Product ID you set up in the Portal. For iOS, make sure that the IAP is approved and that you don't have any typos.

Next, check to make sure that you have the iTunes Connect Shared Secret and the Google Play Shared Secret strings specified in project settings > Store tab. This is especially important for Android purchases. (On iOS, the shared secret is required for subscriptions and for Android, the shared secret is required for any purchase.)

Let us know if you've done both of those things and you're still getting an error when trying to test purchases.

Answers (4)

Answers (4)

Christophe_Joss

Employee

19-05-2016

--> You should be able to test the development viewer properly by setting up test user in your iTunes Connect account. Then log out of the App Store on the device and initiate the purchase. Then log in with your test user credentials so everything is done in the SandBox environment

---> Yes that is exactly the one .. also be aware that setting up Google in-app purchases takes much more time than on iOS, there might be a delay before you see prices appearing

Christophe_Joss

Employee

19-05-2016

Testing Google IAPs is a whole different animal

Have a look at these knowledge documents from the Google Play Developer team, hopefully that will help:

Testing In-app Billing | Android Developers & Set up alpha/beta tests - Developer Console Help

.. and I'm sure more documentation can be found on the site.

JonAshby

19-05-2016

Hi Chrisophe – that's great, signed in with Sandbox and all IPAs appear to be working on iOS… Thanks for advice re Google IAPs. So I guess as we've only just added the shared secret to the Adobe portal we'll have to wait a while? they all say approved and ready to go on the Google Play store, just want to test that IAPs work before I make it live.

Anyhow – Chistophe, Bob – can't thank you enough. Cheers

Jon

JonAshby

19-05-2016

Hey Bob,

Thanks so much for your help! OK the first part re matching IAPs / Product IDs in the respective stores and Adobe AEM portal all fine I think. The IAP in question whenre we were gettign the content error message is in Review as well as the new sign-app API, so maybe that is why. However…

We hadn't set up the shared secret details on the APP which we have now done and it seems to have changed somthing on iOS at least. Now when we test the iOS IPA and try an in-app purchase it simply says "Cannot connect to the iTunes Store" for all of the inApp purchases – I'm guessing that's just becasue it's a dev app signed with dev certificates?

On Android however we are still getting the same issue. To confirm, re Android Shared Secret we have added the "YOUR LICENSE KEY FOR THIS APPLICATION" on the Google developer under the Services & APIs tab to the Adobe Portal, is that right?

Again, thanks so much for your help Bob,

Jon