Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more parity with iOS (breaking change), refactor module, fix theming #32

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

hansemannn
Copy link
Contributor

@hansemannn hansemannn commented Feb 23, 2019

Hey there,

this pull attempts to add more parity with iOS, especially for the returned profile inside the login event (commit 1). Also, this pull adds some meta files so this module can easily be developed inside Android Studio. Let me know if you want to take those changes as well or if I should remove them again.

Cheers!


Also closes #30 and #9. I'd even argue that all open issues should be closed. Most of them (#28, #14, #29, #18, #17) are questions and should be moved to StackObverflow or TiSlack.

Download: ti.googlesignin-android-4.0.0.zip

@hansemannn
Copy link
Contributor Author

@AppWerft This PR is ready for review. cc @chmiiller since you heavily use this module as well I think.

@hansemannn hansemannn changed the title Add more parity with iOS (breaking change) Add more parity with iOS (breaking change), refactor module, fix theming Mar 22, 2019
} else {
Log.d(LCAT, "no clientID found!");
Log.e(LCAT, "No clientID found!");
return;
}

GoogleSignInOptions gso = new GoogleSignInOptions.Builder(
GoogleSignInOptions.DEFAULT_SIGN_IN)
.requestIdToken(serverClientId).requestProfile().requestEmail()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to get more parity with iOS, we should add here .requestServerAuthCode(serverClientId) because currently it returns null whereas iOS returns right.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that have side-issues? If we don't request the id-token, will it still include the idToken? EDIT: See this for details. We should probably not change that?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mmm I see, I'm using it to authorize my server as stated https://developers.google.com/identity/sign-in/android/offline-access. I'm not an expert on this, just my use case requires to have both in order to get the same response than in iOS module

@AndreaVitale
Copy link

Used this PR in my app. Thank you @hansemannn !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Transparent Window during sign in and avoid animation
3 participants