While this is not an explicit bug, it might be misdiagnosed as one.
This has to do more with the nuances of the Taplytics product and properly using the resetUser method call.
Why you might see more devices than the number you currently have to test could be the case where you’re rebuilding new versions of your apps and app users are not getting registered/de-registered properly.
If you’re re-building your app with different versions and build numbers during QA and deleting/re-installing without logging in and logging out, each install will be most likely show up as an entirely different user.
To get around this, we have a resetUser call that can deactivate the old users when you log out. Please see our iOS SDK documentation here!
Comments
2 comments
Hi Will, so when i call `resetUser` — will that delete information about that user from analytics too? I'm afraid of a following scenario: what if our user logs out (we call resetUser() ) and then logs back in — will we lose all previous engagement data about that user?
Thanks!
Hey Raman,
No, it doesn’t delete the user. It's more of a logout function. It removes that device from that user and creates a new anonymous user. When that user logs back in they will get that same user with all data intact.
Please sign in to leave a comment.