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

[GH-ISSUE #3641] versions since 2024.6.1-beta not in f-droid repo #21201

New Issue
Closed
opened 2026-04-16 21:32:15 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 21:32:15 -05:00
Owner
Copy Link

Originally created by @konradmoesch on GitHub (Jul 28, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3641

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Open your F-Droid client
    (2. Add Bitwarden Repo, if not already done)
  2. Search for 'Bitwarden'

Expected Result

The versions should be available and shown in F-Droid

Actual Result

The latest version available via F-Droid is 2024.6.0, no newer versions can be found, not even as another app entry / under another package

Screenshots or Videos

No response

Additional Context

F-Droid build artifacts are available here in github, but Seen to not be linked to in your F-Droid repo. Please fix this!

I have enabled "Show unstable versions" in the F-Droid client.

If the updates would be pushed as new versions of the "Bitwarden" app entry (and not, for example, "Bitwarden (Beta)"), without raising "CurrentVersion", the would be marked as Prereleases (see https://f-droid.org/en/docs/Build_Metadata_Reference/#currentversion for more info)

Build Version

all beginning with 2024.6.1

Environment Details

No response

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @konradmoesch on GitHub (Jul 28, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3641 ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Open your F-Droid client (2. Add Bitwarden Repo, if not already done) 3. Search for 'Bitwarden' ### Expected Result The versions should be available and shown in F-Droid ### Actual Result The latest version available via F-Droid is 2024.6.0, no newer versions can be found, not even as another app entry / under another package ### Screenshots or Videos _No response_ ### Additional Context F-Droid build artifacts are available here in github, but Seen to not be linked to in your F-Droid repo. Please fix this! I have enabled "Show unstable versions" in the F-Droid client. If the updates would be pushed as new versions of the "Bitwarden" app entry (and not, for example, "Bitwarden (Beta)"), without raising "CurrentVersion", the would be marked as Prereleases (see https://f-droid.org/en/docs/Build_Metadata_Reference/#currentversion for more info) ### Build Version all beginning with 2024.6.1 ### Environment Details _No response_ ### Issue Tracking Info - [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bug label 2026-04-16 21:32:15 -05:00
GiteaMirror commented 2026-04-16 21:32:17 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jul 28, 2024):

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

<!-- gh-comment-id:2254321789 --> @bitwarden-bot commented on GitHub (Jul 28, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-10180
GiteaMirror commented 2026-04-16 21:32:18 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Jul 30, 2024):

Hi @konradmoesch,

Thank you for this report. We currently have no plans to distribute the Native clients in the Beta stage via F-Droid. Please consider using the Google Play Store or, if you wish, you can download the .apk files off the GitHub repository.

If you have any questions or concerns, please feel free to get in touch and please include a link to this GitHub report if you do.

Thank you again,

<!-- gh-comment-id:2258889955 --> @SergeantConfused commented on GitHub (Jul 30, 2024): Hi @konradmoesch, Thank you for this report. We currently have no plans to distribute the [Native clients in the Beta](https://bitwarden.com/blog/native-mobile-apps/) stage via F-Droid. Please consider using the Google Play Store or, if you wish, you can download the .apk files off the [GitHub repository](https://github.com/Bitwarden/Android/releases). If you have any questions or concerns, please feel free to [get in touch](https://bitwarden.com/help/) and please include a link to this GitHub report if you do. Thank you again,
GiteaMirror commented 2026-04-16 21:32:19 -05:00
Author
Owner
Copy Link

@konradmoesch commented on GitHub (Jul 30, 2024):

@SergeantConfused , thanks for your answer.
Is this a hard decision, or just a matter of priorities? If it is the latter, I would provide the needed code snipppets for changing the github actions workflow / a metadata file for the f-droid repo. If you say there is a chance that you would accept it, of course.

I think I am not the only user that would love to see a less google-centric (or manual) distribution of your betas. The repo and infrastructure already exists, after all

<!-- gh-comment-id:2258954863 --> @konradmoesch commented on GitHub (Jul 30, 2024): @SergeantConfused , thanks for your answer. Is this a hard decision, or just a matter of priorities? If it is the latter, I would provide the needed code snipppets for changing the github actions workflow / a metadata file for the f-droid repo. If you say there is a chance that you would accept it, of course. I think I am not the only user that would love to see a less google-centric (or manual) distribution of your betas. The repo and infrastructure already exists, after all
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#21201
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?