"There is no information for In-App Purchases" 21107

Hi,

I'm working on moving an app's in-app purchases from Store Kit to StoreKit2 and whilst running in TestFlight I'm getting a "There is no information for In-App Purchases" error every two out of three purchase attempts.

The third attempt usually throws up a "You've already purchased this" dialog and finishes purchasing the subscription within my app.

From what I can see, I'm not getting this back as an error from a call to anything, the error is being displayed by the OS.

I'm not sure if it's something in my code, something in my product setups which is causing it, or something-else.

Any help would be useful, I don't want o push out the update if the in-app purchases aren't working.

Cheers,

Rich

Post not yet marked as solved Up vote post of Rich_UK Down vote post of Rich_UK
2.9k views
Posted by
Rich_UK
Reply
Add a Comment

Replies

Hey Rich, thank you for reaching out. Based on the timing of your post I looked up your error and found your requests. Looking at your user, it looks like you have quite a large history with this account. Could you please try either clearing your purchase history or testing with a separate Sandbox account? If these don't resolve your issues, please file a ticket in Feedback Assistant (https://feedbackassistant.apple.com) and post the FB number here.

Posted by
App Store Commerce Engineer
Up vote reply of App Store Commerce Engineer Down vote reply of App Store Commerce Engineer
Add a Comment

Thanks for getting back to me so quick.

I tried both clearing the purchase history and using a new Sandbox account over the weekend but the error is still occurring, so I created feedbag ticket FB12884381.

Posted by
rich Digitree
Up vote reply of rich Digitree Down vote reply of rich Digitree

  • Hi Rich,

    Do you have news on your ticket ?

    Thanks in advance.

    —
    Tomi84
Add a Comment

I am having same issue past 2 years still no fixes from apple

Posted by
askbabumag
Up vote reply of askbabumag Down vote reply of askbabumag
Add a Comment

just started seeing this errr this week

Posted by
mmdok
Up vote reply of mmdok Down vote reply of mmdok
Add a Comment

It's an issue on Apple's server. It was working as expected albeit slower than usual this morning. Then it stopped working a few hours ago. I have already received an email from a customer having the same issue with a solid app that was updated over 100 times on the App Store. The same issue occured briefly 2 weeks ago but was resolved within half a day.

Posted by
Idolum
Up vote reply of Idolum Down vote reply of Idolum
Add a Comment

The same situation! I am using old Store Kit and didn't do migration. Just "There is no information available for in-app..." 21107

Posted by
dimais
Up vote reply of dimais Down vote reply of dimais
Add a Comment

I am seeing this error all the time now when trying to test purchases on the sandbox. I'm using StoreKit 1. Only started happening in the last few weeks.

Posted by
developer555
Up vote reply of developer555 Down vote reply of developer555
Add a Comment

I'm seeing this issue recently with sandbox account. can you please confirm below queries

  1. can you please confirm whether this issue will happen for actual purchase ?
  2. if this happen, our application is in production if existing users getting this issue, what is the step to resolve ?
  3. development side do we need to do anything to resolve this issue ?
Posted by
balus2
Up vote reply of balus2 Down vote reply of balus2
Add a Comment

The same question! Is there any solution?

Posted by
Vincent810
Up vote reply of Vincent810 Down vote reply of Vincent810
Add a Comment

Hi, we started experiencing that issue last month and now it happens fairly often.
It has never happened before. (several years)

Code is: 21107 precisely.

Could SK engineers confirm it is an internal sandbox error and not a client issue?

Posted by
MathieuP-T
Up vote reply of MathieuP-T Down vote reply of MathieuP-T
Add a Comment

Just to follow up on this: I had my app rejected because this error occurred for the App Review staff! I'm unable to reproduce it so I'm not sure how to proceed- Can anyone confirm the source of this error? Maybe I should enter a FBAssistant bug...

Posted by
crazypill
Up vote reply of crazypill Down vote reply of crazypill
Add a Comment