Incorrect subscriber details for customers with more than one RevenueCat promotional transaction
Incident Report for RevenueCat
From 6:30 AM UTC on January 30th 2024 to 7:00 AM UTC on February 5th 2024, the subscriber details in the subscriber info endpoint (`/v1/subscribers`), the receipt endpoint (`/v1/receipts`) and the `customer_info` field in events sent to Firebase Cloud Functions can potentially contain incorrect information for subscribers with multiple RevenueCat promotional transactions.

This only impacts customers that have 2 or more RevenueCat promotional transactions. It does not impact unlocking of entitlements via the RevenueCat SDK, even if a customer has 2 or more RevenueCat promotional transactions.

For impacted subscribers, the subscriber response would have the following incorrect values:
* The `product_id` field in the `entitlements` section can be incorrect for entitlements that are unlocked via RevenueCat promotional transactions.
* In the `subscriptions` block, when there are multiple RevenueCat promotional transactions, only one will be in the block. Additionally, the key used (which is supposed to be the product identifier) can incorrectly be the product identifier for another promotional transaction for the customer.

If you have any questions or concerns, please reach out to our support team. We apologize for any inconvenience caused, our test suite has been updated to ensure better coverage for multiple promotional transactions on the same subscriber.
Posted Jan 30, 2024 - 06:30 UTC