Request to use a different package ID for the F-Droid build to avoid conflicts with Play Store

Hi, I use F-Droid to manage bitwarden but currently it shares the exact same package ID (com.x8bit.bitwarden) as the Google Play version, the Play Store constantly tries to overwrite it with the non-FOSS build or nags about update errors. It’s honestly a bit of a battle to avoid this behaviour since F-Droid updates are generally late

Please consider giving the F-Droid flavor a different package ID. I understand this would require additional work (which I am ready to undertake) but it would be a massive quality-of-life improvement for privacy users who shouldn't have to use hacky workarounds just to keep the updates hassle free.

The issue names no files, tests, or entry points. Start by locating the Android F-Droid flavor's package ID and its build configuration, then trace references that must remain consistent; done means F-Droid installs and updates under a distinct ID without Play Store conflicts.

Written by the indexing model from the issue text.