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

iOS password autofill doesn't work with Argon2id #1600

New Issue
Closed
opened 2025-11-26 22:53:19 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-26 22:53:19 -06:00
Owner
Copy Link

Originally created by @bobokapi on GitHub (Feb 17, 2023).

Steps To Reproduce

  1. Change KDF to Argon2id.
  2. Enable password autofill.
  3. Go to any website or app and try to autofill a password.
  4. Type in master password and hit enter.

Expected Result

Password is autofilled.

Actual Result

Bitwarden autofill quits, but doesn't autofill the password. When I try to click on autofill again - it again prompts me to enter my master password, and again it quits without autofilling the password.

Screenshots or Videos

No response

Additional Context

When I change the KDF back to PBKDF2, then password autofill works again.

Operating System

iOS

Operating System Version

iOS 16.2

Device

iPhone 12 Pro and iPhone 14 (tried on both and had the same issue)

Build Version

2023.2.0

Beta

  • Using a pre-release version of the application.
Originally created by @bobokapi on GitHub (Feb 17, 2023). ### Steps To Reproduce 1. Change KDF to Argon2id. 2. Enable password autofill. 3. Go to any website or app and try to autofill a password. 4. Type in master password and hit enter. ### Expected Result Password is autofilled. ### Actual Result Bitwarden autofill quits, but doesn't autofill the password. When I try to click on autofill again - it again prompts me to enter my master password, and again it quits without autofilling the password. ### Screenshots or Videos _No response_ ### Additional Context When I change the KDF back to PBKDF2, then password autofill works again. ### Operating System iOS ### Operating System Version iOS 16.2 ### Device iPhone 12 Pro and iPhone 14 (tried on both and had the same issue) ### Build Version 2023.2.0 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:53:19 -06:00
GiteaMirror commented 2025-11-26 22:53:20 -06:00
Author
Owner
Copy Link

@bobokapi commented on GitHub (Feb 17, 2023):

@quexten FYI

@bobokapi commented on GitHub (Feb 17, 2023): @quexten FYI
GiteaMirror commented 2025-11-26 22:53:20 -06:00
Author
Owner
Copy Link

@quexten commented on GitHub (Feb 17, 2023):

Do you have the memory setting set to > 64MiB?

@quexten commented on GitHub (Feb 17, 2023): Do you have the memory setting set to > 64MiB?
GiteaMirror commented 2025-11-26 22:53:20 -06:00
Author
Owner
Copy Link

@bobokapi commented on GitHub (Feb 18, 2023):

Yes, I had it set to 256 MiB or 512 MiB IIRC. When I changed back to the default setting, it worked. I didn't realize that was the problem because it worked when I logged in to the app, but didn't work for autofill. Do you know why the memory parameter needs to be set lower for autofill to work?

@bobokapi commented on GitHub (Feb 18, 2023): Yes, I had it set to 256 MiB or 512 MiB IIRC. When I changed back to the default setting, it worked. I didn't realize that was the problem because it worked when I logged in to the app, but didn't work for autofill. Do you know why the memory parameter needs to be set lower for autofill to work?
GiteaMirror commented 2025-11-26 22:53:20 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Feb 18, 2023):

I believe iOS Extensions have limited memory available from the OS and crash when that is exceeded.

@kspearrin commented on GitHub (Feb 18, 2023): I believe iOS Extensions have limited memory available from the OS and crash when that is exceeded.
GiteaMirror commented 2025-11-26 22:53:20 -06:00
Author
Owner
Copy Link

@quexten commented on GitHub (Feb 18, 2023):

Yes. On some other password managers there is a warning above 64 MiB. In the forums users tested up to 80MiB without issues, but I guess that also depends on the size of the database. It does not happen when biometrics are used.

Maybe there should be a warning on iOS when logging in (or auto-filling) and having > 64MiB, such as: "Warning: Due to restrictions on iOS, auto-fill does not work reliably for argon2 memory configurations above 64MB"

@quexten commented on GitHub (Feb 18, 2023): Yes. On some other password managers there is a warning above 64 MiB. In the forums users tested up to 80MiB without issues, but I guess that also depends on the size of the database. It does not happen when biometrics are used. Maybe there should be a warning on iOS when logging in (or auto-filling) and having > 64MiB, such as: "Warning: Due to restrictions on iOS, auto-fill does not work reliably for argon2 memory configurations above 64MB"
GiteaMirror commented 2025-11-26 22:53:21 -06:00
Author
Owner
Copy Link

@bobokapi commented on GitHub (Feb 18, 2023):

Thanks for the information. I'll close this issue. I agree that having a warning when logging in on iOS with >64 MiB would be helpful.

@bobokapi commented on GitHub (Feb 18, 2023): Thanks for the information. I'll close this issue. I agree that having a warning when logging in on iOS with >64 MiB would be helpful.
GiteaMirror commented 2025-11-26 22:53:21 -06:00
Author
Owner
Copy Link

@arderyp commented on GitHub (Aug 9, 2023):

@bobokapi I am having this issue on latest iOS with argon2 memory set to 64.

The issue only started happening maybe since iOS 16

Sometimes it works despite the warning, sometimes it doesn't

I believe I also have the default iterations and parallelism values

@arderyp commented on GitHub (Aug 9, 2023): @bobokapi I am having this issue on latest iOS with argon2 memory set to 64. The issue only started happening maybe since iOS 16 Sometimes it works despite the warning, sometimes it doesn't I believe I also have the default iterations and parallelism values
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#1600
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?