Migrated:
Home Page: https://github.com/android/identity
License: Apache License 2.0
This repo has been migrated to github.com/android/identity. Please check that repo for future updates. Thank you!
Hash key generated is not working for released apk. Do we have different keys for released and debug mode. What changes in program we need to make to get the key for released mode.
In short: onReceive method of the broadcast receiver is not catching the BroadCast when the Android system receives SMS.
Hi, I am trying to learn SMS Verifier API using this client app and Twilio app offered in here.
The app works all fine. Signing with SMS login works very well; but, SmsBrReceiver is failing to "onReceive" any SMS.
While the SmsBrReceiver(BroadCastReceiver) being kicked, I manually executed am broadcast -a "com.google.android.gms.auth.api.phone.SMS_RETRIEVED" --es "from" "whatever", and onReceives catches it without any problem.
What is being wrong?
Following is the log from the app after I input and submit the phone number.
07-14 22:08:50.856 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: ViewPostImeInputStage processPointer 0
07-14 22:08:50.947 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: ViewPostImeInputStage processPointer 1
07-14 22:08:50.948 16946-16946/com.google.samples.smartlock.sms_verify D/SignUpActivity: Using the phone number.
07-14 22:08:51.070 16946-16946/com.google.samples.smartlock.sms_verify D/ApiHelper: GMS Version: 11055440
07-14 22:08:51.125 16946-24931/com.google.samples.smartlock.sms_verify I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
07-14 22:08:51.125 16946-24931/com.google.samples.smartlock.sms_verify I/System.out: (HTTPLog)-Static: isSBSettingEnabled false
07-14 22:08:51.130 16946-24131/com.google.samples.smartlock.sms_verify D/FA: Logging event (FE): user_engagement(_e), Bundle[{firebase_event_origin(_o)=auto, engagement_time_msec(_et)=23945, firebase_screen_class(_sc)=SignUpActivity, firebase_screen_id(_si)=-5661710448375795420}]
07-14 22:08:51.252 16946-24131/com.google.samples.smartlock.sms_verify D/FA: Logging event (FE): screen_view(_vs), Bundle[{firebase_event_origin(_o)=auto, firebase_previous_class(_pc)=SignUpActivity, firebase_previous_id(_pi)=-5661710448375795420, firebase_screen_class(_sc)=MainActivity, firebase_screen_id(_si)=-5661710448375795422}]
07-14 22:08:51.282 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: Relayout returned: oldFrame=[0,0][1440,2560] newFrame=[0,0][1440,2560] result=0x7 surface={isValid=true 532861273088} surfaceGenerationChanged=true
07-14 22:08:51.282 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: mHardwareRenderer.initialize() mSurface={isValid=true 532861273088} hwInitialized=true
07-14 22:08:51.300 16946-17016/com.google.samples.smartlock.sms_verify D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000, [1440x2560]-format:1
07-14 22:08:51.311 16946-24131/com.google.samples.smartlock.sms_verify D/FA: Connected to remote service
07-14 22:08:51.380 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: MSG_RESIZED_REPORT: ci=Rect(0, 96 - 0, 0) vi=Rect(0, 96 - 0, 880) or=1
07-14 22:08:51.380 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: MSG_WINDOW_FOCUS_CHANGED 1
07-14 22:08:51.380 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: mHardwareRenderer.initializeIfNeeded()#2 mSurface={isValid=true 532861273088}
07-14 22:08:51.386 16946-16946/com.google.samples.smartlock.sms_verify D/SEM_CLIP_SemClipboardManager: isCocktailBarDisplayed : false
07-14 22:08:51.390 16946-16946/com.google.samples.smartlock.sms_verify I/InputMethodManager: [IMM] startInputInner - mService.startInputOrWindowGainedFocus
07-14 22:08:51.400 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel constructed: fd=101
07-14 22:08:51.400 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel destroyed: fd=85
07-14 22:08:51.443 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: MSG_WINDOW_FOCUS_CHANGED 0
07-14 22:08:51.444 16946-16946/com.google.samples.smartlock.sms_verify D/SEM_CLIP_SemClipboardManager: isCocktailBarDisplayed : false
07-14 22:08:51.446 16946-16946/com.google.samples.smartlock.sms_verify W/IInputConnectionWrapper: finishComposingText on inactive InputConnection
07-14 22:08:51.446 16946-16946/com.google.samples.smartlock.sms_verify W/IInputConnectionWrapper: finishComposingText on inactive InputConnection
07-14 22:08:51.471 16946-17016/com.google.samples.smartlock.sms_verify D/OpenGLRenderer: endAllActiveAnimators on 0x7c305e6000 (InsetDrawable) with handle 0x7c130a76e0
07-14 22:08:51.471 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: mHardwareRenderer.destroy()#1
07-14 22:08:51.478 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: Relayout returned: oldFrame=[0,0][1440,2560] newFrame=[0,0][1440,2560] result=0x5 surface={isValid=false 0} surfaceGenerationChanged=true
07-14 22:08:51.478 16946-16946/com.google.samples.smartlock.sms_verify W/IInputConnectionWrapper: finishComposingText on inactive InputConnection
07-14 22:08:51.496 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: MSG_RESIZED: ci=Rect(0, 96 - 0, 0) vi=Rect(0, 96 - 0, 0) or=1
07-14 22:08:51.782 16946-16946/com.google.samples.smartlock.sms_verify D/PhoneNumberVerifier: SmsRetrievalResult status: Success
07-14 22:08:51.804 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: ThreadedRenderer.create() translucent=true
07-14 22:08:51.808 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel constructed: fd=85
07-14 22:08:51.808 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: setView = android.widget.LinearLayout{7a923ea V.E...... ......I. 0,0-0,0} touchMode=true
07-14 22:08:51.815 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: dispatchAttachedToWindow
07-14 22:08:51.835 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: Relayout returned: oldFrame=[0,0][0,0] newFrame=[269,2128][1171,2304] result=0x27 surface={isValid=true 532861269504} surfaceGenerationChanged=true
07-14 22:08:51.835 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: mHardwareRenderer.initialize() mSurface={isValid=true 532861269504} hwInitialized=true
07-14 22:08:51.835 16946-17016/com.google.samples.smartlock.sms_verify D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000, [902x176]-format:1
07-14 22:08:51.844 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: MSG_RESIZED_REPORT: ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
07-14 22:08:53.817 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: mHardwareRenderer.destroy()#4
07-14 22:08:53.831 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: ThreadedRenderer.create() translucent=true
07-14 22:08:53.840 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel constructed: fd=96
07-14 22:08:53.841 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: setView = android.widget.LinearLayout{13c6451 V.E...... ......I. 0,0-0,0} touchMode=true
07-14 22:08:53.842 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@6449fd5[Toast]: dispatchDetachedFromWindow
07-14 22:08:53.865 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel destroyed: fd=85
07-14 22:08:53.870 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: dispatchAttachedToWindow
07-14 22:08:53.905 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: Relayout returned: oldFrame=[0,0][0,0] newFrame=[413,2128][1027,2304] result=0x27 surface={isValid=true 532861269504} surfaceGenerationChanged=true
07-14 22:08:53.906 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: mHardwareRenderer.initialize() mSurface={isValid=true 532861269504} hwInitialized=true
07-14 22:08:53.907 16946-17016/com.google.samples.smartlock.sms_verify D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000, [614x176]-format:1
07-14 22:08:53.928 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: MSG_RESIZED_REPORT: ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
07-14 22:08:55.817 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: mHardwareRenderer.destroy()#4
07-14 22:08:55.824 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5ea9578[Toast]: dispatchDetachedFromWindow
07-14 22:08:55.838 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel destroyed: fd=96
07-14 22:09:01.164 16946-16946/com.google.samples.smartlock.sms_verify D/Graph: removeVertex() : insertDummyVertex, because there is no ancestor.
07-14 22:09:01.169 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: mHardwareRenderer.destroy()#4
07-14 22:09:01.169 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@5aa3c49[SignUpActivity]: dispatchDetachedFromWindow
07-14 22:09:01.179 16946-16946/com.google.samples.smartlock.sms_verify D/InputTransport: Input channel destroyed: fd=93
07-14 22:09:01.450 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: ViewPostImeInputStage processPointer 0
07-14 22:09:01.460 16946-16946/com.google.samples.smartlock.sms_verify D/ViewRootImpl@4e0cc3a[MainActivity]: ViewPostImeInputStage processPointer 1
hi, i'm using google play services compile 'com.google.android.gms:play-services-auth:11.0.4' . After follow tutorial implemented here https://developers.google.com/identity/sms-retriever/overview , the phone number selector didn't come. I test it with function setEmailAddressIdentifierSupported(true) works well but setPhoneNumberIdentifierSupported is not show the intent
I receive this error. I believe I need the google-services.json file that is signed with 'com.google.samples.smartlock.sms_verify'
Error:Execution failed for task ':app:processDebugGoogleServices'.
No matching client found for package name 'com.google.samples.smartlock.sms_verify'
SMS Verification with SMS Retriever API auto fetch issue
I'm trying to use Google's SMS Retriever API for Automatic SMS Verification, but there is an issue in it. previously , I was reading sender number using getOriginatingAddress() and if it's valid sender number then read OTP otherwise it should not read msg. As , forwarded OTP is disturbing user's privacy.
I have the following scenario.
My app is auto-fetching forwarded OTP messages.
User A installs app on his mobile and enters User B mobile number.
User B receives OTP and forwards it to User A.
App reads OTP on User A mobile and goes to home screen.
is there any way around to get sender number?
My use case is accessing a server's login screen via Javascript without an opportunity to inject the username and password from native code. The server returns a token in a roundabout way, via the web with an intent and intent filter. What are the alternatives to:
signInWithPassword(credential.getId(), credential.getPassword());
when I retrieve the Credential?
The logic of my app, which has dynamic and diverse authentication servers, is to come back from a successful login with an API call String that is encrypted on the device for future use. Can I use SmartLock with this use case?
I am trying SmartLock to support devices that do not have Lollipop and later authentication APIs.
Refer to this Stack Overflow
Thanks in advance for any suggestions.
By using AppSignature class I got hash key IV2kdanxlm6 , SMS content is Your unique Prepathon verification code is 7357. Happy Learning, Team Prepathon. IV2kdanxlm6 Still BroadCastReceiver is not getting fired . I have followed all the steps as shown here https://android-developers.googleblog.com/2017/10/effective-phone-number-verification.html . Am I doing anything wrong ?
When I use iTerm2 terminal and work with the file, it shows:
base64: invalid input
But still generating some part of a wrong certificate in hex and generating a wrong SMS Retriever hash code as well.
But when I use regular Terminal, it works well.
A sample wrong output:
➜ Desktop ./sms_retriever_hash_v9.sh --package com.example.test --keystore /path/keystore.jks
package name: com.example.test
keystore file: /path/keystore.jks
File /path/keystore.jks is found.
Enter keystore password: password
base64: invalid input
certificate in hex: 328202c5308201ada00362010202043d1336f8300d06092a864486f70d01010b050030133111300f0603550403430853
SHA-256 output in hex: bf0ae40bf16485b2320765f3c824e263dfba8d09ec46307d6b4dd3153cfbc287
First 8 bytes encoded by base64: ywrkS/HkhbI
SMS Retriever hash code: ywrkS/HkhbI
Machine: Mac OS 10.14.5
iTerm2 version: 3.2.9
It's possible to get the full phone number using the SMS Retriever API, but we can get only the country code?
Hello,
I see that this API supports Facebook. But how to properly use with it? there have no technique to connect in "silent" with the Facebook SDK.
Can you explain how we should use it ?
Thank you.
Hi,
I'm trying to implement a transparent sign in to existing logged in users on new devices via SmartLock and Google Sign in.
The suggested flow is:
Everything works great except for step 5, the silent login returns
Status{statusCode=SIGN_IN_REQUIRED, resolution=null}
I made sure and neither Auth.GoogleSignInApi.signOut / Auth.GoogleSignInApi.revokeAccess access were called in between.
I tried as well to use the regular login method,Auth.GoogleSignInApi.getSignInIntent but in that case the user sees the popup to select an account (even though there is only a single account) so that doesn't work as well.
So my question is why does the SIGN_IN_REQUIRED status is returned and how to resolve it?
According to the silentSignIn docs I see no reason why it shouldn't work:
If your user has never previously signed in to your app on the current device, we can still try to sign them in, without displaying user interface, if they have signed in on a different device.
We attempt to sign users in if:
There is one and only one matching account on the device that has previously signed in to your application, and
the user previously granted all of the scopes your app is requesting for this sign in.
Last note, I even tried to do test it on the same device by just clearing the app data after successful sign in and even then i'm seeing the same results.
Let me know if you need me to provide any other information
Thank you!
How does one retrieve the OTP sms sender/originator ID?
This works well with SMS from another phone but the broadcast receiver can’t read the SMS from server with the same content.
Do you have any solution for this issue?
/com.google.example.credentialssignin D/MainActivity: handleGoogleSignIn:Status{statusCode=DEVELOPER_ERROR, resolution=null}
I get this error in my LogCat after trying to sign in through the sample app credentials-signin
Am I missing something?
Hello,
I use the Google Play services (version 11.4.0), I'm able to send a SMS and retrieve the message by the BroadcastReceiver (as in your example "SMS Verify App") if the SMS message begins with "<#>".
Unfortunately, if I replace "<#>" by two consecutive zero-width space characters, my BroadcastReceiver is not called and I finally received a callback 5min later for a timeout. I use this format, "\u200b\u200b", to write these two characters in unicode with my server (Java).
I wonder if it's a bug or if I miss something...
Gabriel
Hi,
I'm trying to test out smart lock to see if I should start using it in my app. I cloned the project and ran the credentials-signin project on my phone, but when I try to save a new credential, I get the following error. I looked the error code up and it is the error code for resolution required
save:FAILURE
com.google.android.gms.common.api.ApiException: 6: Passphrase required.
at com.google.android.gms.common.internal.zzb.zzy(Unknown Source:14)
at com.google.android.gms.common.internal.zzbk.zzz(Unknown Source:0)
at com.google.android.gms.common.internal.zzbl.zzr(Unknown Source:32)
at com.google.android.gms.common.api.internal.BasePendingResult.zzc(Unknown Source:46)
at com.google.android.gms.common.api.internal.BasePendingResult.setResult(Unknown Source:42)
at com.google.android.gms.internal.zzavw.setResult(Unknown Source:2)
at com.google.android.gms.internal.zzavv.zze(Unknown Source:2)
at com.google.android.gms.internal.zzawc.onTransact(Unknown Source:46)
at android.os.Binder.execTransact(Binder.java:682)
So, I was wondering why this error was happening and how to resolve it. After looking at the saveCredential(), it seems like the exception should've been an instance of ResolvableApiException.
Thanks,
Jeffrey
When I trying to retrieve phone number with Credentials api some device failed to showing phone number picker dialog and just showing empty dialog and the dialog disappear quickly with sliding animation.
Below is my code sample. (And I also tried with google sample)
val hintRequest = HintRequest.Builder()
.setPhoneNumberIdentifierSupported(true)
.setEmailAddressIdentifierSupported(false)
.build()
val options = CredentialsOptions.Builder()
.forceEnableSaveDialog()
.build()
val pendingIntent = Credentials.getClient(this, options).getHintPickerIntent(hintRequest)
startIntentSenderForResult(pendingIntent.intentSender, PHONE_REQUEST, null, 0, 0, 0)and OnActivityResult
override fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {
super.onActivityResult(requestCode, resultCode, data)
if (requestCode == PHONE_REQUEST) {
if (data != null) {
val credential: Credential? = data.getParcelableExtra(Credential.EXTRA_KEY)
val phoneNumber = credential?.id
// Some of our device fail to get phoneNumber here.
}
}
}
In this case, empty popup showed up and disappear quickly with weird animation.
And no value returned in onActivityResult callback.
Even if it fails, popup will not appear and developer should know before popup is showing.
If developer can know this will happen earlier, developer can do alternative way. For example, make user type their phone number manually.
This issue is not related with Android version. Brand new phone or old phone have same issue and might be related with SIM card.(I guess..)
I saw this bug on Samsung galaxy S7, S9.(one of S9 phone we have works fine but the other not)
Thanks!
From legal perspective it seems that a proper LICENSE file is missing for the sms-verification examples - would it be possible to add one, so that it is also clear that example code snippets can be used without limitations on other apps?
@ankitPagalGuy @ithinkihaveacat @keyboardsurfer Sms is not getting broadcasted , when i manually broadcast the intent from adb and its receiving in broadcast receiver. Sms is :
<#> Your Verification Code is 030787. This OTP will s. NKsG/pQa+dw
Need urgent help here.
when first time , I insert phone no and wait for SMS , it does not auto fill the OTP
here is log -
11-07 19:36:44.683 2143-2143/? I/SmsRetriever: [SmsRetrieverApiChimeraService] Prefix does not match 11-07 19:36:44.683 2143-2143/? I/SmsRetriever: [EndsWithStringMatcher] Found a match 11-07 19:36:44.683 2143-2143/? I/SmsRetriever: [SmsRetrieverApiChimeraService] No matching message is found
But if go back and again fill the phone no , it fills the OTP
here is log -
11-07 19:38:43.314 2143-2143/? I/SmsRetriever: [EndsWithStringMatcher] Found a match 11-07 19:38:43.314 2143-2143/? I/SmsRetriever: [SmsRetrieverApiChimeraService] Matched prefix:[#]
Have tried debugging but can't find anything
Make a buttons behind Dialog where you choose smart-lock saved identity (like: factory reset your phone, delete all photos, etc) and after click outside this dialog somewhere where you have some fatal button.
Diloag will dismiss, but button behind this dialog fill be forced to!!!!!!
It's useless.
Latest version of everything.
classpath 'com.android.tools.build:gradle:3.0.0-beta3'
classpath 'com.google.gms:google-services:3.1.0'
gradleVersion = '4.1'
// sdk and tools
compileSdkVersion = 26
buildToolsVersion = '26.0.1' // https://developer.android.com/studio/releases/build-tools.html
minSdkVersion = 16
targetSdkVersion = 26
// google dependencies versions
supportLibraryVersion = '26.0.2' // https://developer.android.com/topic/libraries/support-library/revisions.html
playServicesVersion = '11.2.0' // https://developers.google.com/android/guides/releases
Video with weird behaviour here: https://youtu.be/CpJyR-xm4_M
Is it possible to share saved credentials with the second app? I have one app installed. User logins using email and password. Then when installing the second app I want to have access to this credentials
When I try to save the credentials for the first time, I have this message in the logcat:
E/Volley ( 1070): [250] BasicNetwork.performRequest: Unexpected response code 400 for https://www.googleapis.com/credentials/v1/credentials?alt=proto&header.playServicesVersion=7571000&obfuscationKey=44838BE022CB8E787432945F2B755C422766B72D16B5DDB5CBD56C525143C8AE
E/CredentialsApi( 1309): Error when saving credential.
E/CredentialsApi( 1309): com.google.android.gms.auth.api.credentials.a: java.io.IOException: Server error.
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.d.a(SourceFile:329)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.b.e.a(SourceFile:181)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.b.e.a(SourceFile:33)
E/CredentialsApi( 1309): at com.google.android.gms.common.service.g.run(SourceFile:178)
E/CredentialsApi( 1309): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E/CredentialsApi( 1309): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E/CredentialsApi( 1309): at java.lang.Thread.run(Thread.java:818)
E/CredentialsApi( 1309): Caused by: java.io.IOException: Server error.
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.c.d.a(SourceFile:124)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.s.a(SourceFile:95)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.d.a(SourceFile:279)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.d.a(SourceFile:92)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.z.onTransact(SourceFile:135)
E/CredentialsApi( 1309): at android.os.Binder.execTransact(Binder.java:446)
E/CredentialsApi( 1309): Caused by: com.google.android.gms.auth.api.credentials.be.a.c
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.a.b.a(SourceFile:469)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.a.b.a(SourceFile:156)
E/CredentialsApi( 1309): at com.google.android.gms.auth.api.credentials.be.c.d.a(SourceFile:117)
E/CredentialsApi( 1309): ... 5 more
I don't think the error is on the client-side, but the Intent in the onActivityResult is empty.
Steps to reproduce
Result
In the form you will see(label with email field), that you are still signOut.
Expected result
You will be signedIn(correct email is shown).
Addition
If after this steps you will fold/unfold application one more time you will be signedIn.
As expected.
I investigated a little bit, and looks like we are not receiving onActivityResult after first fold/unfold, but receive after second, which is super strange.
In some mobiles after choosing the number from popup app minimizes and i could not track what actually causes it, since the app doesn't crash it minimizes/closed. Help me to figure out the issue. The device that causes the problems are infocus and few other devices. Note: i m checking for google play services updated and request for phone number hint(using hint request from sms-verification sample).
I have used various methods mentioned to generated hash code. I have tried them all. Problem is each method generated different hash.
I have tried them on both the debug.keystore and release keystore.jks
here is stackoverflow question for the same
I have tried following method:
Here are those various methods:
I tested my implementation on the above device. It successfully starts the retriever, but I never receive any broadcast in the onReceive even after I receive the SMS.
I tried apps like Uber, etc that are using this feature on the same phone, none worked.
However, on other devices, my implementation worked as expected. On these other phones, the version of google play services is 12685025.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.