Issues with autofill popup/tag in apps providing its own keyboard

[godfuture]

Checklist

• I am able to reproduce the bug with the latest version here.
• I have checked and there are no existing issues - open or closed - which report the same bug.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.

Affected version

1.0.10

Steps to reproduce the bug

1. Install app implementing its own keyboard for passwort entry (e.g. banking app: https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan)
2. Open the described app in point 1.
3. Try to enter password and check for autofill popup or tag

Expected behavior

When using https://f-droid.org/de/packages/de.jbservices.nc_passwords_app as standard autofill service, then the popup appears. So still there seems an issue with password field detection that works with other apps.

Actual behavior

My TAN banking app is providing its own keyboard when started. If Nextcloud Passwords is used as autofill service, my banking app is not showing "password autofill overlay or popup dialog".

Screenshots/Screen recordings

No response

Affected Android/Custom ROM version

LineageOS 21

Affected device model

Fairphone 3+

Additional information

No response

[hegocre]

Hello, and thank you for your feedback.

Could you please check if disabling inline autofill fixes the problem?

Thanks!

[godfuture]

Hello, and thank you for your feedback.

Could you please check if disabling inline autofill fixes the problem?

Thanks!

Yes, indeed now it works. Is there a bug with inline autofill?

[hegocre]

The thing is, inline autofill needs a compatible keyboard to display the suggestions. Since there is a compatible keyboard enabled, inline autofill is supported. However, when the keyboard is not visible, it sometimes fails to report it, which means the autofill service does not know it needs to show the popup autofill suggestions.

If I recall correctly, the autofill of the app you mentioned does not support inline autofill, which means it does not have this problem.

I will try to detect if it is actually showing, but I don't know if that is possible. I will report back.

Thank you!