3 Replies
      Latest reply on Feb 6, 2020 8:26 PM by PBK
      blubberlutsch80 Level 1 Level 1 (0 points)

        Sometime i got strange transactionId reported from the ios client.

        Normally they are 15 digits like:

        400000123456789

        but sometimes i got 40 character uuid, example:

        FAB60FFD-906D-48CB-8FED-092C4B2707D6

        In that case the receipt does not contain any transactions (in_app list in the response when verifiying against apple is empty).

        What does this mean? Is someone trying to hack or some strange fallback mechanism? Are there valid transactiondIds in this format?

        I get similar String in response Header of verifyReceipt in the following header: x-apple-request-uuid

        • Re: subscription: strange transactionId uuid style
          PBK Level 7 Level 7 (3,525 points)

          > Sometime i got strange transactionId ......the receipt does not contain any transactions

           

          Then there should not be a transactionId.

           

          If there are no IAPs in the receipt then it is reasonable to conclude that no IAPs were purchased.  It sounds like a hack attack on your app.

            • Re: subscription: strange transactionId uuid style
              blubberlutsch80 Level 1 Level 1 (0 points)

              sometimes apple is too slow and the transaction is not yet in the receipt, so i have to store the failed transactions to re-validate them later. But sometimes i get these weired transactions and it's useless to revalidate them.

              I just look for some advice which format may be valid and which format i can drop instantly.

                • Re: subscription: strange transactionId uuid style
                  PBK Level 7 Level 7 (3,525 points)

                  I have never found Apple "too slow".  Whenever there is a call to updatedTransactions with a state of 'purchased' there is always an updated receipt.  Are you finding something different?

                   

                  EDIT - Wait - I mean the receipt in the device is updated, not that the Apple servers will respond with a latest_receipt_info field that is updated.  -  Is that your issue????