There is no information available for In-App Purchases. Try again later. 21105

Question

Yesterday this error started appearing when testing my apps from nowhere.

It's happening upon calling restoreCompletedTransactions() at app startup.

What does this error mean and is there anything I can do to avoid this error?

I am experiencing the same only on newly created sandbox accounts I think it's the latest version of ios? it started when I upgraded my iPhone to the latest version — Z. Cajurao, Aug 27 '20 at 08:26
I ran into this issue on 13.6. I was able to resolve the issue by erasing all content and settings, and NOT restoring from iCloud backup. — mattwindwer, Aug 27 '20 at 15:22
I’m voting to close this question because it's about an issue with 3rd party services, not about programming as defined by the [help]. It's also a temporal issue that will likely not last longer than a few hours/couple of days. — TylerH, Aug 28 '20 at 14:57
I am voting to keep it opened and allow users to know what is really going on with very common problem — Bartłomiej Semańczyk, Aug 28 '20 at 14:58
@BartłomiejSemańczyk the question doesn't need to be open to accomplish that. That aside, this site isn't the place to keep users informed of a temporal issue with Apple 3rd party service status. — TylerH, Aug 28 '20 at 15:05
I've attempted to edit the question to hopefully make it more on topic. — mbauman, Aug 28 '20 at 15:30
Please add additional comments to [this](https://developer.apple.com/forums/thread/125164?answerId=629310022) thread on the Developer Forum. — Caleb Jones, Aug 28 '20 at 19:57
This seems to be an issue with new sandbox test accounts. I happen to have an old one, and that works fine. Anytime I create a new test account, same issue. Hope Apple fixes this soon coz the review team doesn't understand that its an Apple issue. — xoail, Sep 01 '20 at 20:41

score 6 · Answer 1 · answered Aug 27 '20 at 07:30

6

It's apple's internal servers that are causing this. From what I researched a few hours ago, this happens on SOME testers (apparently not all). And it only happens on test accounts, so production app is safe.

answered Aug 27 '20 at 07:30

Gene Sy

1,325
2
10
17

Ok, but what to do to make it working on test accounts also? They are reviewing it, and reject the app because of this error. – Bartłomiej Semańczyk Aug 27 '20 at 07:32
Same thing's happening to me. I gave them a lot of evidence that this is in fact an error on their end but no replies so far. – Gene Sy Aug 27 '20 at 08:03
I have send a message to Apple Developer Technical Support with this issue. It was the last free one for my account. Lets see what they reply. – Bartłomiej Semańczyk Aug 27 '20 at 08:04
Looks, it's a temporary bug on the Apple side. It's happening on all the apps we have for about 2 days. – Patrik Vaberer Aug 27 '20 at 11:59
I wonder why they're not acknowledging it at all. They still say it's my app's fault this is happening... – Gene Sy Aug 27 '20 at 14:44
Same issue here, im on 3.5.1, anyone got this resolved? – Meku Aug 30 '20 at 18:47
we can't just deploy a new version and test it. This should be fine with sandbox account – Dani Oct 03 '21 at 21:57

score 4 · Accepted Answer · edited Aug 28 '20 at 14:58

4

I have asked an Apple using Apple Developer Center, and they replied to me like this:

Hello Bartlomiej Semanczyk,

I’ve review the problem description presented below. This looks like a bug report issue to be investigated by the App Store Server QA engineers. The error string presented in the Stack Overflow page is new to me. However, this issue needs to be investigated by the Server QA team as it’s likely that the server is issuing this error string. Please follow these instructions to install the StoreKit profile and capture a console log, then submit a bug report. I will review the bug report and make sure that it’s forwarded to the Server QA team for investigation. BTW, I just ran an old StoreKit sample ad I’m not seeing this issue. I wonder if the issue only occurs with new in-app purchase identifiers.

and here they attached a lot of instructions ho to install StoreKit and capture the device console log.

edited Aug 28 '20 at 14:58

desertnaut

57,590
26
140
166

answered Aug 27 '20 at 21:20

Bartłomiej Semańczyk

59,234
49
233
358

Thanks for the update. I hope they fix this soon. Idk about the new inapp identifiers since mine’s a few momths old and old – Gene Sy Aug 28 '20 at 01:36
Do you have any updates from them? I'm getting frustrated by the app review team's responses. – Gene Sy Aug 31 '20 at 16:28
No, they are still reviewing my app also;( – Bartłomiej Semańczyk Aug 31 '20 at 16:31
the app review team doesn't even acknowledge that it's a serverside issue not my app's issue. that's honestly all i want from them right now :( – Gene Sy Aug 31 '20 at 17:16
1

Still happening 2021 – Jalil Apr 27 '21 at 18:27
Still happening in 2022. In debug area, it showed the error was created due to inability to refresh the receipt of IAP through sandbox server. – DORI Jun 12 '22 at 22:28
Still happenning in June 2022. – Shraddha Shravagi Jun 18 '22 at 13:04
Still hapening in Feb 2023 – PlusInfosys Feb 20 '23 at 09:47

Dave C · Answer 3 · 2020-08-27T07:58:28.383

1

One of my TestFlight users has also been experiencing this error, while others haven't strangely. Most of them are on ios 13.6.1. Others on the Apple dev forum thread (where I found your link to here) are experiencing this in production as well. Seems this problem has started roughly 48 hours ago with no concrete answer from Apple. At any rate, to answer your question:

When setting up your server side to communicate with Apple to check the receipt, you need to hit the production api first:

https://buy.itunes.apple.com/verifyReceipt

You will get a json response from Apple that includes a "status" key and a corresponding numerical value. If the "status" returns "21007" it means the receipt is for Sandbox not production. You then hit the testing api instead:

https://sandbox.itunes.apple.com/verifyReceipt

edited Aug 27 '20 at 07:58

answered Aug 27 '20 at 07:55

Dave C

11
2

Ok, but there is no server side for my app, especially my own server side. – Bartłomiej Semańczyk Aug 27 '20 at 07:57
Apple (and myself) strongly recommends not validating receipts directly from the app as stated on this page: https://developer.apple.com/documentation/storekit/in-app_purchase/validating_receipts_with_the_app_store – Dave C Aug 27 '20 at 08:06
Yes, you are right, but I didnt validate any receipt before...;( – Bartłomiej Semańczyk Aug 27 '20 at 08:07
I dont think the issue is not having a servers to validate receipts for this one tho. Since it's returning error even before a purchase is made – Gene Sy Aug 27 '20 at 11:45
Same issue here for a tester on Testflight just after checking the user receipts on App Store from the app and before getting the list of the subscriptions. Probably it will trigger after any interaction with the App Store... – GDM Aug 28 '20 at 10:14

score 1 · Answer 4 · answered Aug 27 '20 at 20:55

1

I have received the same error on my test device with an old sandbox user. The following steps have kind of solved this issue for me:

Sign out sandbox user from test device
Create a new sandbox user
Sign in with the new sandbox user.
Try to restore the In-App Purchase without purchasing it in the first place. Get the error in question.
Try to purchase the In-App Purchase... Purchase successful.
Delete the app.
Re-build the app on the test device.
Restore the In-App Purchase. Restore successful.

I know this may not be a definite solution but I just wanted to share this information with the hope of being helpful. I will update my answer once the app's latest version is approved by the App Store.

answered Aug 27 '20 at 20:55

Luke

965
8
21

Yes it may be good solution, but how to told the Apple reviewers to do that while they review my app? – Bartłomiej Semańczyk Aug 27 '20 at 21:10
@BartłomiejSemańczyk I thought that if we can solve in our local test devices by simply using a new sandbox user, it proves that the problem is not related to the app itself, and therefore I conclude that Apple Reviewers should not refuse approving the app for a reason not related to the app. However, if this is not the case I guess there is nothing more we can do other than contacting them via developer support channels: https://developer.apple.com/contact/#!/topic/select – Luke Aug 27 '20 at 21:50
My issue right now is that they're ignoring everything i'm saying and just "retrying" the same test again and again. I even ask why my previous builds that are on production have the same issue and they just ignore my statements – Gene Sy Aug 28 '20 at 04:48

score 1 · Answer 5 · answered Sep 01 '20 at 03:29

This happened to me also when installing a build from TestFlight. I had a sandbox account configured but that account was not part of the team the build belonged to. So I logged out of the sandbox account and the dialog disappeared. I logged in with proper sandbox account that belong to the team, even then I didn't get the dialog.

I know that when installing the build from TestFlight it uses the actual iTunes store account configured on the device, but my guess is that it has something to do with the sandbox account. To avoid this dialog remove the sandbox account when installing the build from TestFlight or use a proper sandbox account that belongs to the team or account that the build belongs to

score 1 · Answer 6 · answered Dec 14 '21 at 08:14

1

Just check the bundle id in appstoreconnect/App information , make sure is the same with your App bundle id

answered Dec 14 '21 at 08:14

Govan

1,322
1
14
13

Derek Lee · Answer 7 · 2022-09-08T23:02:29.927

Today I encountered a 21105 response code when validating a receipt against Apple's server for a sandbox user and found this thread.

In my case, I had just recently cleared the purchase history for all of the sandbox testers in my Apple Developer Account, so I assume that because I cleared the purchase history, the receipt data is no longer valid.

At least according to Apple's documentation on what valid status codes can be returned, they don't have a definition for this one specifically as it falls under their range of internal data access errors:

Status codes 21100-21199 are various internal data access errors.

Anyone with the appropriate access rights can clear the purchase history for a sandbox tester under "App Store Connect" → "Users and Access" by first clicking "Edit" and then selecting a user account to enable the "Clear Purchase History" button:

That said, after making another in-app purchase with the same user account, all following receipt validation calls were successful.

There is no information available for In-App Purchases. Try again later. 21105

7 Answers7

Linked