Skip to main content
Question

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


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?

0 replies

Be the first to reply!

Reply


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