Skip to main content

Hi,

I have a blind spot when users delete their account from my Flutterflow app. That is, any paid subscriptions stored in RevenueCat remain live. Currently, only the anon Apple ID is attached to the RevenueCat record (this isnt stored in my auth users database though).

 

The simple solution would be to also set the Apple email in the RevenueCat Customer record - then I can find a match with my auth users record.

 

How can I have RevenueCat store the email (aswell as the Apple ID) when a purchase is made please?

 

I’m not a coder and so I was hoping it was a settings adjustment, but I can’t see this anywhere.

 

Many thanks for your time.

Anyone able to help, please?


Are there any Community Managers on this forum?


Hi ​@carl-cd4c83 - stepping back a bit, are you hoping to automatically cancel users’ subscriptions when they delete your app? If so, Apple doesn’t provide a way for developers to manage subscriptions on their customers’ behalf. Instead, customers will have to cancel their subscriptions via Settings on their iPhones.

For privacy reasons, Apple doesn’t provide the Apple ID or email address on the underlying receipt (which is what RevenueCat reads to unlock entitlements). If you ask your users for an email address, you can save it as a customer attribute, but this would make more sense if you also use custom app user IDs and an authentication system (not only using anonymous IDs), as the email would then be associated with a durable user ID.

Let me know if you have additional questions. Thanks!


Thank you for your reply.

 

I am wondering how to handle subscribers to my app, who then delete a subscription within Apple. How can that action inform my supabase users table (so their permissions are restricted)? 

Thank you


@carl-cd4c83 If you enable App Store Server Notifications, RevenueCat will be notified of any change in your customers’ subscription status. We can then send you webhooks, which you can use to modify your database. You can always rely on the RevenueCat SDK to fetch subscription status, however, instead of duplicating this in your database.