User Profile

Today, I confirmed the sandbox environment for the receipt of my subscription.original_transaction_id has been changed each time the subscription is renewed.The original_transaction_id is set to the same value as the transaction_id of the renewal of the subscription.Until last week, original_transaction_id always had the first transaction_id set.Was the specification changed?Or is it a sandbox environment bug?The guidelines have the following description.This value is the same for every specific subscription. This value is useful for relating together multiple iOS 6 style transaction receipts for the same individual customer's subscription.

HelloWe are studying how to restore the user data of the application.Do you have any suggestions?We are now considering restoring user data using receipt of In-App Purchase.Specifically, we are considering restoring user data by using the original_transaction_id of the receipt,Is the value of the original_transaction_id of the receipt a unique value that does not overlap and is not changed?For example, by model change etc., have users transitioning to terminals purchase free non-consumable items in advance.Save the original_transaction_id of the receipt of the free non-consumable item as user data on the server.The user installs the application on another terminal and restores purchase history.When restoring, refer to the original_transaction_id of the receipt and the original_transaction_id of the application server's database to identify the user and restore the user data.If the original_transaction_id of the receipt is unique and immutable value, I think whether it is possible to restore the user data by the above method, how is it?I will be saved if you give me advice.