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
ChenJingFeng
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
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.