Velocity Tracker has Issue [223440806]

Fixed

Bug

Status Update

No update yet.

Description

al...@gmail.com

created issue #1

Mar 9, 2022 07:50AM

Velocity Tracker in compose has an issue.
When I scroll on a composable and concurrently change offset of that composable by scroll delta ,every point that add to Velocity Tracker approximately has same offset , so velocity calculate incorrect.
The issue can be solved if drag amount be used instead of offset of pointer.
When layout is fixed it work well but when layout move by changing offset or translation this issue will be happen.

Comments

so...@google.com <so...@google.com> Mar 10, 2022 05:53PM

Assigned to je...@google.com.

ni...@google.com <ni...@google.com> Mar 16, 2022 03:26PM

Reassigned to co...@google.com.

le...@google.com <le...@google.com> Apr 11, 2022 11:15AM

Reassigned to le...@google.com.

le...@google.com <le...@google.com> #2Apr 12, 2022 02:06PM

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

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

al...@gmail.com <al...@gmail.com> #3Apr 13, 2022 12:01PM

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?

le...@google.com <le...@google.com> #4Apr 20, 2022 05:16PM

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

ap...@google.com <ap...@google.com> #5May 19, 2022 03:44PM

deleted

le...@google.com <le...@google.com> May 19, 2022 03:47PM

Marked as fixed.

le...@google.com <le...@google.com> May 29, 2022 10:42AM

Status: Assigned (reopened)

ap...@google.com <ap...@google.com> #6Jun 8, 2022 09:03AM

Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.

ap...@google.com <ap...@google.com> #7Jun 28, 2022 07:29PM

Hello, I am trying to implement the same thing - it seems like there's no way for current password managers like 1Password or Bitwarden, to automatically pick up the fields. Is there a possible solution?

le...@google.com <le...@google.com> Jun 28, 2022 07:30PM