User alias is created with delay using Purchases.getSharedInstance().logIn

Hi,

We’ve outlined some considerations for avoiding anonymous ids here: https://www.revenuecat.com/docs/user-ids#how-to-only-use-custom-app-user-ids

Are you calling logout() or configure() without a custom id?

Hi @Ryan Glanz 

We're calling configure without a custom id because our app doesn't require users to log in, users that do not log in can still use our app and purchase consumables for their single device usage. The real issue here is not about avoiding anonymous ids, but about the timing when the alias happens on server.

@Ryan Glanz Any updates or advice?

Sorry for the delay on this, I sent you an email because I’ll need some account-specific info.

any updates on this issue, I myself faced this during testing

Been 10 months and RC has this issue with no comments from the team

Hey @f-d-e8d39c,

The community is meant for all users to chime in, and we don’t necessarily respond to all posts. If you do have an issue, always feel free to open up a support ticket here: https://app.revenuecat.com/settings/support
For this issue, it looked like the developer ultimately got the behavior they were looking for my ensuring they had called login() before calling purchase(), and if they hadn’t, they call it right before.

We are facing the same issue. It seems like a racing condition:

In our case, the flow is that the user signs up (we then use the Login method), and immediatley showing a paywall screen. some users start the free trial as they see the paywall, but RC is not fast enough and the webhook received with the anonymous user.

How about this flow?

1. Use your app’s authentication

2. Use our configure() method and pass in the appUserId (so, no need for login method)

3. Show the paywall (make sure to wait for the configuration to finish, of course)

You won’t be able to show the paywall until our SDK is configured, and the user will be identified with the App User Id you pass into the configure method