Newly Created Entitlement Not Added to Users

[jswilliams]

We just added a new entitlement to an existing product (and kept the old entitlement on it as well). Inside RevenueCat it shows the users that are subscribed to this product as having both the old and the new entitlement, which is what we expect.

But inside Firestore it only shows the old entitlement for these users. Shouldn’t this integration receive information on newly created (or deleted) entitlements and add or remove them on the appropriate users?

Maybe this is some sort of cron process on your end that I just need to wait to run? Or does this extension not support that yet?

[jswilliams]

Update: this seems like something that needs to be fixed in the extension. Even subscription renewal events aren’t adding the new entitlement to the user.

(Brand new subscribers do show both entitlements in Firestore however)

[tiinanguyen]

Hey @jswilliams! Any updates from adding / removing products from entitlements should show in the next purchase related event that RevenueCat dispatches.

this seems like something that needs to be fixed in the extension. Even subscription renewal events aren’t adding the new entitlement to the user.

I tried reproducing this behavior by doing the following:

1. Attach product to entitlement A
2. Purchase the product
3. Attach the same product to entitlement B
4. Wait for renewal

When I checked the response body of the Firebase (Firebase function) renewal event, I notice that both entitlements are included in event.entitlement_ids and in customer_info.entitlements.

If you check the response body that was dispatched for renewal events after the product was attached to the 2nd entitlement, do you see them being included under event.entitlement_ids and customer_info.entitlements?