Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autofill broken on iOS after updating Bitwarden app #3231

Closed
1 task
PowerNodeS opened this issue May 9, 2024 · 1 comment
Closed
1 task

Autofill broken on iOS after updating Bitwarden app #3231

PowerNodeS opened this issue May 9, 2024 · 1 comment
Labels

Comments

@PowerNodeS
Copy link

Steps To Reproduce

  1. Enable Bitwarden as the only autofill option in iOS settings.
  2. Launch any app or webpage that requires login credentials.
  3. Tap on autofill suggestion above keyboard.
  4. Authenticate with Bitwarden using master password or biometrics (Face ID).

Expected Result

App or webpage fields should autofill with the respective username and password.

Actual Result

The fields remain empty. Autofill function breaks and will no longer suggest autofill above keyboard on any app or webpage. Instead, a passwords key icon is presented and must be tapped and the user must manually choose login credentials from within Bitwarden in order to fill fields.

To restore autofill suggestion above the keyboard, the Bitwarden autofill toggle in iOS Settings must be toggled off and back on. The next attempt to use autofill will result in a loop of the results described above.

Screenshots or Videos

RPReplay_Final1715223848.mp4

Additional Context

This issue has also been reported in the Bitwarden Reddit thread here.

Operating System

iOS

Operating System Version

iOS 17.4.1, iPadOS 17.4.1

Device

iPhone 15 Pro Max, iPad Pro 12.9 (5th Gen)

Build Version

Version 2024.4.2 (7528)

Beta

  • Using a pre-release version of the application.
@PowerNodeS PowerNodeS added the bug label May 9, 2024
@sammbw
Copy link

sammbw commented May 9, 2024

Hi there!

Thank you for your report, it seems like it is a duplicate of this one: #3225

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!

@sammbw sammbw closed this as completed May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants