Instead, the current user, as determined by the Identity API is exposed via the getCurrentUser() method. The setUserIdentity() and setUserAttribute() methods are deprecated as at version 5. The UserAliasHandler gives you the option to copy over attributes currently held in local storage to the new user profile. When transitioning from one user to another, usually as a previously anonymous user creates an account and becomes a known user, some Identity Strategies will alias the old anonymous profile to the new known one.
You should also update the current User Identity at appropriate points in your app lifecycle, such as Login and Logout. If you do not specify a request, identify will be called with the most recently stored user identities. You may include an Identity request when you initialize the SDK. This approach has been deprecated in favor of more explicit user management via the Identity API. Previously, current user identities and attributes were set at the level of the device and included with any outgoing uploads. start() the SDK without providing an options object. It is now required to configure the SDK by supplying an MParticleOptions argument when you.
Check with your Customer Service Manager before migrating if you are unsure. We are currently in the process of migrating accounts. Version 5 requires that your account be enabled for IDSync. MParticle released Android SDK version 5 in late 2017, including breaking changes to support the new Identity API.
0 kommentar(er)
