We have an app that requires the users to login before making a purchase.We’re observing (in our sandbox testing) that occasionally a users subscription gets transferred from one of our users id’s to an anonymous id. What's quite frustrating is this is happening very infrequently and we haven’t been able to recreate it predictably.Here is an example event (id: 0a5fc80d-ca5a-451a-8a31-cb16b95a3a92){ "event_timestamp_ms": 1643816650712, "store": "APP_STORE", "transferred_from": [ "ce3873cc-10a7-46d0-9463-43364f6b2cb8", "$RCAnonymousID:6a5e992f89a44858b2a8effa6996f257" ], "transferred_to": [ "$RCAnonymousID:a0490b63949a4b6e99a3bf372b3da781" ]} Our touch points with the React Native SDK are rather light:We have an useEffect() that calls Purchases.setup(key) with our keys in our main App.tsx as per the examples. When a user logs into our app we call Purchases.logIn(user.id) using the response to set our initial local subscription state. To keep things up to date we call Purchases.getPurchaserInfo when the user brings the app back into the foreground if they are logged in and have a requestDate that's more than 5 minutes old. We call Purchases.logOut() when the user hits the Logout action in our UI.Sometimes (rarely) when a user logs out and back into our app the above style event will occur.What I can assume (but can’t validate) is somewhere in our implementation we’re causing the SDK to transfer the purchases when the user is logged out. But I'm unclear what part of the SDK would do that? The visible effect this has on us is that the user that does log in (i.e ce3873cc-10a7-46d0-9463-43364f6b2cb8 from example event). They don't have any subscription information as its been transferred to the anonymous user. Oddly when this does happen if they log out and back in again it gets transferred back to them. Would appreciate any guidance here as theres a good chance we’re doing something wrong but since it works 90% of the time its difficult to pin point what may be wrong.

@NizzaSorry for the delayed response, and thanks so much for your patience.I believe what’s happening is:log instart subscriptionlog outsubscription renewal comes inAt step 4, when the renewal comes in, the SDK posts the receipt to our backend, but at this point, you’re an anonymous user. So the backend is transferring the receipt, to make sure that whoever’s currently using the device, even if not logged in, doesn’t get locked out.For this case, the best course of action would be to have a restore button available somewhere in your app once you’re logged in.Note that in practice in production this is fairly rare, since logging out of apps is rare in the first place, and more so when you have an active subscription. But you should still take care of this case, so providing a way for customers to restore purchases once they log back in should suffice.Hope this helps shed some light on the matter! Let me know if you have any more questions!

Solved

App IDs transferring subscriptions to anonymous users

2 years ago
2 February 2022
27 replies
1499 views

N

Userlevel 1

+2

Nizza
Member
9 replies

We have an app that requires the users to login before making a purchase.

We’re observing (in our sandbox testing) that occasionally a users subscription gets transferred from one of our users id’s to an anonymous id. What's quite frustrating is this is happening very infrequently and we haven’t been able to recreate it predictably.

Here is an example event (id: 0a5fc80d-ca5a-451a-8a31-cb16b95a3a92)

{
  "event_timestamp_ms": 1643816650712,
  "store": "APP_STORE",
  "transferred_from": [
    "ce3873cc-10a7-46d0-9463-43364f6b2cb8",
    "$RCAnonymousID:6a5e992f89a44858b2a8effa6996f257"
  ],
  "transferred_to": [
    "$RCAnonymousID:a0490b63949a4b6e99a3bf372b3da781"
  ]
}

Our touch points with the React Native SDK are rather light:

We have an useEffect() that calls Purchases.setup(key) with our keys in our main App.tsx as per the examples.
When a user logs into our app we call Purchases.logIn(user.id) using the response to set our initial local subscription state.
To keep things up to date we call Purchases.getPurchaserInfo when the user brings the app back into the foreground if they are logged in and have a requestDate that's more than 5 minutes old.
We call Purchases.logOut() when the user hits the Logout action in our UI.

Sometimes (rarely) when a user logs out and back into our app the above style event will occur.

What I can assume (but can’t validate) is somewhere in our implementation we’re causing the SDK to transfer the purchases when the user is logged out. But I'm unclear what part of the SDK would do that?

The visible effect this has on us is that the user that does log in (i.e ce3873cc-10a7-46d0-9463-43364f6b2cb8 from example event). They don't have any subscription information as its been transferred to the anonymous user. Oddly when this does happen if they log out and back in again it gets transferred back to them.

Would appreciate any guidance here as theres a good chance we’re doing something wrong but since it works 90% of the time its difficult to pin point what may be wrong.

icon

Best answer by Andy 15 February 2022, 21:50

View original

Show first post Hide first post

27 replies

1
2

Page 2 / 2

N

Userlevel 1

+2

Nizza
Author
Member
9 replies
2 years ago
4 February 2022

Does anyone have any suggestions here? It’s a bit of a red flag for us at the moment. :grimacing:

If nothing else if anyone can confirm whether or not its the desired behaviour that the Revenue Cat SDK will automatically transfer purchases to the account that's currently logged in (even anonymous) if a user returns to our app with a different user id (or anonymous) having made a purchase previously?

If the above is true can someone confirm what role restoreTransactions() does as it seems to be happening automatically for us?

If this the case is our work around to never really call Purchases.logOut() and just rely on the fact that if the user logs in with a different account later, the subsequent call to Purchases.logIn() will swap them over?

N

Userlevel 1

+2

Nizza
Author
Member
9 replies
2 years ago
3 February 2022

Ok so doing some more investigation we think we understand what is happening. I’m just not 100% sure if it is desired behaviour. I’ve detailed steps to try and recreate below, hoping someone with more experience will explain if this is correct behaviour.

Open app and call set up (We have an anonymous id here as expected)
User creates an account - We call login with the id
User subscribes, purchase recorded in RC and alias for the User ID is set against the previous anonymous id. All good so far.
User logs out (Purchases.logOut)
User backgrounds the app (or quits?)
User re-opens the app (still logged out) after 5 - 15 mins (the cache period)
RC transfers their purchase to the anonymous ID.

{
  "event_timestamp_ms": 1643903636840,
  "store": "APP_STORE",
  "transferred_from": [
    "c56acef2-039e-4a10-8ee4-ed2c1ff3772f",
    "$RCAnonymousID:4fbb22f4be4b4f1abdace65eb5edb799"
  ],
  "transferred_to": [
    "$RCAnonymousID:b4ae34bbe4a04d5da4a02f85bd37a93b"
  ]
}

Our assumption going into this was that in order to transfer a purchase you had to manually with restoreTransactions. This appears to restore the transactions to whatever user ID is currently active when it enters the foreground after the cache period is over?

One rather big downside to this behaviour is if the user then logs back into their regular account the getPurchaserInfo() returns no subscription info as its all been transferred to the anonymous user. If we return around 5 - 15 minutes later the call to getPurchaserInfo() then works as the purchase has been transferred back.

We could be way off base here and would really appreciate some clarification on whether this is expected or not?

1
2

Page 2 / 2

Reply

Sign up

‏‏‎ ‎

Log in to the Community

‏‏‎ ‎

Scanning file for viruses.

This file cannot be downloaded