Inline Autofill doesn't work on Galaxy S25
yurividal opened this issue · comments
Steps To Reproduce
Bitwarden's inline autofill doesn't work on Galaxy s25 devices, using the stock Samsung internet browser.
It used to work on previous Galaxy devices. Something between the new OneUI 7, the browser, and Bitwarden is not playing nice, and users never get the prompt to autofill passwords.
Expected Result
Inline autofil should work as it used to on older Samsung devices.
Actual Result
No Bitwarden inline autofil on keyboard. Users need to go to the bitwarden app and copy/paste the credentials.
Screenshots or Videos
No response
Additional Context
Samsung Browser Versions 27.0 and 28.0
Samsung Stock Keyboard
Build Version
2025.1.1
What server are you connecting to?
US
Self-host Server Version
No response
Environment Details
No response
Issue Tracking Info
- I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Thank you for your report! We've added this to our internal board for review.
ID: PM-17956
Hi there!
Thank you for your report, it seems like it is a duplicate of this one: #4586
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.
This issue will now be closed.
Thanks!
@cbbit
Sorry, I don't think this is the same issue. The other issue is in relation to the accessibility service. This one, is bitwardens inline autofill, and happens only when using Samsung Browser.
Agreed that this is not a duplicate issue. I was also trying to use inline auto fill without accessibility options, and I have the same results as described by the OP using 2025.1.2 build from Play store. Granted I am pending a new phone and on an unsupported version of Android on EOL hardware and it is entirely possible that is related, but I figured I can at least point out that these appear to be functionally different tickets.