I also had this problem in the production environment, where a payment would have two callbacks. A synchronous callback, and an asynchronous callback returned from Transaction.updates The transactionId for both transactions is the same。 It is not a necessary problem, but a low probability scenario

Have you found the reason for this problem? Thank you

I also encountered the same confusion, the same transactionid, every time when the restoreTransaction, there will be unverified failure of the order, and I feel very strange

I had the same problem. Does the source code library require a privacy list, and how do I add it

I also have this situation, the transactionIdentifier returned by the Apple API is invalid after verification.