Fixed
Status Update
Comments
so...@google.com <so...@google.com>
ra...@google.com <ra...@google.com> #2
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
ch...@gmail.com <ch...@gmail.com> #3
I found an example
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?
ma...@google.com <ma...@google.com> #5
deleted
ap...@google.com <ap...@google.com> #6
Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.
ra...@google.com <ra...@google.com>
da...@well.co <da...@well.co> #7
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?
Description
Jetpack Compose version: 1.8.0-beta01
Jetpack Compose component used: androidx.compose.ui:ui-tooling
Android Studio Build: #AI-242.23339.11.2421.12700392
Kotlin version: 2.0.20
When you try to use the new autofill semantics functionality on a textfield with a
visualTransformation
the password manager will store asterisks as the password instead of the actual value, e.g********
instead ofpassword
, rendering the feature useless. If I remove the visual transformation everything works as intended.Steps to Reproduce or Code Sample to Reproduce: