We are currently listening to App Store Server Notifications V2 and have encountered an issue with notification ordering. Specifically, there are instances where Apple sends the DID_CHANGE_RENEWAL_STATUS notification before the INITIAL_BUY notification. This leads to a situation where we are unable to process the cancellation of a transaction that is unknown to us at the time of the renewal status change. Could you please clarify why this occurs? If this is a bug, could you kindly address it and implement a fix? Below, I have included examples that illustrate the issue. These examples I obtained using the Notification History API, which may help in troubleshooting.
bundleId: com.picsart.studio
case 1: originalTransactionId 350002410***633 DID_CHANGE_RENEWAL_STATUS - ‘2025-03-05T00:47:05.900Z’ INITIAL_BUY - ‘2025-03-05T00:47:40.728Z’
case 2: originalTransactionId 420002297***345 DID_CHANGE_RENEWAL_STATUS - ‘2025-03-03T11:43:54.006Z’ INITIAL_BUY - ‘2025-03-03T11:43:56.437Z’
case 3: originalTransactionId 150002224***082 DID_CHANGE_RENEWAL_STATUS - ‘2025-03-02T05:15:36.610Z’ INITIAL_BUY - ‘2025-03-02T05:15:52.666Z’