github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-12 06:41:12 -05:00
Code Issues 1.1k Packages Projects Releases 124 Wiki Activity

[GH-ISSUE #802] Autofill pop up inconsistent compared to previous notifications api #26855

New Issue
Closed
opened 2026-04-18 10:11:57 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 10:11:57 -05:00
Owner
Copy Link

Originally created by @05nelsonm on GitHub (Mar 28, 2020).
Original GitHub issue: https://github.com/bitwarden/android/issues/802

Describe the Bug

The new api for displaying autofill as an overlay in the app username/password field (especially with browsers when at a login page of a website), doesn't always show up. The old notification api was FAR more consistent.

Is there a way to give users the option to choose either or?

Originally created by @05nelsonm on GitHub (Mar 28, 2020). Original GitHub issue: https://github.com/bitwarden/android/issues/802 <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug The new api for displaying autofill as an overlay in the app username/password field (especially with browsers when at a login page of a website), doesn't always show up. The old notification api was FAR more consistent. Is there a way to give users the option to choose either or?
GiteaMirror commented 2026-04-18 10:11:59 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 28, 2020):

Fully agreed! The previous system was far superior for a user like myself. I had the old system set to persistent notification to conserve battery life and to keep the app from being shutdown in the background. The new system regularly doesn't work for me and is very inconsistent and messy. I would have much preferred this be an opt-in or at the very least have the old system be an opt-in. I don't understand why the old system was removed, surely it wouldn't have been much effort if any to continue supporting it alongside this new inconsistent system.

In short please bring back the old system as an option, especially the consistent notification version because that was the most reliable. I'm going to use the outdated client for now.

<!-- gh-comment-id:605525100 --> @ghost commented on GitHub (Mar 28, 2020): Fully agreed! The previous system was far superior for a user like myself. I had the old system set to persistent notification to conserve battery life and to keep the app from being shutdown in the background. The new system regularly doesn't work for me and is very inconsistent and messy. I would have much preferred this be an opt-in or at the very least have the old system be an opt-in. I don't understand why the old system was removed, surely it wouldn't have been much effort if any to continue supporting it alongside this new inconsistent system. In short please bring back the old system as an option, especially the consistent notification version because that was the most reliable. I'm going to use the outdated client for now.
GiteaMirror commented 2026-04-18 10:12:00 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Mar 29, 2020):

Duplicate https://github.com/bitwarden/mobile/issues/784

We are working on a new alternative way to autofill until we can figure out whey this popup overlay isnt working right for some people.

<!-- gh-comment-id:605543331 --> @kspearrin commented on GitHub (Mar 29, 2020): Duplicate https://github.com/bitwarden/mobile/issues/784 We are working on a new alternative way to autofill until we can figure out whey this popup overlay isnt working right for some people.
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
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#26855
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?