Our app server has subscription feature and processes purchase life cycles based on App Store Server Notification v1.
Last year, when users purchased subscriptions during the following timeframe, we received "INITIAL_BUY" notifications with "unified_receipt.Latest_receipt_info.purchase_date" set to future date(approx. 1 hour after the actual purchase).
- 2024-11-03 08:00:00 - 2024-11-03 09:00:00 Etc/GMT (UTC)
For example, we received the following v1 notification at 2024-11-03 08:36:33 Etc/GMT.
- "notification_type": "INITIAL_BUY"
- "unified_receipt.latest_receipt_info[].purchase_date": "2024-11-03 09:36:02 Etc/GMT"
Our server grants subscription entitlement based on "purchase_date" so the users had to wait 1 hour before the subscription features became available.
The timeframe coincided with the end of daylight saving time in the U.S., so we assume that it affected the behavior, but our country doesn't adopt daylight saving time.
We have some questions regarding this behavior.
-
In countries without daylight saving time, how should we handle such notifications with future purchase date in order to properly grant subscription entitlement?
-
In App Store Server Notification v2, could purchase date be set to future date at the end of daylight saving time in the U.S., just as in v1 notifications?