Autofill Framework functionality is castrated on Android Emulator when using in Chrome browser

[vaidotasstrazdas]

I am using Android Emulator, so maybe this can be the reason of such behavior.

Autofill service being used: Basic Heuristic Autofill Service Emulator being used: Nexus 6P API 28 (Android 9, API 28)

Steps to reproduce:

1. Open Google Chrome in emulator.
2. Click on URL bar -> BasicService::onFillRequest is triggered. This is OK.
3. Go to any website (e.g. instagram.com).
4. Click login.
5. Focus in some field (e.g. email or password) -> BasicService::onFillRequest is NOT triggered. This is NOT OK.

Expected result:

1. By clicking on URL bar, BasicService::onFillRequest is triggered. This is already the case, so it's ok.
2. By clicking on any website field, BasicService::onFillRequest is triggered. This is not the case, so the behavior is wrong in this case.

What can be the reason of such behavior? Am I missing something or is it a bug of Android Autofill Framework? If it is a bug, then is there some workaround that I can use to make Autofill Framework to work properly? Maybe different emulator would work? If so, then which emulator should I use to test this feature properly?

[the-felipeal]

Chrome does not support the Autofill API. On Android P, the autofill service could work around it by using Compatibility Mode (https://developer.android.com/preview/features/autofill#compat-mode), but you must whitelist the apps that can use it in the device first, so my guess is that your emulator image is not doing that.

Can you attach the output of adb shell dumpsys autofill?