Are there downsides to calling Purchases.shared.login(<id>) several times?
I don’t load the user id until the user has hit a shared TabBarController inside the my app after logging in through a third party. This call is reused whenever a user refreshes data or reopens the app.
I’d like to call Purchases.login whenever user data is loaded. This can happen several times during a session, although typically it only happens once.
This would be the simplest way to fill ids. I think it would also backfill existing users who won’t go through a login flow again.
Best answer by sharifView original