因此,我的项目遇到的一个问题是,通过谷歌登录并不能保持一致。也就是说,它适用于我的朋友,而不是我的电脑,即使昨天在擦拭我的手机之前它对我有用(手机已损坏)。我们的登录代码是谷歌登录的标准,问题是结果不断返回false我认为。代码:
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.welcome_screen);
findViewById(R.id.sign_in_button).setOnClickListener(this);
GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
.requestEmail()
.build();
mGoogleApiClient = new GoogleApiClient.Builder(this)
.enableAutoManage(this /* FragmentActivity */, this /* OnConnectionFailedListener */)
.addApi(Auth.GOOGLE_SIGN_IN_API, gso)
.build();
SignInButton signInButton = (SignInButton) findViewById(R.id.sign_in_button);
signInButton.setSize(SignInButton.SIZE_STANDARD);
signInButton.setScopes(gso.getScopeArray());
}
@Override
public void onClick(View v) {
switch (v.getId()) {
case R.id.sign_in_button:
signIn();
break;
}
}
private void signIn() {
Intent signInIntent = Auth.GoogleSignInApi.getSignInIntent(mGoogleApiClient);
startActivityForResult(signInIntent, RC_SIGN_IN);
}
public void onActivityResult(int requestCode, int resultCode, Intent data) {
super.onActivityResult(requestCode, resultCode, data);
// Result returned from launching the Intent from GoogleSignInApi.getSignInIntent(...);
if (requestCode == RC_SIGN_IN) {
GoogleSignInResult result = Auth.GoogleSignInApi.getSignInResultFromIntent(data);
handleSignInResult(result);
}
}
private void handleSignInResult(GoogleSignInResult result) {
if (result.isSuccess()) {
// Signed in successfully, show authenticated UI.
GoogleSignInAccount acct = result.getSignInAccount();
// mStatusTextView.setText(getString(R.string.signed_in_fmt, acct.getDisplayName()));
updateUI(acct);
} else {
// Signed out, show unauthenticated UI.
noUpdateUI();
}
}
private void updateUI(GoogleSignInAccount acct) {
Intent intent = new Intent(getApplicationContext(), HomeScreen.class);
Bundle bundle = new Bundle();
bundle.putSerializable("NEW_USER", new ClientUser(acct));
intent.putExtras(bundle);
startActivity(intent);
}
For some reason, the result is false:
private void noUpdateUI() {
System.out.println("**** Try again****");
// mStatusTextView.setText(R.string.signed_out);
findViewById(R.id.sign_in_button).setVisibility(View.VISIBLE);
}
我认为我已经正确设置了应用程序的凭据,因为在我擦拭手机之前,它已经从我的桌面上运行了。值得注意的是,我的朋友在他的笔记本电脑上也遇到了同样的问题,但是他的桌面没有问题。不确定是什么?有什么建议吗?
来自sys.out的日志:
12-16 18:48:43.282 27375-27375/oose2017.place2b D/ViewRootImpl: ViewPostImeInputStage ACTION_DOWN
12-16 18:48:43.412 27375-27375/oose2017.place2b I/Timeline: Timeline: Activity_launch_request id:oose2017.place2b time:3231784
12-16 18:48:43.452 27375-27375/oose2017.place2b D/Activity: performCreate Call Injection manager
12-16 18:48:43.462 27375-27375/oose2017.place2b I/InjectionManager: dispatchOnViewCreated > Target : com.google.android.gms.auth.api.signin.internal.SignInHubActivity isFragment :false
12-16 18:48:43.462 27375-27375/oose2017.place2b D/PhoneWindow: *FMB* installDecor mIsFloating : false
12-16 18:48:43.462 27375-27375/oose2017.place2b D/PhoneWindow: *FMB* installDecor flags : 8454400
12-16 18:48:43.462 27375-27375/oose2017.place2b D/SecWifiDisplayUtil: Metadata value : SecSettings2
12-16 18:48:43.472 27375-27375/oose2017.place2b D/PhoneWindow: *FMB* isFloatingMenuEnabled mFloatingMenuBtn : null
12-16 18:48:43.472 27375-27375/oose2017.place2b D/PhoneWindow: *FMB* isFloatingMenuEnabled return false
12-16 18:48:43.482 27375-27375/oose2017.place2b D/SRIB_DCS: log_dcs ThreadedRenderer::initialize entered!
12-16 18:48:43.492 27375-27584/oose2017.place2b D/mali_winsys: new_window_surface returns 0x3000, [1440x2560]-format:1
12-16 18:48:43.542 27375-27375/oose2017.place2b I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@174719e3 time:3231916
12-16 18:48:43.962 27375-27375/oose2017.place2b V/ActivityThread: updateVisibility : ActivityRecord{1458bd29 token=android.os.BinderProxy@e9978a8 {oose2017.place2b/oose2017.place2b.interfaces.Welcome.WelcomeScreen}} show : true
12-16 18:48:43.962 27375-27375/oose2017.place2b V/ActivityThread: updateVisibility : ActivityRecord{d3e4299 token=android.os.BinderProxy@174719e3 {oose2017.place2b/com.google.android.gms.auth.api.signin.internal.SignInHubActivity}} show : true
12-16 18:48:48.102 27375-27375/oose2017.place2b I/System.out: ***** Try again!*****
12-16 18:48:48.132 27375-27375/oose2017.place2b I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@e9978a8 time:3236507
答案 0 :(得分:8)
我遇到了同样的问题。 我通过以下方式解决了这个问题:
我去了我的build.gradle(app),在defaultConfig中,并将applicationId更改为我的包名(我不知道为什么它最初不一样)。
我从compile 'com.google.android.gms:play-services-auth:8.3.0'
切换到compile 'com.google.android.gms:play-services-auth:8.4.0'
确保apply plugin: 'com.google.gms.google-services'
位于build.gradle(app)的底部,即在依赖项之后
我生成了一个新的SHA-1密钥。要在终端中生成SHA-1密钥,请将其粘贴到keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
然后转到credentials page并选择您的项目。
在OAuth 2.0客户端下,单击您的Android客户端密钥。粘贴您生成的SHA-1密钥和您指定的包名称。点击保存。
然后再次尝试登录。希望它应该工作。 有关详细信息,请参阅此post和this as well。它帮助我解决了我的问题
答案 1 :(得分:1)
我在我的项目中遇到了同样的问题并解决了我生成的 SHA1 密钥
Step1- 在右侧打开 gradle
Step2- 点击执行 Gradle 任务,如图所示
Step3- 输入 gradle signingreport
并按 Enter
第 5 步 - 转到您的 Firebase 控制台并转到项目设置
第 6 步 - 在您的 SDK 设置和配置中,点击添加指纹并在此处粘贴您的 SHA1 密钥,然后点击保存
然后就成功了
答案 2 :(得分:0)
创建GoogleSignInOptions时需要附加Android客户端密钥 像这样
signInOptions = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN).
requestScopes(new Scope(Scopes.EMAIL)).
requestEmail().
requestIdToken(getString(R.string.client_id)).
build();
答案 3 :(得分:0)
我不得不从play-services-auth 16.0.0降级到
implementation 'com.google.android.gms:play-services-auth:15.0.1'
然后它起作用了。
答案 4 :(得分:0)