I know this has been discussed many years back but it still seems like this is a frequent issue. How does Apple not support multiple subscription purchases with the same Apple ID? For example we allow managers to manage others account. If they purchase an IAP subscription for Account #1, and also want to purchase a subscription for Account #2 they can't. It would be nice if Apple would allow this to happen by allowing us to specify a customer id that can be used to generate the original_transaction_id. Has anyone found a work around to allow multiple accounts to purchase subscriptions with the same AppleID?

We use a localization service that allows us to export our translated strings in .xliff format. When I import the spanish (es.xliff) file into the string catalogs it imports the english keys and leaves the spanish translation column empty, which causes it to default to English. I created feedback 12429535 and 12429469 because it seems the feedback site is broken and shows it cannot find the feedback I just submitted.

We have noticed lately that a bunch of our receipts coming in from the Apple IAP webhook appear to be the older style receipts pre ios 7 that has the in_app array empty and doesn't provide a latest_receipt_info. Our app only supports iOS 15+ so not sure how these receipts are coming in. I noticed a couple receipts that didn't have the latest_receipt_info initially when coming in, ended up getting a latest_receipt_info a few days later. We are trying to figure out what is causing this as it is messing up our IAP processing system. The receipts look like this. { "receipt": { "receipt_type": "Production", "adam_id": <app_id>, "app_item_id": <app_id>, "bundle_id": "<bundle_id>", "application_version": "308", "download_id": <download_id>, "version_external_identifier": 859744352, "receipt_creation_date": "2023-09-12 23:58:47 Etc/GMT", "receipt_creation_date_ms": "1694563127000", "receipt_creation_date_pst": "2023-09-12 16:58:47 America/Los_Angeles", "request_date": "2023-10-06 14:54:57 Etc/GMT", "request_date_ms": "1696604097794", "request_date_pst": "2023-10-06 07:54:57 America/Los_Angeles", "original_purchase_date": "2022-10-05 13:05:53 Etc/GMT", "original_purchase_date_ms": "1664975153000", "original_purchase_date_pst": "2022-10-05 06:05:53 America/Los_Angeles", "original_application_version": "98", "in_app": [] }, "environment": "Production", "status": 0 } We are trying to figure out what is causing this and if it is an issue on our side or Apple's.