不指望你们会解决!!! 本来bug是软件开发者自己发现自己解决!!! bug让用户发现了, 还要用户按照你们的复杂方式告知你们, 作为开发者真为你们丢脸, 真是一点cover的能力都没有, bug不要修复了, 等着被骂死吧

I’ve also noticed another issue: sometimes Apple creates two pairs of originalTransactionId-transactionId for the same transaction. For example: originalTransactionId: 450002184711774 → TransactionId: 450002184711774 originalTransactionId: 450002184711775 → TransactionId: 450002184711775 Both pairs belong to the same user and the same order at the same time. Since our system uses originalTransactionId + TransactionId as a unique key, this causes the user’s membership to be added twice.

I'am the issuer creator. I found this. I don’t know why, for the same subscription, first purchase it started with originalTransactionId_A, and at some point a new originalTransactionId_B was generated. However, I recently noticed that new renewals are linked back to originalTransactionId_A. Haha, Apple is a magical company.

Apple is god, we are customer .... [ Apple 你个垃圾 , 早期是 DID_CHANGE_RENEWAL_STATUS DID_FAIL_TO_RENEW 受影响, 现在 DID_RENEW 出现问题严重 影响业务] .... 我不得不开始骂人了