Hey there!
We've started to receive duplicated notifications though we responded with 200 HTTP Status Code.
AFAIK there's no way to uniquely identify notification from its properties. We decided to get a hash of the notification body and use this value as a unique ID.
However, unified_receipt.latest_receipt_info seems to be different. Moreover, seems like this is not a valid base64 value.
Could you please help with the issue?
Same problem here.
We are responding with a 200 status code but we starting to receive so many duplicated notifications. The unified_receipt.latest_receipt containing the receipt token is the only field that changes.
In our case, the token is a valid Base64 and we can get the receipt with it. And comparing both receipts the only difference between them is the receipt_creation_x, request_date_x and original_puchase_date_x timestamps.
For this reason, our ratio of received notifications suddenly increased from ~50/h to ~200/h and it remains stable in that range causing several issues related to our revenue metrics.
Apologies for the inconvenience. Due to the issue yesterday (https://developer.apple.com/system-status/) impacting App Store Server Notifications, you are experiencing this issue related to duplicate notifications which is now resolved.
The new notification which are generated after the fix should no longer experience the duplicated notifications issue and for existing impacted notifications which are getting processed should stop being send as we complete processing.
