[Bug]: Contents can't be autofilled (Google password manager) #1282

New Issue

2026-04-24T23:56:32+02:00

adam commented

2026-04-24 23:56:32 +02:00

Originally created by @kuci-JK on GitHub (Sep 29, 2025).

I have verified that the bug is not already awaiting release

Yes

What was the Problem?

Sometimes on bad connection during app startup the app needs to relogin...

On the login page the password manager prompts (I am using google password manager) do not show up - even when clicking on autofill in the context menu which usually helps to trigger it. Instead it shows a toast message with this text: Contents can't be autofilled.

Since i don't remember my password i have to go look for it in the password manager app, if this autofill option would work, it would be faster to get back in the app again.

Steps to Reproduce the Issue

Prerequisites:

Have your Googles password manager turned on

Steps:

Go to the login page
Fill in the url and username (it should autofill here too, but that is the same)
Click to password input -> no prompt from google
long press in the input and select autofill
see the toast message

Screenshots:

What was Expected?

I have expected the google password manager autofill options to show up (they usually show in a form of a bottom sheet or in the top row in the keyboard - replacing the suggestions). See example screenshot from AntennaPod (in settings -> synchronization)

Phone Model

Redmi Note 11

Phone OS

Android 13 TKQ1.221114.001 (Xiaomi HyperOS 1.0.1.0. TGKEUXM)

Audiobookshelf App Version

Android App - 0.10.1

Installation Source

Google Play Store

Additional Notes

I am currently quite busy, but if needed I can try to test it in an emulator...
If i can provide some logs to help diagnose the issue, please let me know.
I only have this issue in the android app (in the web browser the autofill works well).
If this was never supported, you can treat this issue as an enhancement suggestion.

Originally created by @kuci-JK on GitHub (Sep 29, 2025). ### I have verified that the [bug is not already awaiting release](https://github.com/advplyr/audiobookshelf-app/issues?q=is%3Aissue%20label%3A%22awaiting%20release%22) Yes ### What was the Problem? Sometimes on bad connection during app startup the app needs to relogin... On the login page the password manager prompts (I am using google password manager) do not show up - even when clicking on autofill in the context menu which usually helps to trigger it. Instead it shows a toast message with this text: Contents can't be autofilled. Since i don't remember my password i have to go look for it in the password manager app, if this autofill option would work, it would be faster to get back in the app again. ### Steps to Reproduce the Issue Prerequisites: - Have your Googles password manager turned on Steps: 1. Go to the login page 2. Fill in the url and username (it should autofill here too, but that is the same) 3. Click to password input -> no prompt from google 4. long press in the input and select autofill 5. see the toast message Screenshots: ![Image](https://github.com/user-attachments/assets/e538c0e8-3b54-4ed6-b2d7-5e5c20303b22) ![Image](https://github.com/user-attachments/assets/198c5e4c-9c95-4c41-8de4-57838377d8e8) ### What was Expected? I have expected the google password manager autofill options to show up (they usually show in a form of a bottom sheet or in the top row in the keyboard - replacing the suggestions). See example screenshot from AntennaPod (in settings -> synchronization) ![Image](https://github.com/user-attachments/assets/3e562c0f-2641-41fd-bdb2-4fd593498e4f) ### Phone Model Redmi Note 11 ### Phone OS Android 13 TKQ1.221114.001 (Xiaomi HyperOS 1.0.1.0. TGKEUXM) ### Audiobookshelf App Version Android App - 0.10.1 ### Installation Source Google Play Store ### Additional Notes - I am currently quite busy, but if needed I can try to test it in an emulator... - If i can provide some logs to help diagnose the issue, please let me know. - I only have this issue in the android app (in the web browser the autofill works well). - If this was never supported, you can treat this issue as an enhancement suggestion.

adam added the bug label 2026-04-24 23:56:32 +02:00

adam commented

2026-04-24 23:56:33 +02:00