github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-11 17:16:20 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #4685] Inline Autofill doesn't work on Galaxy S25 #8196

New Issue
Closed
opened 2026-04-11 01:16:48 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-11 01:16:48 -05:00
Owner
Copy Link

Originally created by @yurividal on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/4685

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.
Originally created by @yurividal on GitHub (Feb 4, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/4685 ### 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 - [x] 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.
GiteaMirror added the bug label 2026-04-11 01:16:48 -05:00
GiteaMirror commented 2026-04-11 01:16:51 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 4, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-17956

<!-- gh-comment-id:2634223742 --> @bitwarden-bot commented on GitHub (Feb 4, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17956
GiteaMirror commented 2026-04-11 01:16:52 -05:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Feb 4, 2025):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one: https://github.com/bitwarden/android/issues/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!

<!-- gh-comment-id:2635136328 --> @cbbit commented on GitHub (Feb 4, 2025): Hi there! Thank you for your report, it seems like it is a duplicate of this one: https://github.com/bitwarden/android/issues/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!
GiteaMirror commented 2026-04-11 01:16:53 -05:00
Author
Owner
Copy Link

@yurividal commented on GitHub (Feb 4, 2025):

@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.

<!-- gh-comment-id:2635146429 --> @yurividal commented on GitHub (Feb 4, 2025): @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.
GiteaMirror commented 2026-04-11 01:16:54 -05:00
Author
Owner
Copy Link

@hdub-tech commented on GitHub (Feb 20, 2025):

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.

<!-- gh-comment-id:2672913853 --> @hdub-tech commented on GitHub (Feb 20, 2025): 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#8196
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?