detectTapGestures flakes and hangs in the down state on the emulator with mouse input [179239764]

Fixed

Bug

Status Update

No update yet.

Description

ma...@google.com

created issue #1

Feb 3, 2021 11:55AM

What title says, we had to revert clickable to tapGestureFilters and other filters instead of using detectTapGestures because click wasn't fired sometimes under certain circumstances. More context:

After we migrated clickable to detectTapGestures, we were missing clicks on the buttons.

Symptoms: tap with regular speed, after click is up (lifted) sometimes ripple animates to pressed state and stays there and onClick is not fired. Reproducible not on every click and not for everyone.

Notable discoveries throughout exploration/revert:

It was reproducible only on emulators. All attempts to repro this on the
It was flaky, meaning that not everyone was able to reproduce it. 2.1 We were able to reproduce it on some linux machines that operates with mouse 2.2 We were able to reproduce it on the macs when you TAP on the trackpad. Not reproducible when you click.
Revert to tapGestureFilter fully solves the issue.

Seems like a timing/race issue when delay between down and up is very low, or smth along this lines.

It's an important issue to allow us to continue to migrate production code to suspend pointer to solve, hence p1.

Comments

ap...@google.com <ap...@google.com> #2Mar 24, 2021 11:13AM

Marked as fixed.

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

ap...@google.com <ap...@google.com> #3Aug 19, 2021 02:40AM

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

Issue 179239764

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Mar 24, 2021 11:13AM

ap...@google.com <ap...@google.com> #3Aug 19, 2021 02:40AM

Add comment

Issue metadata