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

[GH-ISSUE #5976] [PM-26717] Bitwarden's F-droid repo does not offer latest release, causing gPlaystore to constantly offer to upgrade creating conflict and confusion! #39330

New Issue
Closed
opened 2026-04-23 18:07:22 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-23 18:07:22 -05:00
Owner
Copy Link

Originally created by @ipfreer on GitHub (Oct 6, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5976

plz forgive lack of body in initial issue post, as well no template used, first time using OctoDroid Android app to post issue and it shows no template.

regardless, for past couple months I've not been able to keep Bitwarden up to date with latest version because F-droid repo only offer the most recent previous version for install/update.

i.e. 2025.9.0 is latest on F-droid clients using Bitwarden's official F-droid repo, while 2025.9.1 is offered for update to installed 2025.9.0

This can cause both confusion (as both versions seem to show same release date in the respective app stores (gPlaystore official app vs Droidify F-droid client )

This can cause huge conflict if one installed Bitwarden Password Manager via official F-droid repo then later (mistakenly) upgrades to newer release version via Google PlayStore which changes installer/installed from-by which changes APK signer and opens app to updates from any source (dangerous) at worst and/or causes any BW local files to be overwritten, replaced, deleted (I believe), likely also forcing login as new install portentously being catastrophic to user using biometrics on device for unlock while far away from desktop or other device used to approve new installs of Bitwarden Password Manager.

i do not believe this is influenced by device type nor Android version, however, fwiw this is happening in both Google Pixel 7 pro on latest Android beta version as well as on Google Pixel Fold running latest GrapheneOS alpha version.

🙏plz again forgive as I see no way to attach files while using this particular GitHub client (OctoDroid) so will use browser if screenshots are requested because this is not reproducible or otherwise not understood.

Truly appreciate you guys! I've been paying customer since 2017 and don't think anything out there compares, bit for bit, featurewise🫶

✊🪖🫡🕊️✌️
🗿🪦🐐💨

Originally created by @ipfreer on GitHub (Oct 6, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5976 plz forgive lack of body in initial issue post, as well no template used, first time using OctoDroid Android app to post issue and it shows no template. regardless, for past couple months I've not been able to keep Bitwarden up to date with latest version because F-droid repo only offer the most recent *previous* version for install/update. i.e. 2025.9.0 is latest on F-droid clients using Bitwarden's official F-droid repo, while 2025.9.1 is offered for update to installed 2025.9.0 This can cause both confusion (as both versions seem to show same release date in the respective app stores (gPlaystore official app vs Droidify F-droid client ) This can cause huge conflict if one installed Bitwarden Password Manager via official F-droid repo then later (mistakenly) upgrades to newer release version via Google PlayStore which changes installer/installed from-by which changes APK signer and opens app to updates from any source (dangerous) at worst and/or causes any BW local files to be overwritten, replaced, deleted (I believe), likely also forcing login as new install portentously being catastrophic to user using biometrics on device for unlock while far away from desktop or other device used to approve new installs of Bitwarden Password Manager. i do not believe this is influenced by device type nor Android version, however, fwiw this is happening in both Google Pixel 7 pro on latest Android beta version as well as on Google Pixel Fold running latest GrapheneOS alpha version. 🙏plz again forgive as I see no way to attach files while using this particular GitHub client (OctoDroid) so will use browser if screenshots are requested because this is not reproducible or otherwise not understood. Truly appreciate you guys! I've been paying customer since 2017 and don't think anything out there compares, bit for bit, featurewise🫶 ✊🪖🫡🕊️✌️ 🗿🪦🐐💨
GiteaMirror commented 2026-04-23 18:07:23 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Oct 8, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-26717

<!-- gh-comment-id:3382969609 --> @bitwarden-bot commented on GitHub (Oct 8, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-26717
GiteaMirror commented 2026-04-23 18:07:24 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Oct 8, 2025):

Hi @ipfreer

Appreciate you calling this to our attention. We had a bit of a hiccup in our automation. I'm happy to say it's been resolved and you should see the latest version available on F-Droid now. Going forward new versions will be available the same day GitHub releases are created.

<!-- gh-comment-id:3383179331 --> @SaintPatrck commented on GitHub (Oct 8, 2025): Hi @ipfreer Appreciate you calling this to our attention. We had a bit of a hiccup in our automation. I'm happy to say it's been resolved and you should see the latest version available on F-Droid now. Going forward new versions will be available the same day GitHub releases are created.
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#39330
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?