github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 14:16:23 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

[iOS Accessibility] VoiceOver always seeing fields for all entry types #1165

New Issue
Closed
opened 2025-11-26 22:41:01 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 22:41:01 -06:00
Owner
Copy Link

Originally created by @pitermach on GitHub (Dec 28, 2020).

Originally assigned to: @eliykat on GitHub.

Describe the Bug

No matter what type of entry you're creating or viewing, VoiceOver is seeing the text fields for every other type of entry (IE, if creating a secure note you see text fields for username, password, credit card number and so on)

Steps To Reproduce

  1. Enable VoiceOver (Settings>Accessibility>VoiceOver, or ask siri to turn VoiceOver on)
  2. Note that now the screen will behave differently, touching something will first cause VoiceOver to highlight and speak it, you then need to tap the screen twice to actually press on a control.
  3. In bitwarden, go to add an item
  4. Even without changing the item type, touch on one of the first fields, like username, then continue swiping right to make VoiceOver move sequentially through all controls.

Expected Result

Assuming the default item type of login is being added, you should only see the fields for name, username, password and URI

Actual Result

You will also be able to focus the fields for credit card information, identities and so on. Also, the fields for URI for some reason appear at the bottom of these controls, so accessing them will take a long time to get past all the other fantom text fields. This issue also occurs in a similar fassion when viewing an entry

Screenshots or Videos

Screen Recording
here I demonstrate the problem when trying to add a secure note with voice commentary for context.

Environment

  • Device: iPhone SE 2020
  • Operating system: iOS 14.3
  • Build Version: 2.7.2 (401)
  • Is this a Beta release? No

Additional Context

As I explained in the recording, this slows down navigation while viewing an entry considerably, there's also a security concern, because one of the things that's improperly hidden as a result while viewing an item is the plain text form of a password, no matter whether the button to toggle visibility is pressed or not so one could very easily broadcast a password to anyone in earshot of your phone.

Originally created by @pitermach on GitHub (Dec 28, 2020). Originally assigned to: @eliykat on GitHub. ## Describe the Bug No matter what type of entry you're creating or viewing, VoiceOver is seeing the text fields for every other type of entry (IE, if creating a secure note you see text fields for username, password, credit card number and so on) ## Steps To Reproduce 1. Enable VoiceOver (Settings>Accessibility>VoiceOver, or ask siri to turn VoiceOver on) 2. Note that now the screen will behave differently, touching something will first cause VoiceOver to highlight and speak it, you then need to tap the screen twice to actually press on a control. 3. In bitwarden, go to add an item 4. Even without changing the item type, touch on one of the first fields, like username, then continue swiping right to make VoiceOver move sequentially through all controls. ## Expected Result Assuming the default item type of login is being added, you should only see the fields for name, username, password and URI ## Actual Result You will also be able to focus the fields for credit card information, identities and so on. Also, the fields for URI for some reason appear at the bottom of these controls, so accessing them will take a long time to get past all the other fantom text fields. This issue also occurs in a similar fassion when viewing an entry ## Screenshots or Videos [Screen Recording](https://cloud.tardis.pw/f/48f9adeb976845fdac1a/) here I demonstrate the problem when trying to add a secure note with voice commentary for context. ## Environment - Device: iPhone SE 2020 - Operating system: iOS 14.3 - Build Version: 2.7.2 (401) - Is this a Beta release? No ## Additional Context As I explained in the recording, this slows down navigation while viewing an entry considerably, there's also a security concern, because one of the things that's improperly hidden as a result while viewing an item is the plain text form of a password, no matter whether the button to toggle visibility is pressed or not so one could very easily broadcast a password to anyone in earshot of your phone.
GiteaMirror commented 2025-11-26 22:41:01 -06:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Jan 12, 2021):

Hi @pitermach, thanks for the detailed bug report - the video was especially helpful.

As discussed in the pull request, this issue should be fixed with the next Xamarin.Forms update, which is being worked on at the moment. I'll leave this issue open until the update has been completed and we've tested it again to confirm the issue is resolved.

@eliykat commented on GitHub (Jan 12, 2021): Hi @pitermach, thanks for the detailed bug report - the video was especially helpful. As discussed in the [pull request](https://github.com/bitwarden/mobile/pull/1213), this issue should be fixed with the next Xamarin.Forms update, which is being worked on at the moment. I'll leave this issue open until the update has been completed and we've tested it again to confirm the issue is resolved.
GiteaMirror commented 2025-11-26 22:41:02 -06:00
Author
Owner
Copy Link

@pitermach commented on GitHub (Jan 12, 2021):

Excellent, thanks for looking into this. I'm looking forward to testing the fixed version once it releases.

@pitermach commented on GitHub (Jan 12, 2021): Excellent, thanks for looking into this. I'm looking forward to testing the fixed version once it releases.
GiteaMirror commented 2025-11-26 22:41:02 -06:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Jun 1, 2021):

Related to #1089

@eliykat commented on GitHub (Jun 1, 2021): Related to #1089
GiteaMirror commented 2025-11-26 22:41:02 -06:00
Author
Owner
Copy Link

@fedemkr commented on GitHub (Oct 26, 2021):

Closing the issue given that update of Xamarin Forms 5 fixed this automatically.

@fedemkr commented on GitHub (Oct 26, 2021): Closing the issue given that update of Xamarin Forms 5 fixed this automatically.
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#1165
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?