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

[GH-ISSUE #2775] Unable to turn off warning that "unlocking may fail due to insufficient memory" #27612

New Issue
Closed
opened 2026-04-18 11:06:32 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-18 11:06:32 -05:00
Owner
Copy Link

Originally created by @danmarg on GitHub (Sep 15, 2023).
Original GitHub issue: https://github.com/bitwarden/android/issues/2775

Steps To Reproduce

  1. Switch to Argon2 with default iterations.
  2. Unlock vault on iOS via the password autofill integration.

Note that Bitwarden warns that "unlocking may fail due to insufficient memory".

Expected Result

If the user is comfortable with the KDF iterations, Bitwarden should allow the user to permanently dismiss this warning.

Actual Result

This warning is shown on every unlock, and there is no setting to permanently dismiss or disable it.

Interestingly: I do not get this warning when unlocking the app itself, but only when using autofill.

Screenshots or Videos

No response

Additional Context

No response

Operating System

iOS

Operating System Version

No response

Device

No response

Build Version

2023.8.0 (4566)

Beta

  • Using a pre-release version of the application.
Originally created by @danmarg on GitHub (Sep 15, 2023). Original GitHub issue: https://github.com/bitwarden/android/issues/2775 ### Steps To Reproduce 1. Switch to Argon2 with default iterations. 2. Unlock vault on iOS *via the password autofill integration*. Note that Bitwarden warns that "unlocking may fail due to insufficient memory". ### Expected Result If the user is comfortable with the KDF iterations, Bitwarden should allow the user to permanently dismiss this warning. ### Actual Result This warning is shown on every unlock, and there is no setting to permanently dismiss or disable it. Interestingly: I do not get this warning when unlocking the app itself, but only when using autofill. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System iOS ### Operating System Version _No response_ ### Device _No response_ ### Build Version 2023.8.0 (4566) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2026-04-18 11:06:32 -05:00
GiteaMirror commented 2026-04-18 11:06:34 -05:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Sep 18, 2023):

Hi there,

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum.

Thanks!

<!-- gh-comment-id:1722964017 --> @Krychaz commented on GitHub (Sep 18, 2023): Hi there, We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum. Thanks!
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#27612
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?