Finish migration to Play Games Services v2. #122
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It turns out that Play Games Services v2 includes SavedGame access by default, so we can do away with separate sign-ins and move fully to v2. This wraps up the transition with the following:
isSignedIn
getter to use the v2isAuthenticated
check.signIn
.enableSavedGames
argument fromsignIn
method.isAuthenticated
check fromsignIn
. (In v2, this should only be used to check sign-in status by the end dev. As sign-in happens automatically,signIn
should only be a fallback sign-in option used by the end dev as needed, i.e. if a sign-in button is pressed.signOut
method, as there is no concept of a sign-out method in v2 from a developer perspective. This is now only handled at the system level.