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

Inconsistent placement of the "use another method" button in the 2FA authentication screen #1299

New Issue
Closed
opened 2025-11-26 22:44:14 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 22:44:14 -06:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jun 5, 2021).

Describe the Bug

When logging in Bitwarden, the "log in" button is located at the bottom, but in the next screen, the "use another method" button is in the same place of the "log in" button, instead of the "continue" button. If you accidentally press the "use another method" button and press back, the whole process will be canceled. This inconsistency creates a non-intuitive design.

Steps To Reproduce

  1. Log in with your credentials (2FA must be enabled).

Expected Result

The continue button should be at the bottom.

Actual Result

N/A

Screenshots or Videos

N/A

Environment

  • Device: A50
  • Operating system: Android 11
  • Build Version (go to "Settings" → "About" in the app): 2.10.0 (3516)
  • Is this a Beta release? no

Additional Context

N/A

Originally created by @ghost on GitHub (Jun 5, 2021). ## Describe the Bug When logging in Bitwarden, the "log in" button is located at the bottom, but in the next screen, the "use another method" button is in the same place of the "log in" button, instead of the "continue" button. If you accidentally press the "use another method" button and press back, the whole process will be canceled. This inconsistency creates a non-intuitive design. ## Steps To Reproduce 1. Log in with your credentials (2FA must be enabled). ## Expected Result The continue button should be at the bottom. ## Actual Result N/A ## Screenshots or Videos N/A ## Environment - Device: A50 - Operating system: Android 11 - Build Version (go to "Settings" → "About" in the app): 2.10.0 (3516) - Is this a Beta release? no ## Additional Context N/A
GiteaMirror added the help wanted label 2025-11-26 22:44:14 -06:00
GiteaMirror commented 2025-11-26 22:44:14 -06:00
Author
Owner
Copy Link

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

I agree, I moved the log in buttons in #1073 but didn't extend the changes to the 2FA screen. If anyone would like to tackle it they're welcome, otherwise I'll put it on the to-do list.

@eliykat commented on GitHub (Jun 6, 2021): I agree, I moved the log in buttons in #1073 but didn't extend the changes to the 2FA screen. If anyone would like to tackle it they're welcome, otherwise I'll put it on the to-do list.
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 help wanted
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#1299
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?