github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #603] iOS main app and app extension don't share unlock state #6855

New Issue
Closed
opened 2026-04-10 23:12:51 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-10 23:12:51 -05:00
Owner
Copy Link

Originally created by @danielresnick on GitHub (Sep 18, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/603

It seems that the main app and the autofill app extension don't share unlock state which results in frequently needing to re-enter the master password even within the auto lock time limits.

This is WAI to avoid writing the master password (or some derived data) to disk? If so perhaps we could use CFNotificationCenter to share state if both the main app and the app extension happen to be alive at the same time.

Originally created by @danielresnick on GitHub (Sep 18, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/603 It seems that the main app and the autofill app extension don't share unlock state which results in frequently needing to re-enter the master password even within the auto lock time limits. This is WAI to avoid writing the master password (or some derived data) to disk? If so perhaps we could use CFNotificationCenter to share state if both the main app and the app extension happen to be alive at the same time.
GiteaMirror commented 2026-04-10 23:12:52 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Sep 18, 2019):

The main app and app extensions do not share memory space. An unlocked vault holds the encryption key in memory. I do not know of any way this could work.

<!-- gh-comment-id:532497883 --> @kspearrin commented on GitHub (Sep 18, 2019): The main app and app extensions do not share memory space. An unlocked vault holds the encryption key in memory. I do not know of any way this could work.
GiteaMirror commented 2026-04-10 23:12:52 -05:00
Author
Owner
Copy Link

@danielresnick commented on GitHub (Sep 18, 2019):

https://www.atomicbird.com/blog/sharing-with-app-extensions gives a nice overview of what's possible. You could share the encryption key via CFNotificationCenterGetDarwinNotifyCenter in either direction (from extension to app or vice-versa) and avoid writing anything to disk.

<!-- gh-comment-id:532499298 --> @danielresnick commented on GitHub (Sep 18, 2019): https://www.atomicbird.com/blog/sharing-with-app-extensions gives a nice overview of what's possible. You could share the encryption key via CFNotificationCenterGetDarwinNotifyCenter in either direction (from extension to app or vice-versa) and avoid writing anything to disk.
GiteaMirror commented 2026-04-10 23:12:53 -05:00
Author
Owner
Copy Link

@danielresnick commented on GitHub (Sep 18, 2019):

Actually that might be problematic since AFAICT there isn't any way to lock down darwin notifications to your app group only. I wonder if it's possible to share a file descriptor that points at a memory backed file which is locked down to the bitwarden app group only. Will investigate further.

<!-- gh-comment-id:532501991 --> @danielresnick commented on GitHub (Sep 18, 2019): Actually that might be problematic since AFAICT there isn't any way to lock down darwin notifications to your app group only. I wonder if it's possible to share a file descriptor that points at a memory backed file which is locked down to the bitwarden app group only. Will investigate further.
GiteaMirror commented 2026-04-10 23:12:53 -05:00
Author
Owner
Copy Link

@djsmith85 commented on GitHub (Mar 3, 2022):

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a section for submitting, voting for, and discussing product feature requests like this one.

Please sign up on our forums and search to see if this request already exists. 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.

Here's a link to the existing feature request on our forums:
https://community.bitwarden.com/t/login-to-browser-extensions-when-logging-into-desktop-app-and-vice-versa/1635

This issue will now be closed. Thanks!

<!-- gh-comment-id:1058000461 --> @djsmith85 commented on GitHub (Mar 3, 2022): We use GitHub issues as a place to track bugs and other development related issues. The [Bitwarden Community Forums](https://community.bitwarden.com) has a section for submitting, voting for, and discussing product [feature requests](https://community.bitwarden.com/c/feature-requests) like this one. Please [sign up on our forums](https://community.bitwarden.com/signup) and search to see if this request already exists. 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. Here's a link to the existing feature request on our forums: https://community.bitwarden.com/t/login-to-browser-extensions-when-logging-into-desktop-app-and-vice-versa/1635 This issue will now be closed. 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
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#6855
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?