Status Update
Comments
ex...@gmail.com <ex...@gmail.com> #2
Branch: androidx-main
commit 25369f983e26d758a8a027c84b21f20026637181
Author: Chris Craik <ccraik@google.com>
Date: Mon Jul 12 14:05:36 2021
Update JankCollectionHelper to support S gfxinfo
Fixes: 193260119
Relnote: Fixes FrameTimingMetric to work on Android S beta
Test: ./gradlew bench:integration-tests:macrobenchmark:connectedAndroidTest -P android.testInstrumentationRunnerArguments.class=androidx.benchmark.integration.macrobenchmark.TrivialListScrollBenchmark # On R + S
Still manually cherry-picking changes, as the platform copy of the
file triggers many lint warnings in AndroidX build.
Change-Id: Ib60ccf09fb2fa09f128374140c3657015626dd2c
M benchmark/macro/src/main/java/androidx/benchmark/macro/JankCollectionHelper.java
M benchmark/macro/src/main/java/androidx/benchmark/macro/Metric.kt
gm...@gmail.com <gm...@gmail.com> #3
kc...@google.com <kc...@google.com> #4
gm...@gmail.com <gm...@gmail.com> #5
They both have the same issue with setDeviceCredentialAllowed(true) (see #1).
Bug reports:
On attached screenshots you can see "onAuthenticationError" toast alongside device pattern UI.
gm...@gmail.com <gm...@gmail.com> #6
1. The issue applies to any non-biometric unlock method (pattern, PIN, or password), if fingerprint is configured too. Not sure about face recognition.
2. "onAuthenticationSucceeded" is not called after providing correct pattern/PIN/password.
ex...@gmail.com <ex...@gmail.com> #7
gm...@gmail.com <gm...@gmail.com> #8
ex...@gmail.com <ex...@gmail.com> #9
jo...@gmail.com <jo...@gmail.com> #10
na...@gmail.com <na...@gmail.com> #11
I have attached video to show bug with bio-metric prompt.
BP is not removed when user does home button swipe while setDeviceCredentialAllowed() is set true.
ex...@gmail.com <ex...@gmail.com> #12
ex...@gmail.com <ex...@gmail.com> #13
an...@atlassian.com <an...@atlassian.com> #14
an...@gmail.com <an...@gmail.com> #15
du...@google.com <du...@google.com>
gm...@gmail.com <gm...@gmail.com> #16
el...@gmail.com <el...@gmail.com> #17
kc...@google.com <kc...@google.com> #18
gmkropotkin@, I just requested access to the bugreports
ry...@gmail.com <ry...@gmail.com> #19
gm...@gmail.com <gm...@gmail.com> #20
no...@gmail.com <no...@gmail.com> #21
As I known, can't receive result event of device credential after the not intended cancel event.
Any workaround at application level ?
gm...@gmail.com <gm...@gmail.com> #22
Hello guys! Why is this issue still assigned to me? I've already shared all the info I have.
[Deleted User] <[Deleted User]> #23
[Deleted User] <[Deleted User]> #24
kc...@google.com <kc...@google.com> #25
Is this readily reproducible on actual physical devices (e.g. pixel, galaxy, etc), and if so, can someone attach a bugreport?
[Deleted User] <[Deleted User]> #26
th...@googlemail.com <th...@googlemail.com> #27
cu...@google.com <cu...@google.com>
da...@gmail.com <da...@gmail.com> #28
ma...@asaas.com.br <ma...@asaas.com.br> #29
se...@gratisbroker.de <se...@gratisbroker.de> #30
ir...@gmail.com <ir...@gmail.com> #31
ma...@gmail.com <ma...@gmail.com> #33
jo...@motorolasolutions.com <jo...@motorolasolutions.com> #34
Can we get an update on this? Is there a workaround? Documentation suggests this combination should work.
pi...@gmail.com <pi...@gmail.com> #35
Just to add to this - we've seen this issue on the Samsung Galaxy A40 as well.
However it only happens sporadically meaning, that the user will be able to authenticate correctly after a few tries, but when opening our app usually the first time using the Device Credentials won't work and the user will just end up on our login screen. If they try a few times with Device Credentials they'll be able to login.
The user has biometrics enrolled, but chose to use the Device Credentials instead.
If I set the allowed authenticators to DEVICE_CREDENTIALS only the user will be able to login immediately, but the combination of BIOMETRIC_WEAK and DEVICE_CREDENTIALS will create this weird behaviour.
Also if I set the allowed authenticators to DEVICE_CREDENTIALS only then when I call BiometricManager.canAuthenticate(Authenticators.DEVICE_CREDENTIAL)
it returns BIOMETRIC_ERROR_UNSUPPORTED
and so I end up using the old KeyguardManager
to create a Device Credentials Activity.
This is truly a mess of proportions with all these weird bugs depending on what version of Android and what device you're running on.
I'm wondering why it seems that you won't just stop the new development on this project for just a while and look at all the bugs being reported and fix these bugs before you move on to new things, like Kotlin Extensions etc. I feel like you're just making a mockery of the community by just keep on adding new features instead of fixing whatever bugs comes up. :-(
ps...@gmail.com <ps...@gmail.com> #36
ps...@gmail.com <ps...@gmail.com> #37
ps...@gmail.com <ps...@gmail.com> #38
Google NAMESPACE:Patrick Rene Guerrero
ERRATA-ID:RFC2119
NAME:ALBUQUERQUE-RDP-V6-1
HANDLE:ICI 61-ARIN
Copyright License(2021) and Official Patent Holder, Patrick Rene Guerrero,.
Bug Bounty Hunter and Fiscal EARNINGS and ALL PROCEEDS MUST GO TO THE PROPER IDENTITY , IDENTIFIED as
ps...@gmail.com <ps...@gmail.com> #39
ORGANIZATION: JCS Enterprises LLC
NAME: Patrick Rene Guerrero
STATUS:VALIDATED
NETWORK:ALBUQUERQUE-RDP-V6-1
Charter: IPNGP
OBSOLETES:RFC2119
Email:
ps...@gmail.com <ps...@gmail.com> #40
ORGANIZATION: JCS Enterprises LLC
NAME: Patrick Rene Guerrero
STATUS:VALIDATED
NETWORK:ALBUQUERQUE-RDP-V6-1
Charter: IPNGP
OBSOLETES:RFC2119
Email:
ys...@gmail.com <ys...@gmail.com> #41
Do you have any news about this issue? We receive many similar open points in our side. Do you plan to release a fix?
Thank you,
ps...@gmail.com <ps...@gmail.com> #42
cu...@google.com <cu...@google.com> #43
Version 1.2.0-alpha04 (releasing today) has a workaround that should fix this for most, if not all, devices.
kc...@google.com <kc...@google.com>
an...@gmail.com <an...@gmail.com> #44
me...@gmail.com <me...@gmail.com> #45
1.2.0-alpha04 doesn't fix anything on a Samsung S6, running OS on API 26. Doesn't matter if fingerprints are enrolled.
Calling this:
prompt = new BiometricPrompt.PromptInfo.Builder()
.setTitle(title)
.setAllowedAuthenticators(BiometricManager.Authenticators.DEVICE_CREDENTIAL)
.build();
Results in this, when the authentication screen is supposed to come:
java.lang.IllegalArgumentException: Authenticator combination is unsupported on API 26: DEVICE_CREDENTIAL
at androidx.biometric.BiometricPrompt$PromptInfo$Builder.build(BiometricPrompt.java:579)
at ccom.example.app.util.bioPinAuthentication.authenticate(auth.java:76)
at ccom.example.app.MainActivity.authBio(MainActivity.java:346)
at ccom.example.app.MainActivity.onResume(MainActivity.java:479)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1361)
at android.app.Activity.performResume(Activity.java:7415)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3765)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3830)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3038)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
What I want to do is use PIN only, but it only works when this is called and no fingerprints are enrolled on the device:
prompt = new BiometricPrompt.PromptInfo.Builder()
.setTitle(title)
.setAllowedAuthenticators(BiometricManager.Authenticators.BIOMETRIC_STRONG | BiometricManager.Authenticators.BIOMETRIC_WEAK | BiometricManager.Authenticators.DEVICE_CREDENTIAL)
.build();
Don't know if this is a completely unrelated issue from all above.
an...@gmail.com <an...@gmail.com> #46
In reply to last comment: To use (PIN||pattern||password||biometric if enrolled), forget about this biometric API and use the legacy
em...@gmail.com <em...@gmail.com> #47
st...@gmail.com <st...@gmail.com> #48
Tried the solution of #46, but createConfirmDeviceCredentialIntent() also always returns Canceled.
Description
BUILD INFO
- Device type: Emulator x86_64
- OS version: Android Q
- Biometric library version: 1.0.0-rc1
STEPS TO REPRODUCE
1. Run emulator
2. Set Fingerprint+pattern
3. Run project
4. Tap button
5. Tap 'Use pattern'
EXPECTED RESULTS
Authentication canceled error hasn't been thrown.
OBSERVED RESULTS
Authentication canceled error has been thrown.
NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE
Always
I used Basic activity Android Studio template with the next code:
package com.myapplication
import android.annotation.SuppressLint
import android.os.Bundle
import android.util.Log
import androidx.appcompat.app.AppCompatActivity
import androidx.biometric.BiometricPrompt
import androidx.biometric.BiometricPrompt.AuthenticationCallback
import kotlinx.android.synthetic.main.activity_main.*
class MainActivity : AppCompatActivity() {
@SuppressLint("NewApi")
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
setSupportActionBar(toolbar)
fab.setOnClickListener { view ->
val promptInfo = BiometricPrompt.PromptInfo.Builder()
.setTitle("test")
.setDeviceCredentialAllowed(true)
.build();
val prompt = BiometricPrompt(this, this.mainExecutor, object : AuthenticationCallback() {
override fun onAuthenticationError(errorCode: Int, errString: CharSequence) {
Log.e("Authentication", "Cancel");
super.onAuthenticationError(errorCode, errString)
}
})
prompt.authenticate(promptInfo);
}
}
}