But if the user has an anonymous ID, calling syncSubscriptions will just discard that anonymous ID the user does in fact have a subscription (I believe).
I don’t see any downsides to it, but I could be missing something.
It's okay to trigger a sync once per subscriber programmatically the first time they open a version of your app containing RevenueCat. You should not call this programmatically on every app launch for every user. This can increase latency in your app and can unintentionally alias users together.
If you didn’t configure with an appUserId, then you’ll start aliasing anon ids together.
It's okay to trigger a sync once per subscriber programmatically the first time they open a version of your app containing RevenueCat. You should not call this programmatically on every app launch for every user. This can increase latency in your app and can unintentionally alias users together.
If you didn’t configure with an appUserId, then you’ll start aliasing anon ids together.
Thanks @Ryan Glanz . My approach is to store a flag in device storage recording whether I’ve synced purchases on that device. For every fresh install, that flag will be undefined, and so then I’ll sync purchases, and set the flag to `true`.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.