in app purchase - iOS 7+ server verified inapp purchasing sending many receipts -


I'm trying to get the new inapp purchase API (ios 7+) to work and I think that Receipt data is so much when I read such receipts:

  NSURL * receiptURL = [[NSBundle mainBundle] appStoreReceiptURL]; NSDTA * Receipt Data = [NSData DataWith Contents of URL: Receipt URL];   

I am doing this inside:

  - (zero) Payment queue (SKPMcQ * *) Queued updated transaction: (NSARRA *) transaction   

So what I saw is that I send the receipt ""; And the data I am sending is much larger than the transaction. Transaction Recipe.

In fact, in response to apples, there are dozens of receipts in the "in-app" array. Is this normal? I have terminated these transactions, yet there are so many receipts in the integrated receipt, is that right? Do my big expendants (buy thousands of IAPs) are sending huge receipts with thousands of transactions in them?

In addition, what is the request for SKRETCITRPRESSER?

Update! I came to know that in a live environment, all consumable receipts are removed after the elimination. This is not the case on the sandbox environment, and it just keeps them, so the number of receipts can be found in hundreds. IOS7 introduced several IAP changes, among them: 1) Receipts are stored in the App bundle:

(Yes, plural on receipts) 2) Whether a particular receipt in the bundle remains or not depends on the type of product. For example, I do not think receipts for consumables can not be sustained.

What type of products are you?

Find the API to refresh the receipt. Sometimes the receipt is not in the bundle, and you can refresh it. The user gets inspired for the apple id / password, so the user can be bothered / when you use it.

Comments

Popular posts from this blog

java - ImportError: No module named py4j.java_gateway -

python - Receiving "KeyError" after decoding json result from url -

.net - Creating a new Queue Manager and Queue in Websphere MQ (using C#) -