Verified
Status Update
Comments
cc...@google.com <cc...@google.com> #2
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
cc...@google.com <cc...@google.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?
cc...@google.com <cc...@google.com>
ap...@google.com <ap...@google.com> #4
pr...@google.com <pr...@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.
Description
Component used: androidx.baselineprofile, androidx.benchmark:benchmark-macro-junit4
Version used: 1.2.0-rc01
Devices/Android versions reproduced on: Pixel 7 Android 34 Emulator
Android Studio Iguana | 2023.2.1 Canary 6
Build #AI-232.9921.47.2321.10875067, built on September 28, 2023
Runtime version: 17.0.8+0-17.0.8b1000.22-10799086 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
There seems to be a regression between beta05 and rc01 of the baselineProfile plugin.
saveInSrc = true
works correctly in beta05, but doesn't pull the profile from device to the host and save it when using rc01.rc1 produces the following logcat which seems to output the end of the test twice, is this the issue?
Baseline Test is simple:
Also seeing a lot of time out warnings around the fling(Direction.Down) call. Can log another issue for that if needed.