Hello! when user make purchase new alias created, even on Webhooks there is only 1 alias and original app user id is no correct I am losing subscribers right now and getting refund because I cannot update the user as premium
Please check screenshots
I perceive that my sdk version were 5.6.0 when I update it it updated to 5.20.0 maybe that was the issue
still losing users since your system does not detect the user id nor revenuecat id , your system create new account when purchase made lol. what a shame for revenue cat, I am gonna think about change my whole system.. 1 more user..
Hi @hexadec. I see that you still have server purchase tracking enabled, which can create anonymous IDs if the server notification gets posted to our servers before the receipt gets posted from the device. If you only want to have custom app user IDs, please follow these instructions:
Hi @hexadec - To ensure you only use custom app user IDs, there are a few things you need to ensure:
Never call configure without passing in a custom user ID
Never call logOut. If you want to login a different user, just call login without first calling logOut
when I turned off this feature , some purchases cannot be visible on revenuecat neither web hook works?
if I turn of this feature I cannot catch user made premium right?
All purchases will be posted from your users’ devices to RevenueCat after making a purchase. You don’t need to have server purchase tracking enabled for purchases to work. You should have server notifications (iOS, Android) enabled, but this is different from server purchase tracking.
Also, part of this issue stems from the fact that you’re only saving custom IDs in your backend, and unlocking entitlements there. You may want to also save anonymous IDs to your database in the case that anonymous IDs are created (either through server purchase tracking, or if you inadvertently call logOut or configure without a provided user ID). Doing so would make your system more flexible, though I understand it will likely change your schema.
To sum up for now - please disable server purchase tracking. This should remove anonymous IDs in the meantime.
Hello! when user make purchase new alias created, even on Webhooks there is only 1 alias and original app user id is no correct I am losing subscribers right now and getting refund because I cannot update the user as premium
Please check screenshots
I perceive that my sdk version were 5.6.0 when I update it it updated to 5.20.0 maybe that was the issue
?
Page 1 / 1
Hi @hexadec - To ensure you only use custom app user IDs, there are a few things you need to ensure:
Never call configure without passing in a custom user ID
Never call logOut. If you want to login a different user, just call login without first calling logOut
Can you ensure these are all completed and let me know if it resolves the issue? Thanks!
when I turned off this feature , some purchases cannot be visible on revenuecat neither web hook works?
if I turn of this feature I cannot catch user made premium right?
can someone explain me why new alias created after purchase made?
still losing users since your system does not detect the user id nor revenuecat id , your system create new account when purchase made lol. what a shame for revenue cat, I am gonna think about change my whole system.. 1 more user..
Hi @hexadec. I see that you still have server purchase tracking enabled, which can create anonymous IDs if the server notification gets posted to our servers before the receipt gets posted from the device. If you only want to have custom app user IDs, please follow these instructions:
Hi @hexadec - To ensure you only use custom app user IDs, there are a few things you need to ensure:
Never call configure without passing in a custom user ID
Never call logOut. If you want to login a different user, just call login without first calling logOut
when I turned off this feature , some purchases cannot be visible on revenuecat neither web hook works?
if I turn of this feature I cannot catch user made premium right?
All purchases will be posted from your users’ devices to RevenueCat after making a purchase. You don’t need to have server purchase tracking enabled for purchases to work. You should have server notifications (iOS, Android) enabled, but this is different from server purchase tracking.
Also, part of this issue stems from the fact that you’re only saving custom IDs in your backend, and unlocking entitlements there. You may want to also save anonymous IDs to your database in the case that anonymous IDs are created (either through server purchase tracking, or if you inadvertently call logOut or configure without a provided user ID). Doing so would make your system more flexible, though I understand it will likely change your schema.
To sum up for now - please disable server purchase tracking. This should remove anonymous IDs in the meantime.
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.