Hi,
We are trying to use revenuecat in order to send an email to our users if they experience a billing problem, letting them know how long they have to fix the issue with their card before the subscription expires.
We assumed that we could use `grace_period_expiration_at_ms` however we have found that is doesn’t line up with when the EXPIRATION event is actually delivered. This applies to both Android and iOS subscriptions. The date given by `grace_period_expiration_at_ms` is way off.
Example (Android):
grace_period_expiration_at_ms: 1645129097417 → Thursday, 17 February 2022 20:18:17
We are also using Stripe for web subscriptions and for those customers `grace_period_expiration_at_ms` is null. We assume this is because Stripe is using “Smart Retries” where it uses its machine learning algorithms to determine the best time to retry, however this makes it pretty much impossible to tell when the EXPIRATION event will arrive.
We have also looked at `expiration_at_ms` which also doesn’t seem to line up.
Is there a way to accurately get when the EXPIRATION event will arrive based off a BILLING_ISSUE event or is this not possible?
