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

[Feature Request] Remove internet connectivity dependency #114

New Issue
Closed
opened 2025-11-07 08:27:03 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-07 08:27:03 -06:00
Owner
Copy Link

Originally created by @OhjeezwhathaveIdone on GitHub (Nov 8, 2017).

With KeePass I have to sync the database with a third party application like Dropbox to be able to access it on mobile using MiniKeePass. This happens automatically on desktop but not on mobile and as a result requires manual user intervention to sync the KeePass database on mobile with the desktop version. This can obviously cause sync issues.
Bitwarden, by design, removes this syncing complexity by requiring the Bitwarden Application to communicate with the Bitwarden Server but what if the Bitwarden Server is inaccessible from the mobile device? Regardless of the internet connectivity status KeePass can still view, edit and create entries, on mobile, locally.

In the instances where the Bitwarden Server is not accessible I'd like to have the ability to still edit and create entries via the Bitwarden App. The modification should be stored locally and sync'd to the Server when next connected.

Examples for when the Bitwarden Server may not be contactable:

  • When on a secure/limited network and with no mobile signal
  • The Bitwarden Server itself is not accessible (whether it's the cloud or self hosted version) for whatever reason
Originally created by @OhjeezwhathaveIdone on GitHub (Nov 8, 2017). With KeePass I have to sync the database with a third party application like Dropbox to be able to access it on mobile using MiniKeePass. This happens automatically on desktop but not on mobile and as a result requires manual user intervention to sync the KeePass database on mobile with the desktop version. This can obviously cause sync issues. Bitwarden, by design, removes this syncing complexity by requiring the Bitwarden Application to communicate with the Bitwarden Server but what if the Bitwarden Server is inaccessible from the mobile device? Regardless of the internet connectivity status KeePass can still view, edit and create entries, on mobile, locally. In the instances where the Bitwarden Server is not accessible I'd like to have the ability to still edit and create entries via the Bitwarden App. The modification should be stored locally and sync'd to the Server when next connected. Examples for when the Bitwarden Server may not be contactable: - When on a secure/limited network and with no mobile signal - The Bitwarden Server itself is not accessible (whether it's the cloud or self hosted version) for whatever reason
GiteaMirror commented 2025-11-07 08:27:04 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 8, 2017):

Just FYI: you can still view and use (autofill) all information in your vault without an internet connection. The apps effectively run in a "read only" mode.

@kspearrin commented on GitHub (Nov 8, 2017): Just FYI: you can still view and use (autofill) all information in your vault without an internet connection. The apps effectively run in a "read only" mode.
GiteaMirror commented 2025-11-07 08:27:05 -06:00
Author
Owner
Copy Link

@OhjeezwhathaveIdone commented on GitHub (Nov 8, 2017):

@kspearrin but that does not allow me to create entries on mobile unless I have an active connection to the Bitwarden Server, correct? I did test this last night and Bitwarden requested an active internet connection, but in case I am wrong, I'd like to confirm.

I know in my use case of Bitwarden that I won't be able to connect to the Bitwarden Server all of the time, however regardless of connectivity status I'd still need to make modifications, hence I'd like the ability to sync any modifications that have been created whilst the device has been disconnected from the Bitwarden Server once reconnected.

@OhjeezwhathaveIdone commented on GitHub (Nov 8, 2017): @kspearrin but that does not allow me to create entries on mobile unless I have an active connection to the Bitwarden Server, correct? I did test this last night and Bitwarden requested an active internet connection, but in case I am wrong, I'd like to confirm. I know in my use case of Bitwarden that I **won't** be able to connect to the Bitwarden Server all of the time, however regardless of connectivity status I'd still need to make modifications, hence I'd like the ability to sync any modifications that have been created whilst the device has been disconnected from the Bitwarden Server once reconnected.
GiteaMirror commented 2025-11-07 08:27:05 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 8, 2017):

That is correct. I was commenting on your above statement:

In the instances where the Bitwarden Server is not accessible I'd like to have the ability to still view, edit and create entries via the Bitwarden App.

You can still view things today without an internet connection.

@kspearrin commented on GitHub (Nov 8, 2017): That is correct. I was commenting on your above statement: > In the instances where the Bitwarden Server is not accessible I'd like to have the ability to still ***view***, edit and create entries via the Bitwarden App. You can still *view* things today without an internet connection.
GiteaMirror commented 2025-11-07 08:27:05 -06:00
Author
Owner
Copy Link

@OhjeezwhathaveIdone commented on GitHub (Nov 8, 2017):

Ah, my apologies. Understood.

@OhjeezwhathaveIdone commented on GitHub (Nov 8, 2017): Ah, my apologies. Understood.
GiteaMirror commented 2025-11-07 08:27:05 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Nov 9, 2017):

Are you planning to give Bitwarden add & edit ability without internet

@jerryn70 commented on GitHub (Nov 9, 2017): Are you planning to give Bitwarden add & edit ability without internet
GiteaMirror commented 2025-11-07 08:27:06 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Mar 9, 2018):

We are moving away from tracking Bitwarden feature requests like this one as GitHub issues. We have created a Bitwarden Community Forum which has a section for submitting, voting for, and discussing product feature requests. Please sign up on our forums if you want to continue contributing to feature requests.

Since this was a popular feature request we have already re-created it on the forums and linked back to this GitHub issue for reference. You can vote for this feature request there if you'd like.

https://community.bitwarden.com/t/offline-management-of-writeable-vault-items/107

This issue will now be closed. Thanks!

@kspearrin commented on GitHub (Mar 9, 2018): We are moving away from tracking Bitwarden feature requests like this one as GitHub issues. We have created a [Bitwarden Community Forum](https://community.bitwarden.com) which has a section for submitting, voting for, and discussing product [feature requests](https://community.bitwarden.com/c/feature-requests). Please [sign up on our forums](https://community.bitwarden.com/signup) if you want to continue contributing to feature requests. Since this was a popular feature request we have already re-created it on the forums and linked back to this GitHub issue for reference. You can vote for this feature request there if you'd like. https://community.bitwarden.com/t/offline-management-of-writeable-vault-items/107 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#114
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?