Hello, we are working on our second mobile title using Playfab, in which players first login using their iOS or Android DeviceId, and later register their account using email and password. The problem we anticipate is with players that had already registered an account in our first game, when they try to register their account on the second game and they can't because that email is already 'taken' (since player accounts are shared across all publisher titles, and email accounts are unique).
Of course, it would be ideal if the player was signed in straight away into their existing account from the first game, and didn't need to register again in the new game. That's unlikely to happen in most cases, though, as we cannot ask them to log in with their existing account from the first game (we technically could, but it's off the table for commercial reasons) and we can't trust their DeviceId to be the same one as the one linked to their existing account.
Has anyone faced this problem before? Any suggestion on how to best approach it? The only reliable solution we can think of is to create a new Publisher in the Playfab dashboard and house the new title there, but we imagine there has to be a better way to do it.
Thank you in advance!
Answer by Joshua Strunk · Feb 20, 2018 at 05:14 PM
Considering you are not wanting to share accounts across titles for commercial reasons, creating a new publisher is the only logical option. You are bound to run into more issues than just email registrations already being taken considering the assumption is that all title's in a publisher will share the same user creditials.
Thank you for the quick answer! We will do that then.
AddUsernamePassword requires both email and username while Other APIs do not? 1 Answer
Google account IDs don't match 1 Answer
Get Language List fails at Entity Authentication 2 Answers
Deny CreateAccount in LoginWithCustomIDRequest 1 Answer
Best practice for caching a previously authenticated user? 2 Answers