New RevenueCat SDK version improves user identification

  • 22 July 2021
  • 1 reply

Userlevel 6
Badge +8
  • RevenueCat Staff
  • 474 replies

New SDK Releases

In the new SDK version, we’ve redesigned the way that user identification works. 

We introduced two new methods, logIn and logOut, for handling user identification. These replace createAlias, identify and reset.

To take advantage of the new Identity features, you just need to replace identify and createAlias with logIn, and reset with logOut. These new methods hopefully make usage more clear, and there’s some under-the-hood performance improvements you’ll get for free.

New Dashboard Options

Regardless of whether you have started using the new SDK, we’re also introducing a new option in the dashboard so you can configure the desired behavior when two different App User IDs restore the same Apple or Google receipt. Available options are: 

  • Transfer to the new user (default)
  • Block the transfer

This behavior can be changed at any time through the RevenueCat dashboard, and it replaces the deprecated SDK property allowAppStoreAccountSharing.

(Note: Some developers may see the legacy alias option in their dashboard, you can retain this legacy behavior for as long as you’d like. However, once your app has switched away from the legacy behavior, you won’t be able to switch back to it again.)



Together, these new APIs and configurations should make it significantly easier to integrate your accounts system with RevenueCat, and reduce the number of edge cases to consider. 

You can find detailed information about the new Identity features here.

1 reply

Badge +6

Hei there.

Are there any more changes planedon the identity part of the SDK/API?