We have two test products (auto-renewable subscriptions) - S1 and S2. They have different store product ids. Client application bought first subscription "S1" and sent it to our server. Our server sent this receipt to Apple validation service.
Documentation says about "Original Transaction Identifier" - "All receipts in a chain of renewals for an auto-renewable subscription have the same value for this field.". For "S1" all auto-renewed receipts contains same original transaction id.
According to the client app developer, he did not buy the second subscription. But after several auto-renewals of the first subscription in response from Apple I found information about second subscription and that the second subscription has the same original transaction id as the first one.
And another strange thing - in Apple response i see that original_purchase_date of first and second subscriptions is same (client app developer assures that he did not buy the second subscription), for example:
FIRST SUBSCRIPTION:
"original_transaction_id":"1000000294***869",
"original_purchase_date":"2017-04-27 12:13:02 Etc\/GMT",
"product_id":"com.our.app.s1",
SECOND SUBSCRIPTION:
"original_transaction_id":"1000000294***869",
"original_purchase_date":"2017-04-27 12:13:02 Etc\/GMT",
"product_id":"com.our.app.s2",
In the first iteration of the auto-renewal receipt of first subsuctiption, information about the second subscription does not appear.
Is it normal that two different purchases (with different store product ids) have the same original transaction id? Or is it somehow connected with the test environment of Apple?
I did not find any information on the Internet.
Are these two subscription products part of the same autorenewable 'group':
If so, it is reasonable that they tie into the same original purchase transaction since a user can switch between them at renewal time.