Closed danieljimeneznz closed 3 years ago
Hey, thanks for your feedback. This is not a bug, this is how system works. We do re-use old profiles in case user identifies with their ids and at the same time we keep those "dummy" profiles in DB. We can't remove such "dummy" profiles for now, but definitely will do that in future.
@AKyashkin thanks for the clarification, feel free to close this issue.
Any update on removing these dummy profiles? I hate seeing them in the console. Is there any reason why Adapty.activate has to be in the App delegate and not on Login?
Any updates?
Hi, @aritroper and @georgedavid1990! Since this issue is not directly related to the SDK functionality, I suggest you email this question to support@adapty.io.
Reproduction steps
Adapty.activate()
). => New blank user (User A) is created in the console1234
i.e.Adapty.identify("1234")
. => Previous blank user (User A) is now linked to user via customerId 1234Adapty.logout()
=> New blank user (User B) is created in the consoleAdapty.identify(1234)
=> Previous user is used for identification (User A).Continue to log in a user, and logout a user to generate more garbage users in the console.
Expected behavior
Since User B has essentially mutated into User A through the identify call, I wouldn't expect to see User B in the console. (I was curious if this was the expected behaviour by the Adapty team or indeed a bug)
(I tried bypassing this bug by only calling
identify
on Login but when another user logs in, they mutate the previous users Adapty Profile)