Missing latest_receipt_info in Server2Server notifications

Since yesterday night (around 10:30 ETC+2) Server2Server notifications payloads are missing latest_receipt_info field. Is something similar happening to someone else?

Replies

We are observing the same behaviour. All the "latest_*" fields went missing since around 29 May 21:00 UTC. Before this time all the fields were present. As a result there is no way to relate a status notification back to a particular transaction, which makes the whole concept of server-to-server status notifications meaningless. Now the status notification consists only of the following fields:

{
  "auto_renew_product_id": "com.example.product_id",
  "auto_renew_status": "false",
  "auto_renew_status_change_date": "2019-05-29 20:58:01 Etc/GMT",
  "auto_renew_status_change_date_ms": "1559163481000",
  "auto_renew_status_change_date_pst": "2019-05-29 13:58:01 America/Los_Angeles",
  "environment": "PROD",
  "notification_type": "DID_CHANGE_RENEWAL_STATUS",
  "password": "***"
}

and it's impossible to trace it back to a particular transaction_id. Now you cannot react on subscription cancellations, purchase refunds and even some renewals!

Yup.


Same thing happening to us since exactly that time.


Bad deploy before WWDC?

Yes, same issue.

Yes, I have same issue

Yup, same issue.

Yes, same issue.

It looks like the problem has been fixed.

Same issue

Now it seems it continues only for Sandbox.

We experienced something similar in production for some time.
But it has been happening in Sandbox for a while...