Skip to main content
Question

Receiving an anonymous ID despite the subscription being identified with our own ID on the client.

  • March 14, 2025
  • 1 reply
  • 9 views

Forum|alt.badge.img

This happens in the sandbox (I haven’t tested it in a production environment yet).

Since I’m also using Superwall, I identified the user in the purchase controller on initialization (client) like this:
 

Purchases.configure({ apiKey: REVENUECAT_API_KEY, appUserID });

 

I’m doing some tests, so I subscribed and I wait for the renewal events to arrive:

 

 

Why does the first renewal arrive with an anonymous ID, and then it gets fixed in the subsequent event? Is this a sandbox issue?

What other info can I provide to help debug this?

This post has been closed for comments

1 reply

Forum|alt.badge.img+8
  • RevenueCat Staff
  • 563 replies
  • March 18, 2025

Hi, an anonymous ID will be generated if configure() is called without a custom app user id, if logOut() is called, or when using the feature “Track new purchases from server-to-server notifications”. If you aren’t calling logOut(), then are you seeing this with your iOS app? If so then this can be due to you having “Track new purchases from server-to-server notifications” enabled for this app. I recommend disabling this and seeing if this still occurs.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings