Can't authenticate with device credential on API 29 emulator [142740104]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ex...@gmail.com

created issue #1

Oct 15, 2019 08:51PM

BiometricPrompt always throws Authentication canceled error with setDeviceCredentialAllowed(true) in Android Q.

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);
}
}
}

Comments

ex...@gmail.com <ex...@gmail.com> #2Oct 16, 2019 08:41AM

Please include a sample project that reproduces your issue.

gm...@gmail.com <gm...@gmail.com> #3Oct 26, 2019 05:41PM

Here is the sample project.

Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;

With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.

Please suggest some workarounds or how to fix this issue?

kc...@google.com <kc...@google.com> #4Dec 6, 2019 10:07PM

Reassigned to ex...@gmail.com.

Hello, have you checked sample project? I hope it will help find the issue.

gm...@gmail.com <gm...@gmail.com> #5Dec 7, 2019 11:42AM

@3
I've described a weird workaround that I got, here:

https://issuetracker.google.com/issues/244854449#comment3
Sample:

https://issuetracker.google.com/issues/244854449#comment4

It probably has bugs of its own that I didn't think of.
Google please fix this.

TestBiometricQ.zip

138 KB

Download

TestBiometricX.zip

138 KB

Download

biometric_q_screen.png

32 KB

View

Download

biometric_x_screen.png

31 KB

View

Download

gm...@gmail.com <gm...@gmail.com> #6Dec 7, 2019 11:58AM

Hello, any update please?

ex...@gmail.com <ex...@gmail.com> #7Dec 8, 2019 09:12AM

Hello I raised similar issue with this ticket https://issuetracker.google.com/issues/249247706

This makes the SearchView unusable/broken when fragments are changed (i.e base on searchView input query)

What can we do to fix this problem? What is the progress of work on solving this problem?

gm...@gmail.com <gm...@gmail.com> #8Dec 8, 2019 02:45PM

@7 Check @5 for a workaround.

ex...@gmail.com <ex...@gmail.com> #9Dec 8, 2019 02:51PM

Hi, i am also facing this issue after we dismiss a DialogFragment, the callback comes in the onPrepareOptionsMenu(), which is causing the issues for me.
Any idea on when it will be fixed?

jo...@gmail.com <jo...@gmail.com> #10Dec 9, 2019 04:00PM

Hello, any estimate please?

na...@gmail.com <na...@gmail.com> #11Dec 11, 2019 09:15AM

Facing a similar kind of issue when scrolling the fragments using a ViewPager.

https://issuetracker.google.com/issues/267677504

Can you update regarding any progress on this issue.

BiometricPromptBug.mp4

3.4 MB

Download

ex...@gmail.com <ex...@gmail.com> #12Dec 15, 2019 11:30AM

I wonder if the new SearchBar has this issue:

https://material.io/blog/android-stable-release-1-8-0

ex...@gmail.com <ex...@gmail.com> #13Dec 15, 2019 11:31AM

Project: platform/frameworks/support
Branch: androidx-main

commit 50f098644adc703ae218b0b7e999629f516a0241
Author: sanura <sanura@google.com>
Date: Thu Mar 02 00:11:35 2023

Add check to only invalidate options menu when contributing menu items

FragmentManager previously appropriately only added
a MenuProvider when the host is a MenuHost **and**
we are at the root fragment that is providing the
menu items. This behavior should be mirrored when
removing a MenuProvider as well, so that only
components that directly contribute menu items will
invalidate the options menu.

Bug: 244336571
Test: all tests pass
Change-Id: I9404ee9fcc9ce6b80d70a93bea720fe4ccf583a0

M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentContainerInflatedFragmentTest.kt
M fragment/fragment/src/androidTest/java/androidx/fragment/app/OptionsMenuFragmentTest.kt
M fragment/fragment/src/androidTest/java/androidx/fragment/app/test/FragmentTestActivity.kt
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentActivity.java
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java

https://android-review.googlesource.com/2465169

an...@atlassian.com <an...@atlassian.com> #14Dec 27, 2019 01:16AM

@13 Fixed when? On which version of which dependency?
Please show what to write on gradle file.

an...@gmail.com <an...@gmail.com> #15Dec 30, 2019 01:21PM

This has been fixed internally and will be available in the Fragment 1.6.0-alpha07 release.

du...@google.com <du...@google.com> Jan 9, 2020 01:32AM

Reassigned to kc...@google.com.

gm...@gmail.com <gm...@gmail.com> #16Jan 11, 2020 05:47PM

@15 I've noticed I can avoid using the fragment dependency and still work fine with fragments. How come?
It's part of the material dependency, perhaps?

el...@gmail.com <el...@gmail.com> #17Jan 14, 2020 01:33PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.fragment:fragment:1.6.0-alpha07

kc...@google.com <kc...@google.com> #18Jan 28, 2020 09:50PM

Reassigned to gm...@gmail.com.

@17 What if I don't use this dependency (probably imported automatically by material dependency) ? Use it, still?

ry...@gmail.com <ry...@gmail.com> #19Jan 28, 2020 11:20PM

@17 I wanted to try what you wrote on the sample I've provided (after I remove my workaround), and for some reason it doesn't let me.
It says "Duplicate class found".
The IDE doesn't provide any useful explanation of what is the class that is duplicated and what to do about it.
Please help.

gm...@gmail.com <gm...@gmail.com> #20Feb 22, 2020 09:49PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.fragment:fragment:1.5.6

no...@gmail.com <no...@gmail.com> #21Mar 20, 2020 10:58AM

@20 Not 1.6.0-alpha07 ?

gm...@gmail.com <gm...@gmail.com> #22Apr 21, 2020 08:03AM

@21 androidx.fragment:fragment:1.5.6 is a STABLE release. It has the fix we need. The androidx.fragment:fragment:1.6.0-alpha07 is an alpha as it says. 1.6 is "work in progress". 1.6.0 is still not a stable release. Use "alpha" only for testing

[Deleted User] <[Deleted User]> #23Apr 21, 2020 01:28PM

@22 So it's fixed on both. OK

[Deleted User] <[Deleted User]> #24Apr 21, 2020 01:33PM

This is definitely a bug. You can't get the correct callback from the API. When the user taps the "use PIN" button the cancelled callback is fired. After entering your pin no other callback is called.

kc...@google.com <kc...@google.com> #25Apr 29, 2020 05:58PM

Reassigned to an...@google.com.

I went through the bugreports in #5 and they are taken from the emulator, which sometimes behaves differently due to hardware/hal-specific differences.

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]> #26Apr 29, 2020 08:51PM

I'm seeing this in my emulator too, the success callback never returns. But on my Pixel 3, it works. So I think something is wrong in the emulator layer.

th...@googlemail.com <th...@googlemail.com> #27Sep 11, 2020 06:49AM

I see this issue in my emulator and my physical Samsung S7

cu...@google.com <cu...@google.com> Sep 23, 2020 05:30PM

Accepted by cu...@google.com.

da...@gmail.com <da...@gmail.com> #28Sep 24, 2020 11:51AM

Hi, is there any workaround for devices with sdk < 30 ?

ma...@asaas.com.br <ma...@asaas.com.br> #29Oct 20, 2020 08:44PM

For sdk < 30 use keyguardManager it works.

se...@gratisbroker.de <se...@gratisbroker.de> #30Dec 17, 2020 09:20PM

I see this sporadically occurring on a Samsung A20e as well.

ir...@gmail.com <ir...@gmail.com> #31Dec 30, 2020 08:52AM

It's not only happening on the emulator, the real device occurred too. I reproduce the exact bug on Redmi Note 8 that runs on Android 10. The library I'm using is 1.1.0-rc01, and it's pretty new. Why is this happening? Is it not fixed yet? Or is there's some workaround to tackle this for now? I had read some post that mentioned it's fixed in the newer version, of course, it's false information since I still get the bug.

ca...@gmail.com <ca...@gmail.com> #32Mar 12, 2021 04:58AM

Mmmm, this is not currently deprecated?

https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt.Builder#setDeviceCredentialAllowed(boolean)

ma...@gmail.com <ma...@gmail.com> #33Apr 8, 2021 09:39AM

Any updates how to fix this?

jo...@motorolasolutions.com <jo...@motorolasolutions.com> #34Apr 8, 2021 03:02PM

Even though `setDeviceCredentialAllowed(boolean)` is deprecated, this still happens with `setAllowedAuthenticators(BIOMETRIC_WEAK | DEVICE_CREDENTIAL)`. The issue does not happen when using biometric or device credential alone, only together.

Can we get an update on this? Is there a workaround? Documentation suggests this combination should work.

pi...@gmail.com <pi...@gmail.com> #35Apr 22, 2021 11:36AM

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> #36Sep 25, 2021 01:09PM

https://doc-0hm0-30t0-issuetracker.googleusercontent.com/attachments/0dlerg5f9ko8hpq98s9r91i1ifdul4al/02mugpkhtcammaq7f6sqgos6hmoalu42/1632574800000/931982/110794961014779769937/186921855::34871964::931982?dat=AFNnbnnzImQB0PR99dDiYtLyrysLh_2Pc9fGiRJIUc2kId28C6hF-vt1gaa-maICsvIeIEgbMJw3_afocx40ah_u0YSpVJSvYCA39ng2F45BdmS-4HxydRYcovdP8c8LtnBFVi2hqopNjJ2rpNL83SJcdlr3ilAQLjSX1aF9hnmZnkvki57uOsBt_v6vNyJYbEqEzVp92I9xbo0nsQbCh2NUqYQ5Uv0ij6_S2kfHXGQyBvQ--0fde5CN9i__r9PvGJqZXab1tpGwlvD0UoeVbadq32Oq_8PSAWHjmW1jS-iUdurq9MG7l-9N-DwrEwB6wp2gmwJEg8w-VuoMLvWz3tciZPJWIIkHduEiL29Y9w857_icGdHX0fmzq6kzoVnerbPHrdfy9WFb1U6bfjbIUwa88z_9q5VGzRUrdV8y5hqook_5_TXsdd3ZFjiLbpyNwiGBIRX8ui_o3FQ5gBfDd2ULn6tMEwRzqRFExVjed_YqQ2r4JMAUh40DkiQxmDu2JFwVYcNGDrn9aC-XfbKgqt63LyuR_CUEYC5plUIJxjELEfkiGS7557K3iaGeE_9OirGiat5s82mO69ncfSmwsfHrmDGeXwdh4l0ygU3GlypCMR1wwGhqg7S8uULnyIE0Z2Lm2pNpO8KbAQiF1I5tOUAaXbNaBgn_VDkVYxYMBCtDAEufZPNMmfkyX51MTjEEFoCKQo49E-r1trxwvDHYZuYYz03SFeNRGjlc3p5r1EdVWbcOWNAzY7Q9jKW_M5uLeMqYulipmHBu&u=0&s=1&download=false&nonce=phg0hnm78gsfo&user=110794961014779769937&hash=r2qnmm8a8r4d6me8h0i3bqrrkub9rhat

ps...@gmail.com <ps...@gmail.com> #37Sep 25, 2021 01:11PM

https://drive.google.com/file/d/1nvVrUhSuqq56LA-LnQ08R4YhxwzaiNUW/view?usp=drive_web (255b8f6.diff.base64)

https://drive.google.com/file/d/1-1_Eyii9_deiUA2H1sIrDvgpv8Luiq0M/view?usp=drive_web (JCS-Enterprises-LLC-PRG.json)

https://drive.google.com/file/d/1K7fYDI_g_WcrCo38Cft-uSBuHACEMIQ0/view?usp=drive_web (_ ISO - Quote (EN) - OP-549881.pdf)

ps...@gmail.com <ps...@gmail.com> #38Sep 25, 2021 01:27PM

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 Pstackzz3c@gmail.com(Patrick Rene Guerrero)

ps...@gmail.com <ps...@gmail.com> #39Sep 25, 2021 01:32PM

ORGANIZATION: JCS Enterprises LLC NAME: Patrick Rene Guerrero STATUS:VALIDATED NETWORK:ALBUQUERQUE-RDP-V6-1 Charter: IPNGP OBSOLETES:RFC2119 Email: pstackzz3c@gmail.com Tel: +1(505)317-8801

ps...@gmail.com <ps...@gmail.com> #40Sep 25, 2021 01:33PM

ORGANIZATION: JCS Enterprises LLC NAME: Patrick Rene Guerrero STATUS:VALIDATED NETWORK:ALBUQUERQUE-RDP-V6-1 Charter: IPNGP OBSOLETES:RFC2119 Email: pstackzz3c@gmail.com Tel: +1(505)317-8801

ys...@gmail.com <ys...@gmail.com> #41Oct 4, 2021 01:12PM

Hello,
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> #42Oct 9, 2021 09:46AM

https://issuetracker.google.com/142740104

cu...@google.com <cu...@google.com> #43Nov 17, 2021 05:39PM

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> Nov 17, 2021 06:29PM

Marked as fixed.

an...@gmail.com <an...@gmail.com> #44May 26, 2022 08:07PM

This issue was reported 3 years ago, fixed 6 months ago, and no stable release is published yet. Any ideas what is delaying the stable release? We need this bugfix applied to a stable for yesterday.

Message last modified on May 26, 2022 10:24PM

me...@gmail.com <me...@gmail.com> #45May 29, 2022 07:18PM

Having the opposite issue of #35.

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> #46May 30, 2022 09:48PM

In reply to last comment: To use (PIN||pattern||password||biometric if enrolled), forget about this biometric API and use the legacy createConfirmDeviceCredentialIntent. I've tested it in Android 10 and works exactly as the biometrics API should, but bugs-free.

em...@gmail.com <em...@gmail.com> #47Jul 10, 2022 06:44PM

in your onAuthenticationError, add something like if (++attempts == 1 && errorCode == 5) biometricPrompt.authenticate(...). it flashes, but it works

st...@gmail.com <st...@gmail.com> #48Jul 13, 2022 03:46PM

Having the opposite of issue #35, on physical Android 10.
Tried the solution of #46, but createConfirmDeviceCredentialIntent() also always returns Canceled.

Issue 142740104

Description

Issue summary

Comments

ex...@gmail.com <ex...@gmail.com> #2Oct 16, 2019 08:41AM

gm...@gmail.com <gm...@gmail.com> #3Oct 26, 2019 05:41PM

kc...@google.com <kc...@google.com> #4Dec 6, 2019 10:07PM

gm...@gmail.com <gm...@gmail.com> #5Dec 7, 2019 11:42AM

gm...@gmail.com <gm...@gmail.com> #6Dec 7, 2019 11:58AM

ex...@gmail.com <ex...@gmail.com> #7Dec 8, 2019 09:12AM

gm...@gmail.com <gm...@gmail.com> #8Dec 8, 2019 02:45PM

ex...@gmail.com <ex...@gmail.com> #9Dec 8, 2019 02:51PM

jo...@gmail.com <jo...@gmail.com> #10Dec 9, 2019 04:00PM

na...@gmail.com <na...@gmail.com> #11Dec 11, 2019 09:15AM

ex...@gmail.com <ex...@gmail.com> #12Dec 15, 2019 11:30AM

ex...@gmail.com <ex...@gmail.com> #13Dec 15, 2019 11:31AM

an...@atlassian.com <an...@atlassian.com> #14Dec 27, 2019 01:16AM

an...@gmail.com <an...@gmail.com> #15Dec 30, 2019 01:21PM

du...@google.com <du...@google.com> Jan 9, 2020 01:32AM

gm...@gmail.com <gm...@gmail.com> #16Jan 11, 2020 05:47PM

el...@gmail.com <el...@gmail.com> #17Jan 14, 2020 01:33PM

kc...@google.com <kc...@google.com> #18Jan 28, 2020 09:50PM

ry...@gmail.com <ry...@gmail.com> #19Jan 28, 2020 11:20PM

gm...@gmail.com <gm...@gmail.com> #20Feb 22, 2020 09:49PM

no...@gmail.com <no...@gmail.com> #21Mar 20, 2020 10:58AM

gm...@gmail.com <gm...@gmail.com> #22Apr 21, 2020 08:03AM

[Deleted User] <[Deleted User]> #23Apr 21, 2020 01:28PM

[Deleted User] <[Deleted User]> #24Apr 21, 2020 01:33PM

kc...@google.com <kc...@google.com> #25Apr 29, 2020 05:58PM

[Deleted User] <[Deleted User]> #26Apr 29, 2020 08:51PM

th...@googlemail.com <th...@googlemail.com> #27Sep 11, 2020 06:49AM

cu...@google.com <cu...@google.com> Sep 23, 2020 05:30PM

da...@gmail.com <da...@gmail.com> #28Sep 24, 2020 11:51AM

ma...@asaas.com.br <ma...@asaas.com.br> #29Oct 20, 2020 08:44PM

se...@gratisbroker.de <se...@gratisbroker.de> #30Dec 17, 2020 09:20PM

ir...@gmail.com <ir...@gmail.com> #31Dec 30, 2020 08:52AM

ca...@gmail.com <ca...@gmail.com> #32Mar 12, 2021 04:58AM

ma...@gmail.com <ma...@gmail.com> #33Apr 8, 2021 09:39AM

jo...@motorolasolutions.com <jo...@motorolasolutions.com> #34Apr 8, 2021 03:02PM

pi...@gmail.com <pi...@gmail.com> #35Apr 22, 2021 11:36AM

ps...@gmail.com <ps...@gmail.com> #36Sep 25, 2021 01:09PM

ps...@gmail.com <ps...@gmail.com> #37Sep 25, 2021 01:11PM

ps...@gmail.com <ps...@gmail.com> #38Sep 25, 2021 01:27PM

ps...@gmail.com <ps...@gmail.com> #39Sep 25, 2021 01:32PM

ps...@gmail.com <ps...@gmail.com> #40Sep 25, 2021 01:33PM

ys...@gmail.com <ys...@gmail.com> #41Oct 4, 2021 01:12PM

ps...@gmail.com <ps...@gmail.com> #42Oct 9, 2021 09:46AM

cu...@google.com <cu...@google.com> #43Nov 17, 2021 05:39PM

kc...@google.com <kc...@google.com> Nov 17, 2021 06:29PM

an...@gmail.com <an...@gmail.com> #44May 26, 2022 08:07PM

me...@gmail.com <me...@gmail.com> #45May 29, 2022 07:18PM

an...@gmail.com <an...@gmail.com> #46May 30, 2022 09:48PM

em...@gmail.com <em...@gmail.com> #47Jul 10, 2022 06:44PM

st...@gmail.com <st...@gmail.com> #48Jul 13, 2022 03:46PM

Add comment

Issue metadata