server to server notifications - no dates

Question

Created Mar ’21

Replies 2

Boosts 0

Views 1.1k

Participants 1

Has anyone else noticed that for the past two days the subscription service, server to server Apple notifications, has not included a purchase or expiration date?

Answered by CaponeTheGSD in 666430022

I figured it out. It was from the original format being deprecated. If anyone else needs assistance on this, this is an example of what the new data structure looks like:

Code Block perl{unified_receipt}->{latest_receipt_info}[0]->{purchase_date_ms}

Notice there is an array of data in the unified receipt->latest_receipt_info with record 0 being the latest record

Boost

Answer 1

CaponeTheGSD OP

Mar ’21

some additional info:

Maybe something that is deprecated has been disabled, but I can not find a sample of the new data that is being sent and understanding the docs is a bit confusing. I am trying (and previously was) collecting the following info from the JSON data that is sent:

Code Block perl{latest_receipt_info}->{purchase_date_ms}; //now missing - no info here
{latest_receipt_info}->{expires_date}; //now missing - no info here
{latest_receipt_info}->{is_trial_period}; //now missing - no info here
{latest_receipt_info}->{product_id}; //this is still OK
{notification_type}; //this is still OK
{auto_renew_status}; //this is still OK

If anyone has any info that could help me out it would be greatly appreciated.

Thx

0

Answer 2

CaponeTheGSD OP

Mar ’21

Accepted Answer

I figured it out. It was from the original format being deprecated. If anyone else needs assistance on this, this is an example of what the new data structure looks like:

Code Block perl{unified_receipt}->{latest_receipt_info}[0]->{purchase_date_ms}

Notice there is an array of data in the unified receipt->latest_receipt_info with record 0 being the latest record

0