github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 20:41:29 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

[PM-25231] Beta apks are being filtered out of GH releases #2334

New Issue
Closed
opened 2025-11-26 23:16:04 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 23:16:04 -06:00
Owner
Copy Link

Originally created by @sommerfelddev on GitHub (Aug 27, 2025).

Steps To Reproduce

  1. Go to https://github.com/bitwarden/android/releases/tag/v2025.8.0-bwpm

Expected Result

The presence of beta and fdroid-beta apks in the Artifacts such as in the previous release: https://github.com/bitwarden/android/releases/tag/v2025.7.2-bwpm

Actual Result

No beta nor fdroid-beta apks in the release Artifacts

Screenshots or Videos

No response

Additional Context

This is the cause: https://github.com/bitwarden/android/pull/5666#discussion_r2300621216

Build Version

v2025.8.0-bwpm

What server are you connecting to?

Self-host

Self-host Server Version

No response

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 @sommerfelddev on GitHub (Aug 27, 2025). ### Steps To Reproduce 1. Go to https://github.com/bitwarden/android/releases/tag/v2025.8.0-bwpm ### Expected Result The presence of `beta` and `fdroid-beta` apks in the Artifacts such as in the previous release: https://github.com/bitwarden/android/releases/tag/v2025.7.2-bwpm ### Actual Result No `beta` nor `fdroid-beta` apks in the release Artifacts ### Screenshots or Videos _No response_ ### Additional Context This is the cause: https://github.com/bitwarden/android/pull/5666#discussion_r2300621216 ### Build Version v2025.8.0-bwpm ### What server are you connecting to? Self-host ### Self-host Server Version _No response_ ### 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 app:password-managerbug labels 2025-11-26 23:16:04 -06:00
GiteaMirror commented 2025-11-26 23:16:05 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 27, 2025):

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

@bitwarden-bot commented on GitHub (Aug 27, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-25231
GiteaMirror commented 2025-11-26 23:16:05 -06:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Aug 28, 2025):

Hi there,

Your issue appears to be describing an intended change on Bitwarden's part. Bitwarden is not currently running a Beta program for our Android app, and has not run one since the release of our native application in November 2024. While a Beta release was still included in the build process, this version was identical to the standard release.

Bitwarden may use a Beta program again in the future.

This issue will now be closed.

Thanks!

@rmcdowell-bitwarden commented on GitHub (Aug 28, 2025): Hi there, Your issue appears to be describing an intended change on Bitwarden's part. Bitwarden is not currently running a Beta program for our Android app, and has not run one since the release of our native application in November 2024. While a Beta release was still included in the build process, this version was identical to the standard release. Bitwarden may use a Beta program again in the future. This issue will now be closed. Thanks!
GiteaMirror commented 2025-11-26 23:16:05 -06:00
Author
Owner
Copy Link

@sommerfelddev commented on GitHub (Aug 28, 2025):

Thanks for the clarification!

Just some feedback:

I had the beta version installed (and updated) through Obtainium. I initially did it for the mobile passkey early support.

This change now forces me to uninstall the current app, install the non-beta, re-login and apply the same settings. Doable but midly annoying and inconvenient.

I also feel that this was communicated suboptimally. I usually read all the release notes before updating and there was no mention that the beta version would be discontinued. I was compelled to investigate it myself and all pointed to it being a mistake: the beta variant is still present in the build system and still built in the GHA job, just filtered out (why build it then? Just to waste some Wh?)

Some heads up would have been appreciated.

@sommerfelddev commented on GitHub (Aug 28, 2025): Thanks for the clarification! Just some feedback: I had the beta version installed (and updated) through Obtainium. I initially did it for the mobile passkey early support. This change now forces me to uninstall the current app, install the non-beta, re-login and apply the same settings. Doable but midly annoying and inconvenient. I also feel that this was communicated suboptimally. I usually read all the release notes before updating and there was no mention that the beta version would be discontinued. I was compelled to investigate it myself and all pointed to it being a mistake: the beta variant is still present in the build system and still built in the GHA job, just filtered out (why build it then? Just to waste some Wh?) Some heads up would have been appreciated.
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 app:password-manager 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#2334
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?